Upgraded drupal 6.11 to 6.26 with drush - works fine but now login access denied

Posted by kmoney on June 13, 2012 at 4:19pm

Hi,

as mentioned above I upgraded from drupal 6.11 to 6.26 (newest) using drush.

Everything worked fine, however, if I log out now, I can not login again with any of the admin accounts.

I always get access denied with all accounts (passwords are correct and restting them does not help).

Any ideas for help?

THANKS
kmoney

Comments

It is usually a cookie

Posted by John_B on June 14, 2012 at 6:27pm

It is usually a cookie handling problem on browser or server (assming you are not getting a message about failed login attempts or something). Hard to see how it is related to the upgrade.

If you are absolutely certain you did nothing else apart from updating, then I would be tempted to roll back to backup and re-run the update. Changes to settings.php sometimes cause a problem, but the update with drush should not have done this.

Digit Professionals

I'm having a similar issue

Posted by Milkrow on June 29, 2012 at 9:41pm

I'm having a similar issue where now I'm getting the WSOD. I tried to upgrade to 6.26, but it wouldn't update because of some conflict with theme.inc (Fatal error: Call to undefined function user_access() in /includes/theme.inc on line 992). Line 992 refers to the Search module. I cannot determine where to go from here. Any ideas?

Sounds like a bug in your

Posted by John_B on June 30, 2012 at 9:55am

WSOD and access denied are separate problems, so your post does not relate to the rest of the thread in my mind but I will answer it anyway.

Sounds like a bug in your theme. Change default theme to Garland, disable your current theme, and run the update. Then re-enable your theme. Or maybe disable search module in case that is causing the problem. Not guaranteed to work but worth a try as the quick and easy possible fixes.

Sometimes clearing caches and running cron clears these problem. It could be the search module (or theme) have been hacked and Drupal's cache are still reflecting the hacked code. Now you have overwritten any hacks, the does not work until the cache is cleared and cron is run, at which point Drupal database 'discovers' that the hacks / modifications have been removed. Of course, if you rely on those hacks for the appearance of your site, your modifications have been lost. But hacking is not the right way to modify a site... Just guessing here.

Take a new site backup including database backup just in case your preferred theme does not work with the updated site, so you know how would restore your site if there is a problem. If you are struggling you can always restore from the backup.

Digit Professionals