• 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 - 16 through 30 (of 36 total)
  • I had the same problem with Visual Editor’s hyperlink not working. I tested all my plugins and discovered the problem for me was “Constant Contact”. I deactivated the “Constant Contact” plugin, then all works fine. I will now have to find a solution to have a Constant Contact form on my site that integrates with CC.

    Hope this may help someone else!

    Thread Starter David

    (@davidjrojas)

    @improbablejulia, thanks for your input! This solved the problem for me as well. I guess I just needed to talk to the right person at Pair Networks. ??

    @david, did you find out what the name of the vulnerability was or what they did? My host is not Pair Networks. Also, posting that info here may help WP folks get to the bottom of it in their code if they can.

    Thread Starter David

    (@davidjrojas)

    @mikulator, improbablejulia posted it above:

    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.”

    Here are the lines I removed from my .htaccess file.

    RewriteEngine on
    RewriteCond %{QUERY_STRING} ^[^=]*$
    RewriteCond %{QUERY_STRING} %2d|- [NC]
    RewriteRule .? – [F,L]

    The site I had the problem with was on Pair also.

    HTH

    @jonbius

    So, doing that, made your visual editor work again?

    ??

    Yes, birdog123, it sure did! We’ve since encountered a few more instances of that, and it fixed things straight away when we removed that code.

    Moderator t-p

    (@t-p)

    Glad you got it sorted and reporting it back ??

    Moderator t-p

    (@t-p)

    @deencoded,
    As you might have noticed this a “resolved” thread.

    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. So, 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

    Dear All,

    I too experienced these problems when I upgraded to WP 4.1.1 version.

    This is the solution I got so far. I downloaded the WP4.1.1 version from www.ads-software.com, opened its /wp-includes/js/tinymce/ folder and compressed to .zip
    On the cpanel I renamed the tinymyce folder to tinymyce2 and uploaded the zipped tinymyce file.
    After decompressing it, I refreshed both the cpanel window and one of the website( I manage several) and Viola! the Visual Editor was visible again on the posts. Also remember to delete the tinymyce2 folder on the cpanel once this works for you.

    Or you can choose to upload the JS folder as a whole too.
    I hope this helps someone else.

    PS: I had to give step by step illustration so that those who are not familiar with this can get it.
    Thanks.

    Please note if the No. 1 option does not work for you, consider replacing the whole JS folder(as a whole) as it did work for me on the other sites (that did not work with no. 1 option).

    Thanks

    Just a quick THANKS David, improbablejulia, and jonbius! Your troubleshooting with pair’s setup was invaluable – I’d been bogged down by this forever! Now fixed, removing these lines from my .htaccess file.

    RewriteEngine on
    RewriteCond %{QUERY_STRING} ^[^=]*$
    RewriteCond %{QUERY_STRING} %2d|- [NC]
    RewriteRule .? – [F,L]

    THANKS!!
    Scott (satisfied pair user since 1997!)

    @scottolson_byram ! Long time no see! ?? Another Pair buddy from 1997 here. And this is a “me, too” post for a broken WP 4.1 visual editor, and have spent the afternoon removing all of those emergency fixes. All are working fine now.

    You guys rock.

    I’ve been pulling my hair out for 2 days about the inoperable Visual Editor since upgrading to WP 4.1.1 and have sifted through dozens of red herring support tickets.

    I’m no Pair and removing that code solved the problem.

    thank you thank you thank you

    This solved my problem too. Thank you very much.

    In my case the .htaccess file contained only the problematic lines so I deleted the file and problem solved.

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