WordPress.org

Forums

[resolved] [closed] TinyMCE broken using Visual Composer (8 posts)

  1. purplearth
    Member
    Posted 1 year ago #

    Using WP3.9beta3 and Visual Composer (v3.7.4 or 4.0.4):

    Editing content in the normal WP editor window seems to work as advertised.

    Editing text in a wysiwyg window of VC is horribly broken (and yes, we do have a support ticket to the plugin author). HTML tags are rendered in visual mode (even <p> tags, which don't show in text mode), text is white on a white background, the button bar doesn't show up, and edits are not applied in VC 4.0.4. Maybe the "visual" rendering/styling isn't being applied properly?

    We see reports of similar problems affecting the Advanced Custom Fields plugin:
    http://support.advancedcustomfields.com/forums/topic/wp-3-9-breaks-wysiwyg-editor/
    http://support.advancedcustomfields.com/forums/topic/wysiwyg-toolbar-not-showing-no-js-errors/

    TinyMCE seems to be a common thread in the difficult interaction between WP3.9 and some very important and popular plugins. Hopefully this will be fixed before release, otherwise many sites will break.

    Thank you.

  2. Visual Composer's paywalled, so we can't guess at that one for you.

    http://codecanyon.net/item/visual-composer-page-builder-for-wordpress/242431

    You can try using your browser to figure out the errors: https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors

    ETA: This MAY be because jquery-ui-dialog is no longer enqueued by default. On RC1 you should get an error message in the console.

  3. chris@vendiadvertising.com
    Member
    Posted 1 year ago #

    Thanks Mika, the developer says he's looking into this so that's good.

    They have a blog post saying they just hit 20,000 sales so there is a pretty sizable install base. They are often packaged within themes, too. Unfortunately the average user will think "the WordPress update broke my stuff" when 3.9 lands.

    We aren't receiving any errors in the console or apache logs and we've tried enqueuing jquery-ui-dialog but that didn't fix anything.

    Our symptoms are the exact same as ticket #27601 which is why we thought we'd post here. We get white text on a white background and the markup is plain text with HTML tags (not rendered). We can provide access for debugging if anyone wants to try it.

  4. Hello Chris,

    We can provide access for debugging if anyone wants to try it.

    You should do it by yourself and report the issues back. :)

    TinyMCE received a major update, to version 4.0. Any editor plugins written for TinyMCE 3.x might require some updates. (If things broke, we’d like to hear about them so we can make adjustments.) For more, see TinyMCE’s migration guide and API documentation, and the notes on the core development blog.

  5. chris@vendiadvertising.com
    Member
    Posted 1 year ago #

    Thanks Dominik, that's actually why we posted here! :)

    We've debugged as far as we could to no avail. We were hoping someone more familiar with TinyMCE could find some weird bracket rule equivalent like in 27601 (needle in a haystack, I know). This will be the first time that we'll have to delay a WP update.

  6. Andrew Ozz
    WordPress Dev
    Posted 1 year ago #

    text is white on a white background, the button bar doesn't show up...

    This indicates that TinyMCE was not initialized. What you're seeing is the plain textarea without any editor. There is usually an error in the browser console that would give hints about what's wrong.

    Generally TinyMCE would fail initialization if it cannot load a plugin or translation file (shows as a 404 error), or if there are other JS errors on the page. Also, the first error is usually the culprit, any following errors are most likely caused by it.

  7. nathanstaton
    Member
    Posted 1 year ago #

    Just wanted to confirm that I am having the same issue on WP 3.9 with Visual Composer. I first noticed the issue with white type on the white background which I fixed with a simple function call to the admin_head,

    function name_of_function_call() {
       echo '<style type="text/css">
               .js .tmce-active .wp-editor-area{color: #000000!important}
               </style>';
    }
    add_action('admin_head', 'name_of_function_call');

    But after not seeing the WYSIWYG editor and not being able to see any difference after clicking "visual" or "text" in the visual composer text editor I knew there was some sort of bug going on. I've tried further debugging per what Ozz recommends but I'm not getting any js errors in the console.

    This is very frustrating to deal with when you have a site going live. Anyone else have any ideas?

  8. giselleaz
    Member
    Posted 1 year ago #

    Everything seems to have been fixed with the latest 3.9 update.

Topic Closed

This topic has been closed to new replies.

About this Topic