Visual editor not working after 4.2.3 upgrade

I think you misunderstand, it’s not the WordPress install that is being rolled back, read the link I posted, it’s security tools inside Plesk but as I have stated, they then get re-initialised after successful loading of the Visual Editor.

My site WordPress install had been updated to 4.2.3, that is the point, this is where the error started, NOT before.

Caches were cleared as a first port of call, this achieved NOTHING.

4 different devices running 4 different browsers all showed the same issue, cannot have been such a huge coincidence.

I am new to WordPress but not to Web design & tech and it seems that WordPress need longer beta testing before implementing upgrades and causing endless grief for the client.
This update 4.2.3 proves that point, a security fix, obviously overlooked in 4.2.2

I wish people would read ALL the post before jumping in ??

Does anyone know of a fix for this issues for sites hosted on Bluehost (clearing my cache did not fix the problem? Can I use that same fix that was suggested for Plesk?

Thanks

@nacragun

Don you use Plesk as the Admin interface to your webspace?

If so then contact your host and point them to the link that I have posted, outlining you issue.

If you do not use Plesk, then this fix is not for you but I can only assume that there are similar security tools for other Admin interfaces such as cPanel etc….

Hope you get it sorted or WordPress pulls their finger out their butt and employs another fixed update

Clearing cache does not fix for me either.

@1cm69 I spoke with my host about a cPanel fix for this yesterday. They had no solution. Suggested I go back to WordPress forums…

Thank you for your help. The tech support at Bluehost was able to fix the problem for me.

@nacragun

Thanks excellent news ??

@1cm69

Thanks for posting your link above. I did all of the things that Bob suggested and I still had no editor.

However, I looked at my error log in cPanel and it said that post.php had it’s permissions set to 664. I changed it to 644 and I suddenly have an editor to use! Hurray! I can now do my job!

Called Blue Host. They told me to deactivate all plug-ins and add them back one at a time.
I did and my text came back. I even updated and viewed each time, because I had lost text before when I did that even if it showed up to begin with.
I added ALL of the plug-ins back in and there weren’t any offenders, so it’s a mystery.
Just happy that I can finally get some work done!
Hope it works for y’all.

Tried that (deactivating plugins) and still nothing.

Did this get anywhere? I’m running WordPress on AWS EC2 and having the same issue. Here are all my files in that directory:

ls -lhas

Shows:

total 548K
4.0K drwxrwsr-x  7 apache www 4.0K Jan  7 14:32 .
4.0K drwxrwsr-x 11 apache www 4.0K Dec  8 23:45 ..
4.0K drwxrwsr-x  2 apache www 4.0K Dec  8 23:45 langs
 28K -rw-rw-r--  1 apache www  26K Apr 11  2011 license.txt
4.0K drwxrwsr-x 24 apache www 4.0K Dec  8 23:45 plugins
4.0K drwxrwsr-x  4 apache www 4.0K Dec  8 23:45 skins
4.0K drwxrwsr-x  3 apache www 4.0K Dec  8 23:45 themes
324K -rw-rw-r--  1 apache www 321K Nov 17 23:19 tinymce.min.js
 16K -rw-rw-r--  1 apache www  15K Jul  1  2015 tiny_mce_popup.js
4.0K drwxrwsr-x  2 apache www 4.0K Dec  8 23:45 utils
148K -rwxrwxr-x  1 apache www 146K Nov 17 23:19 wp-tinymce.js.gz
4.0K -rwxrwxrwx  1 apache www 1.2K Jan  7 14:32 wp-tinymce.php

Any thoughts??

Why did you give the wp-tinymce.php file 777 permissions?

Change it back to the proper 644 permissions, like it should be. If you’re running various security add-ons, such as mod_suhosin or similar, then having a file with 777 permissions will actually prevent it from being run.

I just set it back to 644 for that file – must have been something else. Thank you for your input.