Hi,
I have installed Test Link 1.7.2 in Redhat linux using XAMPP 1.65 . I successfully installed, but unable to login. After entering admin username and password, URL is changing to
http://localhost/testlink/login.php?note=expired . I have created a new user and while trying to login , same result. I'm using PHP 5.2 and Apache 2.2.6 and MYSQL. Pls help me out to solve this issue.
Regards
Arun
Unable to login to Test Link 1.7.2 in Linux
Moderators: Amaradana, TurboPT, TL Developers
Any ideas on this one? I am running into the same issue when I upgrade from my working 1.7.1 deployment to 1.7.3?
I wonder if it might be related to this post?
http://www.teamst.org/phpBB2/viewtopic.php?t=759
Thanks,
-Dave Johnson
I wonder if it might be related to this post?
http://www.teamst.org/phpBB2/viewtopic.php?t=759
Thanks,
-Dave Johnson
Grrr.... I just don't get it...
http://ip/testink-1.7.1 works but http://ip/testlink (which is 1.7.3) doesn't.
I should have mentioned that my situation is slightly different then Arun's, he mentioned he actually gets the login page. I noticed that my 1.7.1 deployment does redirect to this expired session URL so that seems to be a good thing, the difference with me is that I get a blank page.
My previous posted questioned if it was related to another post questioning PHP sessions, I am still not sure if that is the problem. I md5sum'd the php scripts in the testlink root directory and ./lib/functions directory and most are identical between 1.7.1 & 1.7.3. And the ones that are different don't seem to be related.
Any ideas on why I am seeing a blank login page. I just noticed this forum post which is identical to what I am seeing, http://www.teamst.org/phpBB2/viewtopic.php?t=692
Further searching the forum I found these two posts which mention PHP session save path value.
http://www.teamst.org/phpBB2/viewtopic.php?t=254
http://www.teamst.org/phpBB2/viewtopic.php?t=524
The thing that confuses me is why the heck does 1.7.1 work and 1.7.3 doesn't. I have deleted caches/cookies and 'chmod 777 /var/lib/php/session' still not luck. I have used different machines and I always get a blank login page. Grrr!
BTW, my configuration... Fedora Core 5, php 5.1.6 (maybe I need to upgrade?), apache 2.2.0-5.1.2, mysql-5.0.27-1
Enough ranting. Any help/insight/comment is greatly appreciated. Can you tell I want to run 1.7.3?
http://ip/testink-1.7.1 works but http://ip/testlink (which is 1.7.3) doesn't.
I should have mentioned that my situation is slightly different then Arun's, he mentioned he actually gets the login page. I noticed that my 1.7.1 deployment does redirect to this expired session URL so that seems to be a good thing, the difference with me is that I get a blank page.
My previous posted questioned if it was related to another post questioning PHP sessions, I am still not sure if that is the problem. I md5sum'd the php scripts in the testlink root directory and ./lib/functions directory and most are identical between 1.7.1 & 1.7.3. And the ones that are different don't seem to be related.
Any ideas on why I am seeing a blank login page. I just noticed this forum post which is identical to what I am seeing, http://www.teamst.org/phpBB2/viewtopic.php?t=692
Further searching the forum I found these two posts which mention PHP session save path value.
http://www.teamst.org/phpBB2/viewtopic.php?t=254
http://www.teamst.org/phpBB2/viewtopic.php?t=524
The thing that confuses me is why the heck does 1.7.1 work and 1.7.3 doesn't. I have deleted caches/cookies and 'chmod 777 /var/lib/php/session' still not luck. I have used different machines and I always get a blank login page. Grrr!
BTW, my configuration... Fedora Core 5, php 5.1.6 (maybe I need to upgrade?), apache 2.2.0-5.1.2, mysql-5.0.27-1
Enough ranting. Any help/insight/comment is greatly appreciated. Can you tell I want to run 1.7.3?
Today I decided to take another look at this and decided to run the install on a fresh database just to see what happens.
Turns out that the gui/templates_c directory wasn't writable and was causing all of my issues.
Why is that directory packaged read only if the installation requires it to be writable? Sounds like a bug to me but there could be a valid reason.
Turns out that the gui/templates_c directory wasn't writable and was causing all of my issues.
Why is that directory packaged read only if the installation requires it to be writable? Sounds like a bug to me but there could be a valid reason.