Maybe make a nice page with an image that says "Please wait system busy"

Looks better than an error which makes ppl think its broken

Or that nice little Preloader that was made a while back.

Unfortunately this fix also wiped away a post of mine, on which I was working over a relatively long period of time. After clicking Submit I got the error message, the redirect and then

Quote::

No post mode specified

Of course I got my post back by using the back-button (I have browsercaching enabled), but it's not really elegant.

I believe this has to do with the php "session.gc_maxlifetime" setting..

http://us3.php.net/manual/en/ref.session.php

session.gc_maxlifetime integer
session.gc_maxlifetime specifies the number of seconds after which data will be seen as 'garbage' and cleaned up.


Default:
session.gc_maxlifetime: "1440" // 1440 seconds (24 Minutes)

For administrators that want to increase that time.. They may modify the "\includes\classes\session.php" file..

Backup the file first before editing of course..


Do a search for this next line to get to the right place in the file

Quote::

$this->old_handler = ini_set('session.save_handler', 'files');

Under that you may or may not see this line commented out below it

Quote::

// ini_set('session.gc_maxlifetime', $expired); # bug not deleting ?

$expired is declared as "$expired = (gmtime()-($time*60));"
The gmtime() isn't supposed to be included in the gc_maxlifetime setting...


You could change the 'session.gc_maxlifetime' line to the following and uncomment it, or if you don't see the commented line then add a new line under the one you searched for. Change/Add the following one line..

Quote::

ini_set('session.gc_maxlifetime', ($time*60));

default value for $time in the function is 180.. So this should change the dragonfly session expired time from 24 minutes to 3 hours.. (180 minutes)..

If that doesn't work for someone, like for instance the "ini_set" feature is disabled..then maybe you need to manually edit the php.ini and set it to a higher setting..

It's fixed for atleast our PHP systems.
Donno if it works on others.

WizKid234 wrote:

I believe this has to do with the php "session.gc_maxlifetime" setting..

Yes and no, we've already tried that but the server crashes when you extend it. This has to do with a memory restriction on the list creation in the shell 'ls' command.