Upgraded from WP 3.3 to 3.3.1 and upgraded themes as well (Brunelleschi, 2011 and 2010). Lost all options when rolling over admin menu, e.g can't access Appearance/Editor. Tried the following:
Disabled all plug-ins, changed theme to 2012 standard, cleared firefox cache, no difference.
Upgraded firefox to 9.0, no difference.
Even tried the expanded admin menus plugin, no difference.
I'm not a WP or CSS expert so I'm hoping there's an easy to understand solution to this? Thanks in advance for any solutions offered.
Suse.
[closed] Lost functionality of admin menus in 3.3.1 (40 posts)
-
Susebb
Posted 4 months ago # -
Chrome Orange
Posted 4 months ago #I'm seeing the same problem in IE9, Firefox and Chrome, the hover menus have gone - they still expand though.
the screen options and help tabs are not working either after I upgraded
I have cleared caches and cookies etc in all browsers.
-
Posted 4 months ago #Yep, same problem in Chrome and can't get menus to expand at all. Also, have no screen options or help tabs working now. Additional problem is now can't move any widgets from Available widgets to widget areas. I really hope someone has the magic answer to all this!
-
Posted 4 months ago #Just tried the widgets and I can't move anything either :(
-
Posted 4 months ago #ok, just updated another copy of WP on a different server and that works so it's not WP but something in the update has caused one of my installs to stop working as it should.
Off to look at what changed from 3.3 to 3.3.1
-
Posted 4 months ago #OK, my problem is a plugin.
-
Posted 4 months ago #Can I ask which plugin causes the problem?
-
Posted 4 months ago #it was one I'm writing :)
there is something in my jQuery that is upsetting the admin menus
-
Posted 4 months ago #What do you think I could look at to try to figure this out for me?
-
Posted 4 months ago #I've just found my error using the Google Chrome console
(open the admin in google chrome, right click and choose 'inspect element', now choose the 'console' tab and (hopefully) you will see an error there that you can fix)
If there is an error, post it here and I'll see if I can help
If you don't have chrome then you can use firebug in FireFox (you will need to install this)
-
Posted 4 months ago #Uncaught SyntaxError: Unexpected token ILLEGAL load-scripts.php:2
Uncaught ReferenceError: jQuery is not defined akismet.js:1
Uncaught ReferenceError: jQuery is not defined brunelleschi-options-scripts.js:1
Uncaught ReferenceError:jQuery is not defined index.php:98
Uncaught ReferenceError:jQuery is not defined load-scripts.php:19
Uncaught ReferenceError:jQuery is not defined index.php:550
Uncaught ReferenceError:jQuery is not defined indx.php:611 -
Posted 4 months ago #does this help?
http://wordpress.stackexchange.com/questions/30282/uncaught-syntaxerror-unexpected-token-illegal
(obviously this is local host)
Also, have you tried reinstalling WP ? It might be as simple as a corrupt file
-
Posted 4 months ago #load-scripts.php was one of the files that was changed from version 3.3 to version 3.3.1
-
Dave333
Posted 4 months ago #So is there a simple solution? I don't understand the reply on that link you gave.
-
Have you tried:
- deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).
- switching to the Twenty Eleven theme to rule out any theme-specific problems.
- resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.
- re-uploading the wp-admin and wp-includes folders from a fresh download of WordPress.
-
Posted 4 months ago #Dave33
Esmi is correct and if all that fails use the console info I posted earlier to try and spot the error
(open the admin in google chrome, right click and choose 'inspect element', now choose the 'console' tab and (hopefully) you will see an error there that you can fix)
If there is an error, post it here and I'll see if I can help
If you don't have chrome then you can use firebug in FireFox (you will need to install this)
-
Posted 4 months ago #Chrome Orange, can you please elaborate on those instructions?
Open Admin in Chrome
Right-click - where?? I guessed and right-clicked in the widget area and it gave this error:event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.
I'm not sure if that makes any sense to you.
-
Posted 4 months ago #if you go to the admin section of your website (http://www.YOURDOMAIN.com/wp-admin) and login while using the Google Chrome browser.
Find some clear space in the browser window and right click.
Now choose 'inspect element' from the context menu that opens (if you don't see this then find a different spot and right click again).
The screen will split in half horizontally and in the bottom section you choose the 'console' tab and (hopefully) you will see an error there that you can fix).
-
Posted 4 months ago #Also, did you follow Esmi suggestions? Based on my experience this afternoon this is a jQuery error and will either be something you have added to WordPress or a corrupted file during the update.
-
Posted 4 months ago #Thanks Chrome Orange, I understood you the first time. It's just that you didn't state where one needs to right-click. So I took a guess and chose the problem area - the widgets and right-clicked there. I posted the results for you:
event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.
I have no idea what that means.
But while I was in the console I noticed there was mention of the Podpress plugin - it had also thrown an error. So I disabled it and re-enabled it and everything works fine again now.
Yes I did try Esmi's suggestions first but it didn't help.
As I told Esmi in the other thread. I have no idea which one of these things was responsible for getting the website working again. If it was the Podpress plugin then why wasn't the problem solved when I deactivated all plugins in an earlier troubleshooting attempt?
Also, if the Podpress plugin was responsible for the fault, why has the fault not returned now that i have reactivated it?
Perhaps it was a combination of things in a certain order, like I said, i have no idea.
-
Posted 4 months ago #Actually, I spoke to soon. It's broken again and it's actually worse than before. Now I have lost the Header widget entirely. I'll keep prodding (three hours so far) and if I manage to get it working I'll post here.
-
Posted 4 months ago #I've turned off Podpress again but didn't see any change. So I emptied the cache. Now my widgets work again.
-
Posted 4 months ago #A quick google of this error
event.layerX and event.layerY are broken and deprecated in WebKit
suggests you are using jquery 1.6 (http://stackoverflow.com/questions/7825448/webkit-issues-with-event-layerx-and-event-layery)
I haven't seen any where that you have re-uploaded the wp-admin folder?
I have just installed PodPress on a test site I have and haven't seen any problems (although looking at the other thread the problems seem to occur if you update to 3.3.1 after installing PodPress)
-
Posted 4 months ago #Above I wrote:
Yes I did try Esmi's suggestions first but it didn't help.
Yes, that included the wp-admin & wp-include folders.
Yes, I already had Podpress installed BEFORE upgrading to WP 3.3.1
Thanks for the link but it only said where to download it from. Where do I instal it?
-
Posted 4 months ago #what error messages do you get if you run the Chrome console on the admin home page?
-
Posted 4 months ago #Do you still get problems if you use internet explorer? WordPress doesn't use event.layerX anywhere that I can find so it's either a theme, a plugin or I found a link that said that error can be due to a Chrome Extention
-
Posted 4 months ago #If I click in the white space on the Admin dashboard I get no error.
I don't have Internet Explorer installed. I use mainly Safari, Firefox and Chrome.
-
Posted 4 months ago #And you still get the same problem in Firefox?
Do you have problems with the admin menus on all admin pages?
The console only gives the error you pasted above on the widget page?
-
brightonmike
Posted 4 months ago #Have you tried a complete clean fresh install of WP with none of your plugins, uploads or themes?
If you're worried about losing anything, create a sub-directory and create a fresh install. Test for the problem.
Presuming it's not there, start adding your plugins and themes one-by-one. This install of WP won't have your posts/pages but that doesn't matter, you're just doing this to identify the plugin/theme responsible.
-
Posted 4 months ago #
Topic Closed
This topic has been closed to new replies.
