Magento

hmm…

can you try this solution mention here..

[Fix] Product Link return 404 error; New category/product not showing up!
http://www.mtomto.com/108/fix-product-link-return-404-error-new-categoryproduct-not-showing-up/

Roly - 16 December 2008 07:51 PM

hmm…

can you try this solution mention here..

[Fix] Product Link return 404 error; New category/product not showing up!
http://www.mtomto.com/108/fix-product-link-return-404-error-new-categoryproduct-not-showing-up/

Thank you, but doesn’t work. ????

Yes, it is 50/50 chance since your problem occur in the backend rather than in the frontend..

I think you have an incomplete file upload or permission problem that caused the 404 error.. you may want consider re-install your magento again.

jmcneil - 21 November 2008 05:55 AM

SOLVED!

This worked for me and I hope it helps someone else. This is on version 1.1.7 so not sure if this will work on any other versions.

Directory /downloader/ set to 755
file /downloader/index.php set to 644

I use Cpanel and I had password protected the directory /Magento/ so that I wouldn’t have anyone stumbling on the site while it was being developed. I removed the password protection and the ‘Magento Connect Manager’ worked.

I figured it was something really simple but, for some reason this never occurred to me.

Thanks so much. I was looking for the proper permissions, you get them out of wack lol and its definitely a pain to get it back. Even being an old post. woot!

@theapokalypsis, If you are still struggling to get things back in whack, the Magento cleanup tool handles most of the heavy lifting in getting your permissions and such sorted out.

You can download it here:

http://www.magentocommerce.com/wiki/_media/groups/227/magento-cleanup2.zip

Unzip to the root of your Magento installation and then browse to http://yourdomain.com/magento/magento_cleanup.php and it will do the rest for you and provide feedback as to it’s progress.

downloader FOLDER 755
index.php 644

all you have to do

Thank you for this, I just encountered the same problem, and changing the permissions fixed it.

Thanks!!

This fix has worked for me also. I am a complete novice and managed to do it. Thanks all.

I am getting the same error.

Whoops, our bad…

The page you requested was not found, and we have a fine guess why.

* If you typed the URL directly, please make sure the spelling is correct.
* If you clicked on a link to get here, the link is outdated.

What can you do?
Have no fear, help is near! There are many ways you can get back on track with Magento Store.

* Go back to the previous page.
* Use the search bar at the top of the page to search for your products.
* Follow these links to get you back on track!
Store Home | My Account

This was the response which i am facing. Pls any one help me.

This fix has worked for me also. Thanks so much dudes.

jmcneil - 21 November 2008 05:55 AM

SOLVED!

This worked for me and I hope it helps someone else. This is on version 1.1.7 so not sure if this will work on any other versions.

Directory /downloader/ set to 755
file /downloader/index.php set to 644

I use Cpanel and I had password protected the directory /Magento/ so that I wouldn’t have anyone stumbling on the site while it was being developed. I removed the password protection and the ‘Magento Connect Manager’ worked.

I figured it was something really simple but, for some reason this never occurred to me.

This has worked for me too!
Thanks

Set all folders to 755

"Directory /downloader/ set to 755
file /downloader/index.php set to 644 “

this worked for me in 1.4.1

Thanks!

For me, when I went click the link on the Admin Panel, I get 404. Checked permissions and all were good. I just had to go to the downloader page manually by entering: downloader/index.php

Hope this helps someone out.

It’s almost funny in my case. In localhost it works although in the beginning it didn’t and in the web server it doesn’t work. I always get the 404 error in 1.4 no matter how I set permissions.

Finally I downloaded the clean up tool posted by skippybosco and it worked!

Maybe the problem is a combination of permissions and cache.