It was a Wednesday. I reached my office at 9.30 am. After going through the mails and logging into Skype, I checked the issues in bug tracker. There wasn’t many, but stillT a few GOOD ones. Ctrl + T and first 3 letters of domain URL + Enter Key led me to the Typo3 Backend of the website. As the username and password were already saved, I again pressed Enter Key but didn’t succeed – usual for any Typo3 site. So once more…, no. Once more…., No. I typed the username and password. Again NO. Hacked??? No, it’s not possible as it’s a local setup hosted in our server. I asked others to login. Their login details also not working. Then I visited the frontend pages, couldn’t find anything wrong. But still Something has went wrong somewhere. I checked database ‘be_users’ table and re-entered the password manually. The values entered are getting encrypted. Now let’s go for the usual method – GOOGLE…!!! Google helped me, it gave me the hint needed – check ‘be_sessions’ table. I checked the ‘be_sessions’ table and found that it’s corrupted. I used the ‘Repair table’ option and tried to login again. Success!! I got logged in to the Typo3 backend. Thanks Google!
- What makes the database table corrupted?
A server crash.
Server hardware failure.
A MySQL bug.
- What is the use of ‘be_sessions’ table?
Every typo3 backend user has his own session and those session data are stored in the database table be_sessions.
So I can suggest you 3 options to check if backend user login is not working:-
- Try again. Try againn..
- Check your username and password.
- Check whether the database table ‘be_sessions’ is corrupted or not. If corrupted, then repair it and try to login again.
- I would be really glad if I can write a 4th one also, but fortunately or unfortunately for me the problem got solved at step 3. Please help me to write the 4th ie, something not mentioned here.