8 replies to this topic

[vw53a]

As of yesterday we cannot access the manager. The site itself seems to be working fine, I can access the files via ftp, but accessing site.tld/manager/ gives an error 310: Too many redirects.
Does anyone have any clue as to what happened here? I've asked my host if they have changed anything and am waiting for their answer also. But maybe this behaviour rings a bell with any of you experts. Thanks in advance.

[vw53a]

Turns out my host had to change the configuration of my database. Therefor they changed the username cq. databasename. They have changed this also in the config.inc.php file so the site should work. Well the site does, but not the manager. I'll have to check where the name is stored elsewhere. ...this evening, cause meanwhile my lunchbreak is over.

[Ralph]

Contact your host and ask them if they have upgraded to PHP 5.3.x as that is the most common reason for existing sites to stop working correctly... I haven't run into any instances of MySQL being the reason other than data corruption issues, aside from perhaps once or twice over the past several years...

[vw53a]

php is version 5.2.13
mysql is version 5.1.46
according to phpinfo.
Don't know if that's something they've changed though. Will ask.

[vw53a]

Just found out that when renaming .htaccess in the manager folder makes the manager accessible.
It is the standard .htaccess file that came with 0.6.final and contains only

RewriteEngine Off

php_value session.cookie_lifetime 483840
php_value session.gc_maxlifetime 483840
php_value upload_max_filesize 8388608

Some testing shows that the RewriteEninge Off line is still okay, but any of the given php_value lines will stop the manager from being accessible.
Is it usefull to investigate further or can I leave these three lines out without giving it a second thought?

Edited by vw53a, 17 May 2010 - 08:05 PM.

[PaulD]

Hi,

I am no expert, but would suggest that deleting these might be a problem in the long run.

A quick google of session.gc_maxlifetime indicates to me that it is quite important. Cookie lifetime is probably less so and max file upload, if your users are not uploading images, you can take care of by being careful. However the maxlifetime cleans up session data, but will probably be set by the host in php.ini anyway. If I was you, and I am NOT an expert, If all seems fine I would leave them deleted and see what happens (and I back up like a back-up crazy OCD patient so would suggest you back up now too, while everything is still working).

Are you running the old version of eto? If so I would also upgrade as a matter of some urgency.

Hope that helps,

Paul.

[Ralph]

I haven't checked yet but I don't recall any php_value settings in the original .htaccess file... In fact, some servers gag if they are found, as you have discovered... Your host most likely did some server upgrades which caused the sudden problem..

Nope... Just checked and the .htaccess file in the manager/ directory should be:

RewriteEngine Off

[vw53a]

Thanks Paul,

I'm running the old version as the site is scheduled for ... ehm, well deletion actually. For some years now, though, but we're in the final stages of merging two sites/domains into one. So as long as the current/old one isn't broken, I try not to fix it .

This evening my host has sent me a php.ini file which I may edit and place in the manager folder. A little addition to the .htaccess file should then override the default php.ini file with the one in that folder. I'll dive into that later.
Also my host has admitted that among the changes were new versions for PHP and MySQL . Just not PHP5.3.x
One other change is that our database is now added to the daily backup. Yea!

[vw53a]

Ah Ralph, you've just beaten me to it.
The lines are in the file in version 0.6.1-final, they're not in version 0.6.1.4
I'm not sure though which version is newer.
If there's no harm in leaving them out, I'll not bother trying to get my head around a php.ini file.