I upgraded to version 7.2. When working on trying to get CKFinder to work, as admin, I chose the Settings menu button. At that point the system denied access, asking me to put in my uid and password. They are not valid anymore. After choosing the 'forgot password' function and clicking on the link in the mail the page went back to "access denied" mode.
Restored to previous version but still no access.
Help..
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | excerpt_db_dump.txt | 1.6 KB | harri00413 |
Comments
Comment #1
vm commenteduid is a number, have you checked the user table for uid 1 and the associated user?
Comment #2
webchickHm. Which version did you upgrade from? 7.0? Or 6.x?
And yes, a peek at your users table could be very informative.
Comment #3
harri00413 commentedHi,
I upgraded from 7.0, all went well, no errors on the updating of the DB.
The plot thickens, I now don't have access to my databases through PHPMyAdmin at my provider. So I can't look at the database directly. Probably have to download it to check it out, or start from scratch... It's a "practice site" (harland.tk), so not much harm done, just some hours wasted.
Btw, the "request new password" gives the "Not enough rights for this page" (or equivalent from the Dutch message) when clicking the link in the received email.
I am the only user "Frank Harland" and have uid 1. From the excerpt from the dump that is attached, I think I can see that...
Just hope it isn't a Drupal Issue.
Cheers,
Frank
Comment #4
webchickSorry, I have absolutely no idea what this could be. :\
The only database-related change to that table between 7.0 and 7.2 was a change to the default value in the uid field so it matches the schema of D6. But your uid 1 record exists, and looks fine.
I guess let's leave this open and see if we get any other reports.
In the meantime, you can try resetting your password this way: http://drupal.org/node/1023428
Comment #5
vasna sdoeung commentedI got the same issue too.
Oddly enough, i was able to login the first session after the upgrade to 7.2 last night. In the morning, i attempted to login back into the site and it didn't give any login errors. After a few more tries to login, it was still unsuccessful. So i decided to reset the password, got the email, follow the one time login link. Clicked on the login button, after a few moments, a access denied showed up.
Comment #6
vasna sdoeung commentedI found out what it was.
It had to do with Fatal error: Class 'ctools_export_ui' not found in a panel module class, see http://drupal.org/node/1139732. It prevented me from logging in. I posted a short term solution to it.
Comment #7
webchickThanks. Cross-linking #1098696: Panels mini: fatal error in the Panels queue. Could you follow-up there? Developers generally don't read the forums, and need to be informed of bug reports via the issue queue.
Comment #8
paulgemini commentedHere's a temporary solution:
http://drupal.org/node/1139732#comment-4526448
Comment #9
cpelham commentedBefore I upgraded I scanned the list of changes but it was very long and nothing screamed out, changes are being made to the class registry so if you are using any modules that depend on it, know that they may break. Maybe I didn't read it well (i admit my eyes glazed over...) but it would be easier to make sense of if the changes were presented in order of significance (which begs the question, significant to whom, i know) rather than in chronological order. That way we could better anticipate problems rather than just discover and react to them after the fact?
Comment #10
harri00413 commentedI restored the 7.0 version, not the database. There is no sites/all/modules/panels/... directory, however I remember installing a 'Panels' module to check it out (on the 7.0).
Today I opened my site from another PC and there I was logged in as admin. (only account) Of course I tried to log out and in again. Could not. System did not recognize my password.
Comment #11
marcvangendA similar 'class not found' error occurs in the Feeds module on Drupal 7.2. I think this is caused by files that need to be declared in the .info file in order to enable the auto-loading of classes. See #1169986-12: Fatal error: Class 'FeedsPlugin' not found.
If this is indeed the cause of all similar class not found errors, I guess this issue can be closed because it's not a problem in Drupal core.
Comment #12
harri00413 commentedSo what gives... back to 7.0?
Comment #13
webchickOk, some core developers hashed this out on IRC tonight, and I think this is now a duplicate of #534594: [meta] system info cache writing and registry rebuilding is broken without a full bootstrap, at least if it's caused by fatal errors due to classes not being found. A rollback of the offending patch has been committed to 7.x there.