[Solved] Problems logging in to upgraded CMS instance

[djn62]

I'm having trouble logging in to the administration panel of CMSMS and I'm hoping someone can help.

Here's my scenario:

I have a production instance of CMSMS v1.2.5 deployed and am having no administration problems with it.  My site is running with MySQL 5.0.67 and PHP 5.2.5.  Can't seem to find what version of Apache is being used, nor the OS details, though I know it is Linux.

I am planning to upgrade to CMSMS v1.5.2, so I set up a test machine running Fedora 8, with MySQL v5.0.45, PHP 5.2.6-2, Apache 2.2.6-3.  I installed CMSMS v1.2.5, exported the MySQL data from my production system, imported the data into my test system, tweaked a few config parameters (to deal with port number and URL diferences) and successfully got it up and running as expected. 

I then overlayed the CMSMS v1.5.2 files onto my v1.2.5 file structure, logged into the admin area, and pointed my browser to the install/upgrade.php script.  The upgrade process appeared to complete successfully, including upgrading the database schema to support the newer version of CMSMS (don't remember the schema versions unfortunately).  I renamed the install directory to install.save until I knew I wouldn't need it any more.

All the data seems to be served up fine from an end-user perspective, but I can no longer log into the admin area after the upgrade.  I'm using the same username/password(s) from the production instance, and reviewing the content of the cms_users table confirms all the user data is present.  However, it responds with "Username or password incorrect".

I obviously can't deploy this to my production server until I figure this out.  Any suggestions?

Thanks in advance for any advice....

[djn62]

Okay, I figured this one out. 

After I installed my original production instance, I renamed my admin directory to something else for security reasons.  When I overlayed the 1.5.2 files over y 1.2.5 installation, I had *two* admin directories (the 1.2.5 renamed admin dir, and the new 1.5.2 admin dir).  I didn't update my config file to point back to the *new* admin dir.

After fixing this up, I'm able to log in fine.