Support Forum
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.
YELLOW
SWORDFISH
|
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:
YELLOW
SWORDFISH
|
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?
Visit Cruise Talk Central and Mr Papa's World
confused as to what the original problem was then if everything is working fine... but happy if so...
Visit Cruise Talk Central and Mr Papa's World
1 Guest(s)