Page 1 of 1
Successfull login redirects to login page
Posted: 02 Mar 2005, 01:20
by elifarley
I have Mantis 0.19.2 installed under FreeBSD 5.3. I used to use it normally, but all of a sudden I cannot get past the login screen anymore.
If I supply an incorrect password, I'm redirected to
http://localhost/mantis/login_page.php?error=1
(which is normal). But if I supply correct user name and password, I'm redirected to
http://localhost/mantis/login_page.php? ... n_page.php
What's happening ?
Thanks.
Posted: 02 Mar 2005, 10:53
by vboctor
Do you have the cookies enabled?
Regards,
Victor
http://www.futureware.biz
Posted: 03 Mar 2005, 10:48
by elifarley
Yes, cookies are enabled (I'm usign Firefox, BTW).
Posted: 03 Mar 2005, 10:53
by vboctor
- Try logging with another browser (eg: Opera).
- If the other browser works, try removing the cookies relating to the Mantis website that you are trying to login to, and try again with FireFox.
Regards,
Victor.
http://www.futureware.biz
Posted: 03 Mar 2005, 19:27
by elifarley
Logging in with Opera made no difference. What could be wrong here ?
Posted: 07 Mar 2005, 08:37
by LIAM
I hope I'm not hijacking this thread but want to highlight that I am encountering similar error that elifarley is encountering. I have tested Mantis on my windows machine with Apache and all works fine using IE and Firefox.
However, after uploading to my virtual server which is running on BSD 4.10 and trying to login, the page is redirected continously to login_page.php
For your information I am testing my files on a subdomain, I hope this doesn't make a difference.
I think an answer to elifarley problem will most likely my solution too.
Thanks,
LIAM
Posted: 07 Mar 2005, 21:00
by lance
After deleting my cookies I now get the recursive redirect to login_page.php too. If I log into version 0.19.0 in order to create the cookie I can then log back into 0.19.2, but I can't log into 0.19.2 directly without cleaning out my cookies. Ugh.
does this fix your problem?
Posted: 08 Mar 2005, 07:52
by ed
Posted: 09 Mar 2005, 20:31
by elifarley
Changing the function 'current_user_is_anonymous' did not solve my problem.
I think my problem and the one pointed out are unrelated.
Should I open a new bug ?