Please Log in to join the conversation.
Please Log in to join the conversation.
I recently had the same problem. What I discovered was that after the upgrade to Joomla 1.0.13 the secure MD5 hash creates this condition.
Here's how I solved it:
1. I went into my MySQL database on the host server using my db id and password. Looked up the "jos_user" file and edited the password field for my record. This is an MD5 hash so that is what has to replace it.
2. I went on the web and found a site that generates MD5 hash and entered a simple password like "admin". This generates the MD5 hash and I clipped and saved it to my clipboard. (Ctrl+C). I went back to the record in the db and replaced the MD5 hash that was there with the "admin" hash code (Ctrl+V) and saved it.
3. I entered this new password in the admin sign on and "Viola" I was back in the admin of my site. I went to User Admin and changed my password to what I really wanted it to be. This generates a new MD5 hash that is salted (you can tell because there is now a ":" in the MD5 code in the record in the database).
From now on a synchronized CD 1.1 and the Joomla 1.0.13 work well with the id and password and the site is more secure.
I hope this works for you, at least it did for me.
Regards, BT:)
Please Log in to join the conversation.
2. I went on the web and found a site that generates MD5 hash and entered a simple password like "admin". This generates the MD5 hash and I clipped and saved it to my clipboard. (Ctrl+C). I went back to the record in the db and replaced the MD5 hash that was there with the "admin" hash code (Ctrl+V) and saved it.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.