• Since our blog has been moved to Cloudfront the tinyMCE editor just doesn’t show up. According to our server admin the blog install is, “on a standard ec2 instance with cloudfront in front of it but not caching anything but static content”.

    Also, it’s running on nginx.

    We did a fresh WP install, and only replacing our config file and wp-content from back up. I didn’t include the plugins to check if they were the problem. Still no tinyMCE.

    I’ve Googled this quite a bit but nothing has worked or the fix doesn’t apply to our server config.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The first step is to use the developer tools in Firefox (or Firebug) or Chrome or Safari or IE to see if you’re getting a 404 for any files, if there is a Javascript conflict with other scripts, etc., then go from there.

    And try Debug and see what PHP errors you are getting. See https://codex.www.ads-software.com/WP_DEBUG

    Add

    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );

    in wp-config.php and the debug.log file will be in wp-content.

    Add this line

    define( 'WP_DEBUG_DISPLAY', true);

    to wp-config.php to log and also dump them to the browser.

    Thread Starter fiftydonboise

    (@fiftydonboise)

    Thanks, so for Firebug console is clear and I can see the debugging coming through the php log and the only thing that seems halfway interesting is this NOTICE: “The called constructor method for WP_Widget in MP_Authors_Widget is deprecated since version 4.3.0! Use

    __construct()

    instead.“.

    Not sure how I’d fix that, but I guess it’s worth looking at.

    Thanks

    That’s just a php notice, not an error, and you can ignore it for now. Ask the server admin to look in the ec2 logs and see what’s there.

    Thread Starter fiftydonboise

    (@fiftydonboise)

    Thanks I’ll do that, but something strange is going on.

    I’ve put error logging in wp-includes/class-wp-editor.php. In the method parse_settings(). The method is being called twice when I refresh the new post editor. Both times the function user_can_richedit() returns false. I’m looking at the DB table user_meta and ‘rich_editing’ column is set to true for all users.
    <?>

    Thanks

    Thread Starter fiftydonboise

    (@fiftydonboise)

    The other variable ‘self::$this_tinymce’ is also showing false, without this being true, the tinyMCE editor won’t show.

    If I force this variable to be true, the editor shows up but the content gets converted to HTML entities and is useless as a post.

    I’m stumped.

    – Don

    Do you have an exception in Nginx for wp-includes/js/tinymce/wp-tinymce.php ?

    Thread Starter fiftydonboise

    (@fiftydonboise)

    Do you have an exception in Nginx for wp-includes/js/tinymce/wp-tinymce.php ?

    I don’t know, I doubt there is anything that specific in the nginx conf, let me check with the admin.

    Thanks,
    Don

    You might be subject to this issue:
    https://core.trac.www.ads-software.com/ticket/29159

    Adding something like this to your theme’s functions.php might resolve it for desktop users (however those on mobile devices (phone/tablets) may have various other issues with the wp-admin as this fix doesn’t cover all cases):
    https://dtbaker.net/web-development/rich-textvisualwysiwyg-editor-does-not-work-in-wordpress-behind-cloudfront/

    Thread Starter fiftydonboise

    (@fiftydonboise)

    The dtbaker fix did indeed work.

    Thank you for replying to my post!

    – Don

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Since move to Cloudfront WordPress tinyMCE not displaying’ is closed to new replies.