After instalation login doesnt work

[pedrotuga]

Ok, i have just finished the instalation...
everything looks ok, expect i cant login.
I tryed several times... it just doesnt work.
The default site is running on the server perfectly.... what da heck can it be?

[KevinK]

I had the same problem the last couple of days. Actually did 3 clean installs in a row and STILL it would not let me in. It is very annoying as I tend to forget passwords but I knew I could not forget a password in literally 5 minutes AND I actually wrote down everything I typed in also. I think it might be adding a space or return character to the entered password during the install...

Found this in a thread in here and tried it and it let me in:

"Change your password in cms_users to 21232f297a57a5a743894a0e4a801fc3.  Then login with the password of admin.  Change it to something else after you login."

See if it works for you...

KevinK

[red raven]

I had the same problem om my apache testbech. I've tried several CMS systems, and configured the directives for the drupal cms system. One of the requirements for drupal is that you must set session.savehandler = user in the php.ini file. This file is most likely located in /etc/php4/apace2/ directory.

With the session.savehandler set to this I was not able to display the loginpage. So I (accidently) set it (a bit) wrongly back to session.savehandler = file. Then the loginpage shows up alright, but I could not login anymore and had the same probem as you( I think; if username or pass is wrong, then an error message is displayed, if no errormessage we have the same problem....).

summary:
The session handler should be set like :
session.savehandler = files

(note the last 's' in 'files'. Easy to mix things up here....  )

[Chris..S]

There is a bug, its double hashing your chosen password before it stores it in the database.

If you can execute,

SELECT md5('your chosen password');

copy the value.  Using phpmyadmin or other mysql client, goto the user table, browse it and edit the one row.  Paste in your value from above to replace the value that's in the database.

[pedrotuga]

Currently i am using windows.

chris i will do as u say... but, btw... can u explain what does that query do?

I am used to the sintax

Code: Select all

 slect #### from #### Where ####

[pedrotuga]

There is a bug, its double hashing your chosen password before it stores it in the database.

If you can execute,

SELECT md5('your chosen password');

copy the value.  Using phpmyadmin or other mysql client, goto the user table, browse it and edit the one row.  Paste in your value from above to replace the value that's in the database.

Ok, the encripted code i got was the exact same i had before.
I will try another sugestion

[pedrotuga]

I had the same problem om my apache testbech. I've tried several CMS systems, and configured the directives for the drupal cms system. One of the requirements for drupal is that you must set session.savehandler = user in the php.ini file. This file is most likely located in /etc/php4/apace2/ directory.

With the session.savehandler set to this I was not able to display the loginpage. So I (accidently) set it (a bit) wrongly back to session.savehandler = file. Then the loginpage shows up alright, but I could not login anymore and had the same probem as you( I think; if username or pass is wrong, then an error message is displayed, if no errormessage we have the same problem....).

summary:
The session handler should be set like :
session.savehandler = files

(note the last 's' in 'files'. Easy to mix things up here....  )

So... either u cant see the login page or u cant login.... that means that this problem has no solution?

[Chris..S]

I happened to install CMS:MS three times today.  Once to check it out, using the latest subversion code, then my real install & my test copy.  In all three occasions I couldn't login after running the install script and each time I had to pasted in my own md5 hash of my password before it would work.  After the third time I checked the code and sure enough, the code indicated it being double hashed.

I confirmed that by doing...

Select md5(md5('mypassword'));

the result was identical to the hash stored as a password for the one use in the user table.

If that doesn't solve things for you I don't know what it could be - I'm only new here

[pedrotuga]

Solved!!!!

Noone of those worked... so i remember the good old law:

"The hardware is allways right."

well, in this case the software, lol.

I cheked md5 encoded password and it was correct...i set the cookies on... still nothing working...

then i thought.. "LET'S TRY SHUTING DOWN ZONE ALARM", yes, I am using windows, the  modem doesn't work with linux. So... it worked!!!!

Now the question is: what should I set on zonealarm configuration in order to have it on and run CMS?

greetz

[Ted]

Very very strange.  CMSMS only needs cookies enabled to use the admin.  The rest is basic html. 

As a Mac user, I don't know anything about Zone Alarm, though. 

[red raven]

I had the same problem om my apache testbech. I've tried several CMS systems, and configured the directives for the drupal cms system. One of the requirements for drupal is that you must set session.savehandler = user in the php.ini file. This file is most likely located in /etc/php4/apace2/ directory.

With the session.savehandler set to this I was not able to display the loginpage. So I (accidently) set it (a bit) wrongly back to session.savehandler = file. Then the loginpage shows up alright, but I could not login anymore and had the same probem as you( I think; if username or pass is wrong, then an error message is displayed, if no errormessage we have the same problem....).

summary:
The session handler should be set like :
session.savehandler = files

(note the last 's' in 'files'. Easy to mix things up here....  )

So... either u cant see the login page or u cant login.... that means that this problem has no solution?

In short:
In the php.ini file the option session.savehandler must by set to files otherwise you can't log in.
However this is on a Linux platform.

[red raven]

I not shure what your problem might be and my recommendations will just be guessing. My conclusion for my problem was how the server side store so called "sessions". This is how it keeps track of your identity after you log in. It store on part of an identity on the server and another one on your computer. Perhaps zonalarm does not allow you to store cookies ?

[kida]

Long time reader, first time installer..

I'm having the same problem as discussed above and after reading this thread I am still none the wiser..

Is there a consensus as to what the primary problem is - a php setting? Hashing in front of the password? I don't use zone alarm so that aint it for me.

Any help from those more familiar with this app would be greatly appreciated.

ps: very elegant little cms folks