1
ukdave
set a long session expiration value or autologin hack?
  • 2004/7/7 20:47

  • ukdave

  • Just popping in

  • Posts: 67

  • Since: 2003/6/27


There are two ways that I know of to stay logged in.

1. Check 'use custom session' and set a long expiration time.

2. Use the autologin hack.

What is the difference? Would it do any harm setting sessions to expire after say one year?

2
Bender
Re: set a long session expiration value or autologin hack?
  • 2004/7/7 21:27

  • Bender

  • Home away from home

  • Posts: 1899

  • Since: 2003/3/10



Might depend on your site size. (to be exact the number of users usually online)


Check this thread:

remembering login

3
brash
Re: set a long session expiration value or autologin hack?
  • 2004/7/8 2:01

  • brash

  • Friend of XOOPS

  • Posts: 2206

  • Since: 2003/4/10


Using extended sessions over the autologin will increase server load. Mightn't matter much for low traffic sites (under 100 visits a day, depending on server), but larger sites it could have the potential to bring the server to its knees.

4
ukdave
Re: set a long session expiration value or autologin hack?
  • 2004/7/8 9:58

  • ukdave

  • Just popping in

  • Posts: 67

  • Since: 2003/6/27


Thanks for that, I will go with the login hack.

I think the login hack should be decommented in the core XOOPS download package, perhaps with a switch and a notice regarding security.

I want to use it so that users can keep their chosen theme alive without having to login and reset it all the time. I succesfully used the xt_temas module however it had side effects which I was unable to resolve. - Basically it broke my address book module.

Login

Who's Online

95 user(s) are online (70 user(s) are browsing Support Forums)


Members: 0


Guests: 95


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits