Bug #14690
closedcan't login under Windows
0%
Description
Tried to use 3.8.0beta1 with WinXP (SP2), but unable to log into backend. Tried with existing and new databases, setting admin password from install tool. BE doesn't accept password (browser independant). System uses PHP 4.1.2 and mysql 3.23 (from original Win installer package).
Either something is wrong or missing in the Windows package or it is a real bug??
Tested also on Linux, no problems there.
Regards
Jochen
(issue imported from #M1000)
Updated by Sebastian Kurfuerst about 19 years ago
Hi, do you have a different version of PHP in windows and linux? Greets, Sebastian
Updated by Jochen Weiland about 19 years ago
Yes, different PHP versions:
Linux: PHP 4.3.10
Windows: 4.1.2
Updated by old_clonedyke about 19 years ago
if using eAccelerator and the like: have you cleared all those cached files (session data as well) and all other caches?
that solved the problem for me.
greets
rainer
Updated by Jochen Weiland about 19 years ago
I am not using an accelerator with Windows and clearing cache etc. doesn't help. i also tried it with a freshly created database (as well as an imported one from 3.7), but no differences.
Jochen
Updated by old_gaumondp about 19 years ago
Saw somewhere that 3.8 needs PHP > 4.2
PHP 4.2.0 is 3 years old...
I'm running 3.8b2.1 on WinXP and PHP 4.3.10.
Updated by Sebastian Kurfuerst about 19 years ago
Have a look at bug 997, and in the dev list something was posted about this:
"This version doesn't work with PHP with smaller version than 4.2 because there is a functioncall (floatval) which
is avaiable from version 4.2!"
Maybe you can check if the admin user and pass is created with e.g. phpmyadmin- or you just try a newer PHP version?
Regards,
Sebastian
Updated by Jochen Weiland about 19 years ago
I thought bug 997 was fixed to make it work with PHP 4.1.x again. I don't have a problem with raising PHP requirements to 4.2.x, I was just concerned about people who used the Typo3 installer before which included PHP 4.1.2
Regards
Jochen
Updated by Sebastian Kurfuerst about 19 years ago
Yeah, that bug was fixed, but just in CVS, 3.8.0 beta2 contains the non fixed version.
Updated by Sebastian Kurfuerst about 19 years ago
the current bug should be fixed in CVS.