OPNsense Forum

English Forums => General Discussion => Topic started by: James Marvel on January 15, 2025, 01:49:46 AM

Title: Opensense Forum Sucks
Post by: James Marvel on January 15, 2025, 01:49:46 AM
 When you go to login in and write a post. The forum ask how long are you going to be logged in for. If you choose 1hr and have written a book and its gone over that time. There are no alerts or anything to warn you. So when you go to post, it asks you to log back in. Of course all of the data the you wrote is lost.That is a hour of your life gone that you cant get back. Remove that stupid option of "How many hours to logout", and instead have "Always logged in until you decide to log out manually".
Title: Re: Opensense Forum Sucks
Post by: James Marvel on January 15, 2025, 01:51:40 AM
I wont be using those stupid options ever again.
Title: Re: Opensense Forum Sucks
Post by: pfry on January 15, 2025, 03:01:22 AM
Yep, most fora are annoying that way. The "back" button works on most browsers. But paranoia works, too - it should only bite you zero to one times.
Title: Re: Opensense Forum Sucks
Post by: passeri on January 15, 2025, 03:48:20 AM
Quote from: James Marvel on January 15, 2025, 01:49:46 AMAlways logged in until you decide to log out manually

I believe the manual option is "Forever". It is at the top of the list.
Title: Re: Opensense Forum Sucks
Post by: Greg_E on January 15, 2025, 04:45:39 PM
Wait... Maybe I'm misunderstanding things... I thought the 1 hour was inactivity, not 1 hour total. Do I have this wrong?

If it's a hard timer, I can see that as a problem. If it is somehow linked to activity, and resets every time you open a post or make a post, this would be fine.
Title: Re: Opensense Forum Sucks
Post by: Patrick M. Hausen on January 15, 2025, 04:51:07 PM
Quote from: Greg_E on January 15, 2025, 04:45:39 PMIf it's a hard timer, I can see that as a problem. If it is somehow linked to activity, and resets every time you open a post or make a post, this would be fine.
Editing a text field in a form is not activity in an "old school" web application. The next exchange from browser to server or vice versa takes place only when you hit that "submit" button.

I bet that is the root cause of the problem.