The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Help! I set my cookie timeout to 0 seconds and can't login!
I am a newb at vbulletin, so I do not know how to access the database or anything besides using AdminCP.
I'm on version 5.2.4 patch level 2. How do I reset the cookie timeout without access to AdminCP (since I can't login due to cookie timeout 0)??? --------------- Added [DATE]1479441311[/DATE] at [TIME]1479441311[/TIME] --------------- vBulletin is hosting my site, so I don't have access to FTP or the DB? |
#2
|
||||
|
||||
I already fixed this for you when you put in a ticket. There isn't a way for you to fix it without access to the database.
|
2 благодарности(ей) от: | ||
In Omnibus, MarkFL |
#3
|
||||
|
||||
Just go into phpadmin, settings table and look for cookietimeout.. Change the value..
Clear your browser cache and log in.. If the browser clear does not work change the cookie prefix in your config file. |
#4
|
||||
|
||||
He is on vBCloud, so he was unable to run queries on the database.
|
Благодарность от: | ||
RichieBoy67 |
#5
|
||||
|
||||
Quote:
Oh well, the information will possibly be helpful to someone else. |
#6
|
||||
|
||||
Why would anyone set it to 0 in the first place
|
#7
|
||||
|
||||
^ Also please don't set this value very high either, it can cause issues being set too high as well.
I've never seen it set to 0 before and that is why Paul also seems quite surprised! |
#8
|
||||
|
||||
They either thing 0 is unlimited or they accidentally deleted the value in there and Saved. At least, that was what happened the two times I have seen this done.
|
Благодарность от: | ||
TheLastSuperman |
#9
|
||||
|
||||
vBulletin should put eval code in that field so that this cannot be set to less then 30 seconds.
|
#10
|
||||
|
||||
There has always been code in vB (3 & 4) to prevent it being < 60 seconds.
The problem with vB5 is that as they slowly stopped using the legacy vB4 code is was initially built from, they reached a point where that particular code was no longer running on the front end, which means its now became a potential issue. They added the code (well similar) back into 5.2.6. |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|