Using wp_editor instead of wysiwyg

  • Is that possible?

    I’ve tried to hack the code myself for “tiny_mce” shortcode element type and tried replacing the “wysiwyg” plugin with native wp_editor() function and it all worked well until I modify the contents of the editor in the “Text” tab.

    When I update things on the “Text” tab, all content entered earlier disappears and doesn’t save.

    I’m actually reporting this as a bug but asking if there’s a way to use native WP editor for text areas?

    Thanks in advance!

    https://www.ads-software.com/plugins/ig-pagebuilder/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author InnoGears

    (@innogears)

    Hi sj_o,

    What a good hack ;), but the native WP editor got problem when using inside an iframe, and the problem you had is what we had, so we decided to use a simple wysiwyg editor for the first versions of IG PageBuilder. And we’ll try to find a way to implement the WP editor into it also.

    In case you find the solution for this, all contributions are welcomed, you can find the resource here:

    https://github.com/wp-plugins/ig-pagebuilder

    * An other not-related information: we had already the mechanism to allow 3rd-party developers to extend IG PageBuilder ability, the API and documents will be provided soon, so please keep an eye on us if your are interested in ??

    Thread Starter Onur Oztaskiran

    (@sj_o)

    Thanks and unfortunately I couldn’t find a way around it but disable the “Text/Html” tab (not from the function but with js overrides) on the wp_editor for the elements in the builder. So anyone using the builder with wp_editor elements would have to stick with the visual editor on my version. All is fine that way.

    They can always switch back to classic editor and edit html there anyways, but still this doesn’t make it a solution but a cheap hack ??

    I definitely want to contribute but I’m actually a designer and a very poor developer and not sure how qualified my code will be, since I may break things while I fix something else ??

    Still, very impatiently awaiting those API docs! ??

    The other things I tried to hack are as follows just fyi:

    – Replaced “fancybox” with a much more lightweight lightbox – Magnific Popup (https://dimsemenov.com/plugins/magnific-popup/)
    – Trying to implement font-awesome instead of icomoon since FA has more than 400 font options
    – Did a stupid (and not proud of it:)) “if (‘post.php’==$pagenow && isset($_GET[‘post’])) {…” – then load pagebuilder thing since when the builder is activated it takes over wp-admin everywhere even when not needed and I just wanted to enable it in specific post types such as pages and posts only, excluding custom post types or make it flexible to select where to use. Couldn’t find an easier way because the builder class works as a whole system for both front end and admin and I’m trying to separate front end inits from admin inits.
    – Updated to bootstrap 3.0.3 and tried to cancel jsn-bootstrap which caused dual bootstrap load(while %90 of the jsn-bootstrap code does what bs already does) on front end since it was also depending on bs 2’s responsive_css.

    I’ll try to fork the github repo for those if I can ??

    Thanks again for the awesome plugin!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Using wp_editor instead of wysiwyg’ is closed to new replies.