On Tue, Feb 24, 2009 at 8:44 AM, Axel Bojer <axelb@skolelinux.no> wrote:
Wagner, Jane skrev:
-----Original Message----- On Tue, Feb 24, 2009 at 7:33 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On Tue, Feb 24, 2009 at 7:15 PM, paul POULAIN <paul.poulain@biblibre.com> wrote:
Wagner, Jane a écrit :
Can someone clarify the timeout system preference? In the 3.0.x manual site, it says
Hi Jane,
Inactivity timeout for cookies authentication (in seconds). This preference applies to both the staff client and the OPAC.
Default Value: 12000000
I think at some point someone probably complained they were getting disconnected too much so it got set to a really high value.
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet. Short for opac, long for intranet, where you want to : start cataloging a book, go have a coffee, continue cataloging that darn book. my 2 cts Nicolas
That's one reason I was looking at the syspref (thanks to all for the responses). It would be useful to specify that an OPAC session should close after x minutes of inactivity -- especially for a public workstation in a library. However, a staff session should have a much longer timeout. We may try to do something with this at some point....
At the same time perhaps also make it possible to log in as another user in opac as in staff on the same computer? I am sometimes confused that I have to log out of staff to test a user in opac, unless I have a separate machine to do this on.
An easy way to do this presently is to setup a different virtualhost name for the staff interface. IE. opac.foo.bar for OPAC staff.foo.bar for staff Regards, Chris