-
☆ A M B ☆
- 237 Posts
O.k. Not sure what is going on here, but as the admin of the site and as my two other admins of the site can no longer login. When I try to login as the main admin - bpadmin, I get this message:
jdiprospero is currently editing these settings. Please wait until the other user has finished and try again.
Then it just kicks me out to the home page. I'm the main admin, shouldn't I always be able to login?
When I try logging in as jdiprospero I get this message:
bpadmin is currently editing these settings. Please wait until the other user has finished and try again.
So, what do I do now? Can I kill all the sessions from PHPmyAdmin? Is there another way around this?
I have never seen anything like it.
A few notes about this site. First, there was some custom programming on it that was hacked a few weeks ago. We removed all of the custom programming just leaving Modx 1.0.5 - then I updated to Modx 1.0.6 over the weekend. Everything seemed fine. Now today my client calls to tell me no one can login.
So, any thoughts out there?
-
☆ A M B ☆
- 237 Posts
Things seem to have gotten worse. Now I'm getting an internal server error 500 - Everything seemed to be working fine when I updated to Modx Evo 1.0.6 on Sunday. Now it's totally falling apart and no one has touched anything since then.
I'm desperate here. The site is no longer live.
-
☆ A M B ☆
- 237 Posts
Yes. It is solved thanks to gallenkamp. I didn't close this yet because I wanted to mention what I think may have happened. Not sure and I would like to hear some input from others.
After Guido helped me eliminate the active users using PHPmyAdmin, I was able to login as the admin. Right when I logged in it took me to the configuration page where I got a message saying because I just did an upgrade I should make any changes to the configuration and save.
Now, I updated the site a few days ago to 1.0.6 so this makes sense I guess. However, I don't recall it going to the configuration page when I did the update. Then no one could log in because the settings were being edited.
So, is it possible that I just didn't notice this the other day or that if you don't click save on the configuration page that it kind of got stuck there?
Maybe I'm over thinking it. I'm just glad that there are people like Guido out there trying to help. It was a fairly quick fix once he got me into the database.
Thanks again Guido.
Just had the same problem following my updates to 1.0.8
It only happens if:
- an admin made the update
- he/she did not save the configuration
- someone else tries to log in
Then both the admin and the other person are blocked.
The admin CAN log-on even if the configuration has not been saved, provided he is the only one to access the website.
The solution as said above: delete the session lines via PHPMyAdmin in the modx_active_users table.