Magento

mrbigint,

First check your root folder to make sure it is set to 755 (not 777).

Secondly, if you do not have access to SSH to follow my instructions above you can:

1) Download the Magento cleanup tool here
2) Unzip it to the root of your Magento installation
3) Browse to it (http://mydomain.com/magento/magento-cleanup.php)

It will try and set all of the permissions (minus the root directory obviously) as well as clearing up various the various caches.

Lastly, if you are still having problems, see what happens if you rename .htaccess to something else (like .htaccess.bak)

skippybosco - 24 April 2009 04:56 PM

mrbigint,

First check your root folder to make sure it is set to 755 (not 777).

Secondly, if you do not have access to SSH to follow my instructions above you can:

1) Download the Magento cleanup tool here
2) Unzip it to the root of your Magento installation
3) Browse to it (http://mydomain.com/magento/magento-cleanup.php)

It will try and set all of the permissions (minus the root directory obviously) as well as clearing up various the various caches.

Lastly, if you are still having problems, see what happens if you rename .htaccess to something else (like .htaccess.bak)

Hey, I uploaded and ran the script, it cleared the problem up, it now takes me right to the install wizard. Chhers!

Awesome, glad to hear it!

I ran accross this thread trying to figure out why I was getting 500 Internal Server Error everytime I was proceeding to checkout (I still wonder what that screen looks like as I have never gotten that far). I started with a clean install of 1.3.1 and have beating my head against it for a couple weeks now - aarrgg.

Decided to try the cleanup.php and got this result:

----------------------- CLEANUP START -------------------------

*************** SETTING PERMISSIONS ***************
Setting all folder permissions to 755
Setting all file permissions to 644
Setting pear permissions to 550

****************** CLEARING CACHE ******************

************** CHECKING FOR EXTENSIONS ***********
-= WARNING =- Overrides or extensions exist in the app/code/local folder
-= WARNING =- Overrides or extensions exist in the app/code/community folder

------------------- CLEANUP COMPLETED in:0.0176 seconds ------------------

Now I cannot access Admin back end at all. I even clicked on Forgot password to get a new one but still cannot access because of “invalid username or password”. I suspect there must be a cookie issue??

PLEASE - Any suggestions?

first of all you should look in your apache error.log to see what is the reason of this 500 error.

Thanks for the reply Samm. Do I have access to that file from my host? The only time I see the 500 error is when trying to go to checkout - otherwise everything seems ship shape.

I searched the log files for ‘500’ and this is an example of the entries there:

[26/Apr/2009:01:16:56 -0400] “GET /online/checkout/onepage/?___SID=S HTTP/1.1” 500 5 “-”

“Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.9) Gecko/2009040821 Firefox/3.0.9”

I read that it can matter if www is used in the base url or not. I have changed all of the secure and unsecure base url’s to have ‘www’ although I still couldn’t get past the 500 errors when Proceeding to Checkout. Is this related to the session ID?

Meanwhile, back at the farm - I still can’t access Admin after running cleanup tool…

All the cleanup tool does is clear your cache and set the permissions of your files, nothing that would affect your admin userid/password. Assuming your host is a typical setup then directory permissions of 755 and file level permissions of 644 would be appropriate. If not, depending on your site configuration, adjust the values in the script and re-run.

Is this a local installation or a remote installation? If local, there is a known issue where you must use a full qualified domain name (ie. localhost will not work) so either http://127.0.0.1/magento or add a local host entry for something like mydomain.com and access via that manner.

There is also known issues (search the forums here on login issue for admin) where invalid timezone settings (local / remote) causes the cookies to not be valid and prevents logging in so you can check that.

As far as the 500 error, I notice you have local and remote extensions (overrides).. is it possible that one of them is causing the problem?

skippybosco - 26 April 2009 04:26 PM

All the cleanup tool does is clear your cache and set the permissions of your files, nothing that would affect your admin userid/password. Assuming your host is a typical setup then directory permissions of 755 and file level permissions of 644 would be appropriate. If not, depending on your site configuration, adjust the values in the script and re-run.

Is this a local installation or a remote installation? If local, there is a known issue where you must use a full qualified domain name (ie. localhost will not work) so either http://127.0.0.1/magento or add a local host entry for something like mydomain.com and access via that manner.

There is also known issues (search the forums here on login issue for admin) where invalid timezone settings (local / remote) causes the cookies to not be valid and prevents logging in so you can check that.

As far as the 500 error, I notice you have local and remote extensions (overrides).. is it possible that one of them is causing the problem?

skippybosco - Thanks for your input. It’s a remote installation. I cannot log in using the dedicated ip+path either. I had all the cache disabled so now I can’t log in as a subscriber now. I’ve tried logging in as a subscriber, and Admin from Firefox, IE7 and Chrome, to no avail.

Is there a way for me to clear the cookies info on the host DB? Any ideas about the location of the cookie info?
I’ve been trying to fix and configure this puppy for a couple of weeks - Would ‘invalid timezone’ be a factor here?
About the remote extensions, I have no clue what those may be. I’m relatively sure I didn’t install any. Sounds crazy - I know.

Thanks!

There are not server side cookies, there are sessions that are stored in your magento/var/session folder.

There are a number of threads on various things folks have run into:

http://www.magentocommerce.com/search/results/?q=admin+login+invalid+1.3

Some of the more common are the timezone issue I mentioned, the fully qualified domain name issue and an issue where session validation is causing problems..

So many threads, so little time . I think I screwed this up by setting the cookie domain incorrectly. I just read that the proper structure/syntax is .domain.com, and I didn’t do it that way. I was experimenting with whatever seemed remotely plausible. There is so much guesswork for a rookie like me! If only F1 worked!

If I can repair the cookie domain entry, I should be able to atleast get back to the 500 errors and delete the unexplained extensions. Any thoughts? Thanks for your help, and your time on these threads.

I believe that data is stored in the Magento database, specifically in the core_config_data table.

If you have PHPMyadmin, open that table and look for the web/cookie/cookie_domain and web/cookie/cookie_path values. You can simply delete these entries (that should be enough).

After you delete the values you will need to clear your browser cookies and restart the browser. Before trying to login to admin you will also need to clear your magento/var/session files, and potentially magento/var/cache depending on your setup.

Give it a try and let me know how it goes.

Things must be badly corrupted because even my hosts’ phpMyAdmin won’t load. I decided to ditch this installation and try another host. I signed up with Nexcess.net (as someone else on the board suggested). I’m liking it alot because everything seems to work without much tweaking. I will need to search around the boards to see why the PayPal sandbox is returning the “We cannot process this transaction because there is a problem with the PayPal email address supplied by the seller” error. Otherwise, the cart is working like a dream. I Love it!
Thanks for your suggestions skippybosco.

OMG!!!!!

you saved my mental health with your post!
I’ve been spending the last 2 days installing, reinstalling, chmoding, banging my head on the walls, becoming nuts with magento!

....and the cleanup file saved me

thank you soooooo much (you should get a medal )

cheers

Laurence

skippybosco - 24 April 2009 04:56 PM

mrbigint,

First check your root folder to make sure it is set to 755 (not 777).

Secondly, if you do not have access to SSH to follow my instructions above you can:

1) Download the Magento cleanup tool here
2) Unzip it to the root of your Magento installation
3) Browse to it (http://mydomain.com/magento/magento-cleanup.php)

It will try and set all of the permissions (minus the root directory obviously) as well as clearing up various the various caches.

Lastly, if you are still having problems, see what happens if you rename .htaccess to something else (like .htaccess.bak)

Glad to hear it. Go out and build something great with it!