Is this following the update to Simple:Press 5.4.2? You do not say but I am going to assume so. If so there are already quite a few threads on this forum dealing with this. So… once again…

After updating WordPress to 3.9.0 and Simple:Press  to 5.4.2 – did you also update ALL of any other Simple:Press plugins you are using?

If yes- and the problem persists – then the likelihood is that you have a WordPress plugin that has not been updated for WP 3.9.0 and is causing issues. Some candidates that have been found by users so far include ‘wp-polls’, possibly ‘cforms’ and, in some cases, some plugins that use the Lightbox library.

This also applies to any WP plugin that in any way adds. removes or ‘interferes’ in any way with the TinyMCE editor. If it has not been specifically updated for WP 3.9.0 then it will cause issues.

WordPress made a lot of script changes in 3.9.0 including moving to a whole new version of the editor and to date we have found all issues have related to out of date WP plugins.

I’ve deactivated all plugins and the problem still persists. The button just links to javascript:void(null)

javascript:void(null) is exactly what it should be.

If all else fails then you really do need to use the script console. If you do not know how to do this then this wordpress codex article is a pretty good guide although the instructions for Firefox are out of date:

http://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors

this?

Consider using ‘dppx’ units instead of ‘dpi’, 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, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) (index):693
Uncaught TypeError: undefined is not a function pb-view.js?ver=1398299163:1
event.returnValue is deprecated. Please use the standard event.preventDefault() instead. www-embed-player-vflWfXjsU.js:29
Denying load of chrome-extension://elmdghkkehlmfllejpgikgpjgfalppei/lib/jquery-2.0.2.min.map. Resources must be listed in the web_accessible_resources manifest key in order to be loaded by pages outside the extension. (index):1
Failed to load resource: net::ERR_FAILED chrome-extension://invalid/
Denying load of chrome-extension://elmdghkkehlmfllejpgikgpjgfalppei/lib/jquery-2.0.2.min.map. Resources must be listed in the web_accessible_resources manifest key in order to be loaded by pages outside the extension.

Yellow Swordfish said

javascript:void(null) is exactly what it should be.

In the forum, I can’t add topic because it says javascript:void(null). In the topic, I can’t reply because it says javascript:void(null), but in the topic I can add a topic because it says /forum/problem-with-post-edit-buttonearthstone-general-1/?new=topic

So… should it say void null?

I got it to work. The code you told me to change in the other thread was the problem. Once I changed it back, everything that was wrong is now working again. For reference, the below quote is what you said to do.

 

wp_register_script( ‘custom_js2′,  get_template_directory_uri().’/js/jquery-ui-1.10.3.custom.min.js’,”,”,true);
wp_enqueue_script(‘custom_js2’);

to

wp_enqueue_script(‘jquery-ui-core’);

so its working normal like previous?  or now you can figure out which plugin is the problem?

It is working normally like previous. There is no plugin problem – just the code change was the problem.

confused as to what the original problem was then if everything is working fine… but happy if so…

Hi, Just jumping in on this as I’m having the same issue.

Started off great, but now seem to be unable to add new threads or reply to posts. Can’t tell if this is a code issue, and I’ve tried disabling ass my custom Css to no avail. Themes and plugins has been updated, disabled, tried it all.

http://www.reflexcreativearts.co.uk/forum/

We have had quite a few of these following the WP3.9 and SP5.4.2 updates. A lot of WP plugins have not been updated to correctly handle the quite extensive changes within WP and so far all problems have been traced to other WP plugins being out of date. This is, of course, also assuming you updated all of the SP plugins as well.

We have had reports of problems with WP-Polls, possibly cForms and any plugin using Lightbox. Also if you have ANY plugins that add features to TinyMCE editor in the admin that have n ot been specifically updated following WP 3.9 then they will no longer work and will cause breakage.

I can’t try running the editor as a non-registered user but I am seeing at least two errors just loading pages. These are shown in the screen-shot attached.

Whoops – sorry about the size. Damn retina display!

So – one error witj something called st_go which is clearly not loaded – I do not know what it is. And anopther to do with something called CookieControl. They are probably enough to stop the editor in the first place but might be hiding more going on.

I use Easy Video Suite and I just confirmed that disabling the EVS-WP plugin fixes this issue. Which is good info – but I can’t disable EVS or 100s of site videos won’t work! So for now I turned off the rich text editor and have contacted EVS to urge them to update their plugin to WP 3.9.

Thanks for all the great info in these threads that led me to identifying which plugin was conflicting. I hope it will be resolved soon!

you are welcome. glad to help.  wp 3.9 caught a lot of plugins by surprise…