Thank you for your answer, ... but in my php.ini there are only timeouts set in seconds and noting above 90 seconds. Also in the apache-confs there is nothing to find about this. Any more ideas? Kind regards, Frank Raquel schrieb:

I've gone overnight with editing and haven't been logged out, so it's definitely possible. In my php.ini there's an option called "session.cookie_lifetime" which apparently means "until the browser is restarted." Maybe that's it? (Assuming cookies are working for your sessions and it's not falling back to another method that times out sooner.) Either way if you've been away for a while just open another link (like the main page) in a new window/tab - log in there if required, and then go back and save your changes in the original window/tab. Cheers, Adam.

Hi Brion, How can I prevent MediaWiki from expiring my session without the 'remember my login' option checked? The expiring session is not transparent for normal users and they won't preview their changes before saving it. They also won't copy their changes to clipboard before clicking on the save-button. So again: How can change this behavior. This timeout is surely configurable and one hour is too short at all!! Kind regards, Frank Brion Vibber schrieb: > Adam Nielsen wrote: >>>> but in my php.ini there are only timeouts set in seconds and noting >>>> above 90 seconds. Also in the apache-confs there is nothing to find >>>> about this. >>> I've gone overnight with editing and haven't been logged out, so it's >>> definitely possible. In my php.ini there's an option called >>> "session.cookie_lifetime" which apparently means "until the browser is >>> restarted." Maybe that's it? (Assuming cookies are working for your >>> sessions and it's not falling back to another method that times out >>> sooner.) > > The session may expire earlier than the cookie; the server has no way of > knowing when the browser leaves. > > >>> Either way if you've been away for a while just open another link (like >>> the main page) in a new window/tab - log in there if required, and then >>> go back and save your changes in the original window/tab. > > Personally, I pull out the 'preview' button for this sort of case. Once > you're sure the session is reestablished, you can click 'save' in > confidence. :) > > -- brion vibber (brion @ pobox.com) _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l

Hi Adam, Well, the default value is "0" which means exactly what you have written. But the browser window isn't closed, so the session can't expire! So IMHO this can't be the parameter which is responsible for the problem. Yes, I can also copy my changes to clipboard before saving, but I am not asking because I have got this problem, but my users. And they won't understand, why they should do such trouble to just save a stupid article. And if they would understand, they would forget it in the moment they want to save and their work would be trashed. Kind regards, Frank Adam Nielsen schrieb: >> but in my php.ini there are only timeouts set in seconds and noting >> above 90 seconds. Also in the apache-confs there is nothing to find >> about this. > > I've gone overnight with editing and haven't been logged out, so it's > sessions and it's not falling back to another method that times out > sooner.) > > > Cheers, > Adam. > _______________________________________________ > MediaWiki-l mailing list > MediaWiki-l(a)Wikimedia.org > http://mail.wikipedia.org/mailman/listinfo/mediawiki-l >

Hi Brion, I have tested all previously quoted parameters and none of them was responsible for the timeout. I have tested: session.gc_maxlifetime => "1440" So I should have been logged out after 24 minutes. After starting to edit an article I waited 27 Minutes and clicked on save and the changes were saved correctly. I think that both parameters session.cache_expire => "180" session.cookie_lifetime => "0" can't be the reason for the timeout. Do you have another idea? Thank you in advance, kind regards, Frank Brion Vibber schrieb: _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l

Hi Raquel, If I had changed the value from the default-paramter (1440 seconds => 24 minutes), I surely would have restarted the server. But 1440 is the default-parameter, so the server needn't to be restarted. But the problem isn't solved and the timeout-parameter isn't found yet. Any more ideas? Thank you in advance, Frank Raquel schrieb: > On Mon, 11 Dec 2006 18:09:20 +0100 > "bl(a)vitronic.com" <bl(a)vitronic.com> wrote: > >> Hi Brion, >> >> I have tested all previously quoted parameters and none of them >> was responsible for the timeout. >> >> I have tested: >> >> session.gc_maxlifetime => "1440" >> >> So I should have been logged out after 24 minutes. After starting >> to edit an article I waited 27 Minutes and clicked on save and the >> changes were saved correctly. >> >> I think that both parameters >> >> session.cache_expire => "180" >> session.cookie_lifetime => "0" >> >> can't be the reason for the timeout. >> >> Do you have another idea? >> >> Thank you in advance, >> >> kind regards, >> >> Frank >> > >

I am sorry... Please apologize, OK? Frank Raquel schrieb:

Hello Frank, Do you know if this is a client side issue? Could you give us a URL for the site and let us see if the cookie expires after one hour? Have you tried different browsers? Thanks, Kasimir On 12/11/06, Raquel <raquel(a)thericehouse.net> wrote: -- Kasimir Gabert

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 bl(a)vitronic.com wrote: To the best of my knowledge any timeout on sessions, stored on the filesystem per PHP's defaults, would be from the PHP configuration. - -- brion vibber (brion @ pobox.com)