Welcome, Guest. Please login or register.
Did you miss your activation email?


Login with username, password and session length

Search

 
Advanced search

8043 Posts in 1856 Topics- by 2099 Members - Latest Member: roi
Calendar Script CommunityCustomizationHacks and Mods (Moderators: scott, DanO, Marty)Time Stamp Problems - Again!
Pages: [1]   Go Down
Print
Author Topic: Time Stamp Problems - Again!  (Read 346 times)
0 Members and 1 Guest are viewing this topic.
ronaldo
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« on: May 06, 2004, 06:28:00 AM »

Our calendar is hosted at Powweb, and they can't seem to keep the time set correctly on their server, at least not the one on which our calendar is hosted.

All too often I get the message "Your Session has expired. You must login again" immediately after logging on and trying to add or edit events.  I then check their server and find that their time is waaaaaay off, sometimes nearly 24 hours.

Their server is on Pacific Time and we are on Eastern Time.  I have the offset correct in CalendarScript.  However, I need to significantly bump up the amount of time that I'm allowed to be logged on so that I no longer get the dreaded "Your Session has expired" error message.

Can someone please tell me what to change in the script to permit me to stay logged on longer?  My knowledge of PERL is limited, but I follow directions well.  Any help will be appreciated.

Thanks,
Ron

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #1 on: May 06, 2004, 02:24:00 PM »

The code to set the session expiry is contained in the CGISession.inc file in the calendarscript/lib directory. The line responsible is in the "new" subroutine and is the line:

$self->{"_expires"} = 180;

You may be able to adjust that duration by increasing the number accordingly.

Dan O.


------------------

Logged
ronaldo
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #2 on: May 06, 2004, 04:04:00 PM »

Thanks, Dan O.  That solved the problem.  I dislike revising the code to crutch a problem on the web hosting company's server, so hopefully I can change the script back soon.

Incidentally, what are the consequences of a user logging in and failing to log out, assuming the 180 in the script is changed to 980?

Thanks for your help.
Ron

------------------

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #3 on: May 06, 2004, 06:44:00 PM »

I assume the 180 was minutes and if so, it was 3 hours. Going by that assumption 980 would make it 16.333333 hours the user would be logged in for if they didn't log out or close their browser. I can't think of any problems that would create in most cases.

Dan O.

------------------

Logged
ronaldo
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #4 on: May 07, 2004, 09:47:00 AM »

Yes, that's what I was thinking.  I'll change it back to 180 after PowWeb fixes the time stamp on their server.

I appreciate your help with this problem.

Ron

------------------

Logged
Pages: [1]   Go Up
Print
Jump to: