Think I figured it out. Under my user, the option to proofread every post when first created and updated was checked. For some reason it was proof reading and not allowing the post to be published. After unchecking these options it seems to be working…for now at least.
Thank you so very much! This nonsense drove me nuts for a couple hours, because all at sudden after upgrading to WP4.0 we weren’t able to update any posts on a client’s site.
The errors in the console seemed to point to tinyMCE as I could see the error message “Uncaught TypeError: Cannot read property ‘getRng’ of undefined” in Chrome while was getting “TypeError: n is undefined” or something like that (can’t exactly remember) in Firefox.
As it turns out even when everything is working correctly tinyMCE is plagued with warnings and errors which are then shown in the Browser’s console. That’s is very much misleading since actually this was a functionality that got broken by the update where apparently when the admin has those flags set in the user account, will render publishing and updating functionality completely unresponsive as they will fail silently without reporting why to the admin… at the very minimum a warning stating that a mandatory step (proofreading) hasn’t been performed and should offer a choice between performing and publishing/updating and ignore and publish/update.
If you had not shared your experience here (thanks again for doing that!), I would still be stuck as there is no mention of this issue and fix anywhere on WordPress documentation… shame on the team for breaking working installs and for not providing any support in that regard… hopefully they’ll take note and improve where they’re still very weak.
