• Resolved Stephan Whelan

    (@stephan-whelan)


    I’ve got a weird one. Just upgraded to WP 5.0 and Classic Editor 1.3. The editor/tinyMCE would be blank on page load with the following in the console:

    Failed to load resource: the server responded with a status of 403 ()

    Did my standard debug technique of deactivating all plugins apart from Classic Editor. On testing in an incognito window the editor would load on first pageview, however on refresh the editor would disappear.

    Any ideas on what might be happening? We’ve rolled back to 4.9.9 WP to avoid this issue for now.

Viewing 7 replies - 1 through 7 (of 7 total)
  • @stephan-whelan I have not run into this issues and use TinyMCE boxes everywhere on some of our sites. It’s definitely a file permissions issue though. What hosting company are you with? Sounds like a common run-in I’ve had with sites on Cloudways if you ever ran the reset permissions tool. You may need to contact your hosting provider to run a batch chown against the WP directory to the proper user. If you’re a sudoer on your own server/vm then you would need to check and run that yourself. Hope that helps.

    Plugin Author Andrew Ozz

    (@azaozz)

    Please see https://www.ads-software.com/support/topic/text-is-blank-when-editing-pages-posts-or-woocommerce-products/. Seems the same issue, wp-tinymce.php is blocked by some misconfigured “security” measure.

    Thread Starter Stephan Whelan

    (@stephan-whelan)

    @aedelgod – we’re on WP Engine – might be a file permission thing but let me chat to them and see what they say.

    Thread Starter Stephan Whelan

    (@stephan-whelan)

    Spoke to WP Engine. The issue is trying to access this file: https://www.deeperblue.com/wp-includes/js/tinymce/wp-tinymce.php

    They reset permissions on the files but nothing worked. They suggest it is a core product issue which I don’t agree with.

    Any other ideas folks?

    Plugin Author Andrew Ozz

    (@azaozz)

    In previous threads some users reported they had an .htaccess file that blocks access to that file. Can also be cause by some WP security plugins, need to whitelist it there.

    A final workaround would be to add define( 'SCRIPT_DEBUG', true ); to wp-config.php. That will slow down loading of all js and css but should fix this as then WP will load all TinyMCE scripts one by one and not use wp-tinymce.php.

    Thread Starter Stephan Whelan

    (@stephan-whelan)

    Looks like there was a .htaccess file in wp-includes that had a deny all in there, removed that and it’s fixed! Thanks everyone

    Plugin Author Andrew Ozz

    (@azaozz)

    Glad you fixed it. Thanks for letting everybody know.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘TinyMCE 403 on Classic Editor’ is closed to new replies.