Revolution 2.0.0 Login Issues

We made a fresh install with the latest MODx Revolution 2.0.0 and everything was going along smoothly until MODx decided it had enough and won’t allow us past the manager login screen.

We type in the administrator username and password, click on Login, then it just loads the login screen again with the username and password fields as blank.

I have no idea what is causing the problem and we’ve tried the following:

• Completely Clearing Browser Cache (IE and FireFox)
• Checking the DB for blocks in [prefix]users_attributes
• Resetting password in the DB with a MD5 function in [prefix]users
• Trying the forgot password link
• Clearing all sessions from the DB
• Removing all the cache from the entire site
• Checking the error.log file which has no recent errors

We’ve been searching relentlessly for a solution to this problem and we cannot find any solution. Is there thing which we could try!? I really don’t want to re-install, especially considering we’ve been spending an entire week populating the site with resources and now this.

We are running a CentOS 5.4 machine which has XAMPP for Linux 1.7.3a installed that has Apache 2.2.14, MySQL 5.1.41, PHP 5.3.1 and other stuff running, so we do have to correct version of MySQL.

Try emptying completely the core/cache directory. You might be out of space.

Have done that and we around 990GB free drive space left on the machine...

Are you sure no configuration changes were made to either the server (PHP, MySQL, etc.) or the MODx settings when this just stopped working?

Ok, I’ve just spoken to one of the team members who remember changing a system setting, but not sure what exactly He ’thinks’ it was something with friendly url’s, which system setting from the friendly url setting would cause this? Or could rather?

I have an idea... how can I reset the system settings table?? Or where can I find the default values?

After getting the default settings from a fresh install on my machine, I was able to identify automatic_alias as the culprit in this tale

Thanks for the concern though

Quote from: EvoBunny at Jul 27, 2010, 04:43 PM

After getting the default settings from a fresh install on my machine, I was able to identify automatic_alias as the culprit in this tale

Thanks for the concern though

Hmmm... I wonder what impact automatic_alias would possibly have on MODx Manager login?

Do you know what the value was changed to that caused the issue? What did you change it to to correct it?

Quote from: pixelchutes at Jul 27, 2010, 04:55 PM

Quote from: EvoBunny at Jul 27, 2010, 04:43 PM

After getting the default settings from a fresh install on my machine, I was able to identify automatic_alias as the culprit in this tale

Thanks for the concern though

Hmmm... I wonder what impact automatic_alias would possibly have on MODx Manager login?

Do you know what the value was changed to that caused the issue? What did you change it to to correct it?

Yeah, I’m not following how this would affect manager login either.

Quote from: EvoBunny at Jul 27, 2010, 04:43 PM

After getting the default settings from a fresh install on my machine, I was able to identify automatic_alias as the culprit in this tale

Not sure how it explains it, but this change certainly worked for me!

automatic_alias value field was empty in the system_settings table. I set it to 0 and I was able to login again.