• Have experienced the problem with Chrome and Firefox.
    Script_debug did not fix the error.
    This is the error log I get in Chrome
    “7post-new.php:1 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
    post-new.php:334 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
    post-new.php:2481 GET https://kcsjcatholic.org/wp-includes/js/tinymce/wp-tinymce.php?c=1&ver=4109-20150505
    post-new.php:2483 Uncaught ReferenceError: tinymce is not defined”

Viewing 12 replies - 16 through 27 (of 27 total)
  • Moderator James Huff

    (@macmanx)

    Those permissions are fine. How about the permissions on the directories above?

    Thread Starter jakelivingston

    (@jakelivingston)

    Thread Starter jakelivingston

    (@jakelivingston)

    Moderator James Huff

    (@macmanx)

    Those are all perfect, which suggests that there may be a server-level security system blocking it. mod_security is pretty common, and it can be commonly set to overzealous proportions.

    I recommend contacting your hosting provider about this, and mention the 403 error on wp-tinymce.php specifically.

    Not to hijack the post once again. I’m sure we both appreciate your work James, especially as volunteer. In my case a last ditch third attempt at theme update seems to have fixed the editor problem. On other sites I run the editor took unusually long to load but it does load.

    Lesson learned on the content. My theme in question is paid-theme and with much depending on the Nivo image tools is likely outside the norm and a vendor support issue rather than WP.

    Good luck to you jakelivingston with your editor problem.

    Moderator James Huff

    (@macmanx)

    It’s great that you fixed your problem. A theme would have absolutely no effect on the wp-tinymce.php file, much less a 403 error, which is why we ask folks to open their own threads.

    Thread Starter jakelivingston

    (@jakelivingston)

    Have tried all suggested fixes and still not working.

    Moderator James Huff

    (@macmanx)

    So, what was the result of “I recommend contacting your hosting provider about this, and mention the 403 error on wp-tinymce.php specifically.” ?

    Thread Starter jakelivingston

    (@jakelivingston)

    I mentioned it to him. He did not see any security settings that would have caused that. I just turned visual editor off and it’s “working” in so far as I can now see what I’m typing.

    Moderator James Huff

    (@macmanx)

    Really? Your hosting provider didn’t see anything in the server’s error logs regarding the origin of the 403?

    Maybe it’s time for a new hosting provider.

    Thread Starter jakelivingston

    (@jakelivingston)

    I looked at the error logs and saw this. It’s German to me but maybe you understand it.

    client denied by server configuration: /var/www/vhosts/kcsjcatholic.org/httpdocs/wp-includes/js/tinymce/wp-tinymce.php, referer: https://kcsjcatholic.org/wp-admin/post-new.php

    Moderator James Huff

    (@macmanx)

    “client denied by server configuration”

    That’s the key right there. It means something on your server’s end, most likely a security system, is blocking the file.

    Your hosting provider will need to fix this for you.

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘Visual editor not working after updating to 4.2.2’ is closed to new replies.