PEAK XOOPS - Problem!! 
Problem!!
- You cannot open a new topic into this forum
- Guests cannot post into this forum
ufgeorge
Posts: 3
Posts: 3
Hi,
My XOOPS site works well before install Protector 3.3 beta.
After install Protector, it is ok at beginning.
But I don't know since when, each time I login, I can see "PHPSESSID=blebla" at the end of url.
And when I click anything in my site, XOOPS does not know who I am because there is no PHPSESSID in the URL.
If I manually add it to the URL, XOOPS would know who I am.
Rightnow I remark the two php in mainfile.php. But the situation still there. It drives me crazy. Can anybody tell me what's going on???
Update::
Since I can enter Admin area but cannot uninstall Protector module. So I enter MySQL and change isactive value of protector module to 0. And also remark the added 2 lines in mainfile.php. And also delete XOOPS_TRUST_PATH in mainfile.php.
And now I uninstall protector module succesfully. Uninstall process remove database table of protector.
I empty XOOPS_session table, delete files under template_c and cache folder. I also delete cache of IE.
Strange, the PHPSESSID still there!! Enter admin area to see modules, there is still a message "set XOOPS_TRUST_PATH into mainfile.php".
The only thing I did not do is delete the folder of trust path...
What's going on. Even uninstall still left something on my XOOPS??
How to remove it totally?
Or what did I do wrong?
TKS for any help!!
My XOOPS site works well before install Protector 3.3 beta.
After install Protector, it is ok at beginning.
But I don't know since when, each time I login, I can see "PHPSESSID=blebla" at the end of url.
And when I click anything in my site, XOOPS does not know who I am because there is no PHPSESSID in the URL.
If I manually add it to the URL, XOOPS would know who I am.
Rightnow I remark the two php in mainfile.php. But the situation still there. It drives me crazy. Can anybody tell me what's going on???
Update::
Since I can enter Admin area but cannot uninstall Protector module. So I enter MySQL and change isactive value of protector module to 0. And also remark the added 2 lines in mainfile.php. And also delete XOOPS_TRUST_PATH in mainfile.php.
And now I uninstall protector module succesfully. Uninstall process remove database table of protector.
I empty XOOPS_session table, delete files under template_c and cache folder. I also delete cache of IE.
Strange, the PHPSESSID still there!! Enter admin area to see modules, there is still a message "set XOOPS_TRUST_PATH into mainfile.php".
The only thing I did not do is delete the folder of trust path...
What's going on. Even uninstall still left something on my XOOPS??
How to remove it totally?
Or what did I do wrong?
TKS for any help!!
Votes:12
Average:9.17
vaughan
Posts: 37
Posts: 37
this usually only happens if your browser or firewall is blocking cookies.
check also in php.ini to see if enable_trans_sid is disabled (it should be for security reasons).
but either way if your site is trying to send the session id in the URL then your computer or firewall is most likely blocking cookies.
check also in php.ini to see if enable_trans_sid is disabled (it should be for security reasons).
but either way if your site is trying to send the session id in the URL then your computer or firewall is most likely blocking cookies.
Votes:9
Average:8.89
ufgeorge
Posts: 3
Posts: 3
Hi, vaughan,
TKS for your info.
I do notice that there is no cookie of my XOOPs site on my IE cache. Since I change to other PC and internet connection, I believe that is not because of client browser or firewall.
The php.ini, I check my hosting, there is no "enable_trans_sid" on my web root php.ini.
How should I do? Or any other possiblity that my XOOPs cannot send cookie to browser.
TKS for any help.
TKS for your info.
I do notice that there is no cookie of my XOOPs site on my IE cache. Since I change to other PC and internet connection, I believe that is not because of client browser or firewall.
The php.ini, I check my hosting, there is no "enable_trans_sid" on my web root php.ini.
How should I do? Or any other possiblity that my XOOPs cannot send cookie to browser.
TKS for any help.
Votes:9
Average:8.89
ufgeorge
Posts: 3
Posts: 3
Update to all...
I finally found the problem is because I change mainfile.php.
I want to move db username and password to another file and include that file. This cause the session problem.
I finally found the problem is because I change mainfile.php.
I want to move db username and password to another file and include that file. This cause the session problem.
Votes:7
Average:8.57
Login