I had the same issue going from 1.1.2 to 1.1.3, everything seemed to stop working from the navigation standpoint. Also, the errors were continously popping up in Firebug.
So what I did was go to the js/ folder in the main shop and make sure it was 755. Then go inside and make sure js/index.php was set to 755, this seemed to make everything function correctly.
During the upgrade I think a lot of files have went to different CHMOD.
Thanks again Magento, you are great! I hope that I can contribute to other newbies that have issues as much as you veterans have helped me!!!!
I was anxious to fix this menu issue according to the posts on this thread, but I don’t see a proxy.php in the js directory???? Can anyone comment? Is that file no longer part of 1.1.3 or is the fact that it’s missing part of my problem? The Magento team needs to consider putting some error handling into the admin backend to give administrators a clue where to start when this happens. I saw the post from one of their team members saying every server is different which I get, but it would be awesome to have some sort of idea where to begin. Just a thought. In the meantime if someone could tell me whether or not the proxy.php file needs to be there, I would appreciate it.
Same issue here. We have installed the latest version - Magento ver. 1.1.3. and admin drop down menus are not not working. We have done the following with no results -
Replace the - Head.php file
Chmod “755” - /js but there’s no proxy.php in /js so we Chmodded index.php to “755”
Ok guys! I found the trick! I was on 3iX and it has to do with files and folder permissions! (it was not resolved by the 1.0 release)
Using filezilla, I changed recursively all files permissions to 644 and 755 for folders (which took some time as you may imagine), and right after, everything worked fine!
Thanks for that piece of info! I think this should be checked for during the install.
If you can ssh into your server, here’s the command to do this recursively (from within the base directory of all the magento files):
find ./ -type d -exec chmod 755 {} \; && find ./ -type f -exec chmod 644 {} \;
In the middle of tearing my hair out whilst dealing with all of the other complications of Magento, the admin menu craps out. I would get it if it happened right after an upgrade/install, but not seemingly random and out of the blue.
Let me be clear.
Installed 1.1.3 - new, clean. Adminning along.... SHAZAM! Loss of function of admin menu.
Changing permissions on the /js/index.php file to 755 fixed… for now.
What hurdle will you throw at me next while I try to deliver projects to clients with you, Magento?
I’m experiencing javascript errors like the ones described here.
Basically - If refresh a page and it’s cache (ctrl+F5) everything works okay, fresh that page or revisit it and it gives “… not defined” errors. I made a screencast of it last night.
i had all the correct chmod settings and was still broken so i’m stoked someone worked this out.
maybe they should put this in the install guide, “your navigation in the admin panel is probably going to break rendering your magento useless, especially if you install an extension or a theme. the instructions for the fix is to read through pages and pages of forum posts and if you dig deep enough and after much trial and error you should find this post and it should work for you, but hey, no promises”
I hope this doesn’t come across to sarcastic but i was ready to smash something or through my computer against the wall....