Magento

GoodGBB - 04 May 2008 10:40 AM

For me I have solved this menu problem by doing the following tasks.

1. Upload the new Head.php (downloaded from this thread)
2. CHMOD /js to be 755 and /js/proxy.php to be 644
3. My menu is works!!!!

Thanks for all helping

Yeah! This worked for me, what a relief. Thanks for helping solve this problem. !!

Uploading the replacement head.php and then changing the permissions on js to 755 and js/proxy.php to 644 finally worked for me.

Many thanks to all who contributed to the thread.

This bug still exists in 1.0.19870

Replacing the Head.php in the core(!) an chmod 755 für /js/proxy.php doesn?t work for for me neither.

So I also have to edit the Head.php by hand like described her:
http://www.magentocommerce.com/boards/viewthread/4679/P30/#t17714

Now it seems to work. But im wondering, that this bug still isn?t fixed. Or is it just an error depending an my server configuration?

I too had the same problem and had to edit the head php as above and that finally fixed it…

I wish someone would make this note and sticky it till its fixed…

Tons of javascript errors for me on the front and backend rendering almost all menus inoperable.  As others have suggested “chmod 644 js/proxy.php” solved the issue.  That file was previously set to permission of 666 - perhaps that’s a sign? 

GoodGBB - 04 May 2008 10:40 AM

For me I have solved this menu problem by doing the following tasks.

1. Upload the new Head.php (downloaded from this thread)
2. CHMOD /js to be 755 and /js/proxy.php to be 644
3. My menu is works!!!!

Thanks for all helping

Solved my problem as well but I didn’t do anything to the head just changed the chmods.

Yizi - 26 June 2008 01:44 PM

GoodGBB - 04 May 2008 10:40 AM

For me I have solved this menu problem by doing the following tasks.

1. Upload the new Head.php (downloaded from this thread)
2. CHMOD /js to be 755 and /js/proxy.php to be 644
3. My menu is works!!!!

Thanks for all helping

Solved my problem as well but I didn’t do anything to the head just changed the chmods.

Im having the same problem.

just installed it and none of the top menu section work.

I have checked /js and it is already set at 755. I dont have a /js/proxy.php file? I only have a prototype.js

Can anyone help?

Change the folder to 755 and the files to 644 before the install.

Please help!

how can i resolved thos problem?

i cant believe this issue still exists. i had this problem with the previous installations and after applying Moshes head.php file and fixing the /js/ folder permissions was i able to fix this. I thought with 1.1 they would fix it but i had to do it again :(

@ jstein -

i cant believe this issue still exists. i had this problem with the previous installations and after applying Moshes head.php file and fixing the /js/ folder permissions was i able to fix this. I thought with 1.1 they would fix it but i had to do it again :(

Moshe - 14 April 2008 04:10 PM

@FOOMAN: From what I’ve seen, error 500 can be directly related to admin menus not unfolding, because this happens due to failure to load admin javascripts which are combined using js/proxy.php.

If you use Firefox/Firebug, you might see in Firebug/Net tab error 500 for all javascript connections.

chmod 755 js js/proxy.php

and see if it works.

whoa… for some reason, I dont even have the proxy.php file in my js directory!
Could someone post it’s contents or point me to a place where I could get it?

When I tried to access the admin panel as instructed by the documentation I got a 404 error and had to enter the following line to get to the admin panel.
http://www.example.com/Magento/index.php/admin/

The first time I tried logging in I got a fatal error. It worked the second time though. This makes me think that the software is not quite ready for prime time.

Changing /js to 755 solved the problem for me (running magento 1.1.2 on PHP 5 as CGI)

Jorg

raisinlove - 05 August 2008 03:20 AM

Moshe - 14 April 2008 04:10 PM

@FOOMAN: From what I’ve seen, error 500 can be directly related to admin menus not unfolding, because this happens due to failure to load admin javascripts which are combined using js/proxy.php.

If you use Firefox/Firebug, you might see in Firebug/Net tab error 500 for all javascript connections.

chmod 755 js js/proxy.php

and see if it works.

whoa… for some reason, I dont even have the proxy.php file in my js directory!
Could someone post it’s contents or point me to a place where I could get it?

Yes where is js/proxy.php?