• Resolved David

    (@davidjrojas)


    After upgrading to WordPress 4.1, the visual post/page editor is not loading. The text editor works fine. I have gone through extensive troubleshooting and ruled out most other solutions I’ve found on the web from other users experiencing similar issues.

    Upon first inspection, there are 403 Forbidden errors for the content.min.css and skin.min.css files located in wp-includes/js/tinymce/skins/lightgray folder. So I logically conclude that this is what’s causing the visual editor not to appear. However, all file/folder permissions are correct, as well as file and folder ownership. I checked with out host (Pair Networks) and they were not able to find any issues on the server-side that could be causing the problem.

    I have gone through all standard troubleshooting steps (deactivating themes/plugins) as well as manually deleting the WordPress system files and re-uploading fresh ones to no avail.

    The only thing I have found to get it working again is to downgrade to version 4.0. Obviously, this is not the best solution.

    WordPress team: can you please either give some input or look into a possibly bug issue here?

    Thanks in advance!

Viewing 15 replies - 1 through 15 (of 36 total)
  • Moderator t-p

    (@t-p)

    try a few basic troubleshooting steps:
    – Flushing any caching plugins you might be running, as well as server and/or browser caches.
    – deactivating ALL plugins temporarily to see if this resolves the problem (plugin functions can interfere). If this works, re-activate them individually (one-by-one) to find the problematic plugin(s).
    – If that does not resolve the issue, try switching to the unedited default Twenty Fifteen Theme for a moment using the WP dashboard to rule out any theme-specific issue (theme functions can interfere like plugins).
    – If that does not resolve the issue, try resetting the plugins foldervia FTP or SFTP or whatever file management application your host provides. Sometimes, an apparently inactive plugin can still cause problems.
    – If all the above steps do not resolve the issue, then try MANUAL updating. Download a fresh copy of the WordPress .zip file to your computer, unzip it, and use that to copy up all files and folders EXCEPT the wp-config.php file and the /wp-content/ directory. You may need to delete the old copies of files & folder on your server before uploading the new ones. Read the Manual Update directions first.
    If you haven’t already done, always backup everything (including your database) before doing any actions, just in case something really goes wrong.

    Thread Starter David

    (@davidjrojas)

    Tara, thanks for taking the time to reply. However, as I mentioned in my original post, I have gone through all these basic troubleshooting steps. I’m hoping a WordPress specialist can get back to me regarding this, as I am suspicious of a deeper, code-issue with WP.

    Upon first inspection, there are 403 Forbidden errors for the content.min.css and skin.min.css files located in wp-includes/js/tinymce/skins/lightgray folder.

    First, check to see if those files exist on your server.

    Thread Starter David

    (@davidjrojas)

    First, check to see if those files exist on your server.

    Yep, those files do exist. I even manually deleted the WordPress system files (except wp-config.php and the wp-content folder), then uploaded fresh copies from the WordPress download.

    Moderator t-p

    (@t-p)

    Thread Starter David

    (@davidjrojas)

    try reviewing this codex: https://codex.www.ads-software.com/Using_Javascript

    Thanks, but I’m not sure how reviewing this codex would help. As I also said before, I have tried switching to just the default WordPress theme, as well as disabling all plugins.

    I’m having the same issue. I upgraded from 4.0 to 4.1 on a multisite install. The visual editor does not work on any of the sites.

    Here are the steps I have taken:

    • disabled all plugins- didn’t help
    • changed to default theme- didn’t help
    • Upload fresh copies of wp-admin, wp-includes, and all root files (with the exception of wp-config.php)- didn’t help
    • I even tried uploading copies of the 4.0 wp-admin, wp-includes and root files, but that didn’t help either.

    Unfortunately, my copy of the DB backup did not happen correctly. (Long story…. my failure though).

    Is there any fields/values in the DB that would affect the display of the visual editor?

    Moderator t-p

    (@t-p)

    @jonbius,
    To get full attention to your specific issue, my suggestion would be to start your own thread. Despite any similarity in symptoms, your issue is likely to be completely different because of possible differences in physical servers, accounts, hosts, plugins, theme, configurations, etc. Thus one problem, on one setup is not indicative of the functionality and reliability of an application as a whole. To get the best attention to your specific issue as you deserve, please review how and where to post in this forum: https://codex.www.ads-software.com/Forum_Welcome#Where_To_Post

    Thread Starter David

    (@davidjrojas)

    It would be great if this thread would get some responses from WP associates as well. This is a significant issue which has left the site useless on 4.1. Are there any experienced WordPress professionals here who could provide some insight?

    Thanks! I created a new thread.

    Hi, David.

    I ran into this exact same problem with my site, also hosted on Pair. After a good amount of digging, I found that the core issue was that a number of the JS calls that pull up the visual editor were returning 403, and it apparently had something to do with the query strings appended to the calls.

    Anyway, I contacted Pair support, they responded thusly:
    “I believe that this was likely caused by an emergency fix that was put in place to stop a PHP vulnerability in May of 2012. I’ve commented out the emergency fix, which has been patched, and I can now view the contents of that file.”

    And I’ve verified that the visual editor now comes up. You may want to contact Pair support as well.

    I’m commenting to hopefully revive this thread for some attention as I’m having the same issue and have tried the same troubleshooting steps. Mine doesn’t work with any theme, either.

    While I don’t believe commenting out a vulnerability fix is the answer, improbablejulia, could you find out specifics of what the fix is (name, article talking about it, etc) so others of us not using Pair can ask our domain hosts about it?

    From Pair support:

    “Back in 2012 there was a massive PHP vulnerability that was
    discovered that was present in all versions of PHP, both current (for May
    2012 current that is) and all previous versions. Information on this bug
    can be found at the link below.

    https://bugs.php.net/bug.php?id=61910

    When the bug was discovered, there were no immediate patches
    available. As a work-around, pair Networks gave every domain we host
    special lines in an .htaccess file to secure users against this issue.
    About a week after the bug was discovered, patches were available and all
    versions of PHP on our servers were updated, but the .htaccess file lines
    were left in place as they were not causing any issues.

    As PHP has long since been patched, these lines are no longer
    needed, so commenting them out (disabling the specific lines) poses no
    threat to security.”

    Moderator t-p

    (@t-p)

    mikeulator@,
    to get full attention to your specific issue, my suggestion would be to start your own thread. Despite any similarity in symptoms, your issue is likely to be completely different because of possible differences in physical servers, accounts, hosts, plugins, theme, configurations, etc. Thus one problem, on one setup is not indicative of the functionality and reliability of an application as a whole. To get the best attention to your specific issue as you deserve, please review how and where to post in this forum: https://codex.www.ads-software.com/Forum_Welcome#Where_To_Post

    Tara, I’m aware of that, but as I stated in my original comment (in the first sentence), I’m wishing to draw attention to THIS thread… not start my own. Many folks, like me, will be searching for this issue and this was one of the top results in google. I’d rather they continue to come here and (hopefully soon) find an answer.

Viewing 15 replies - 1 through 15 (of 36 total)
  • The topic ‘Visual Editor Not Working in WP 4.1’ is closed to new replies.