Yes, as Massimo and I have suggested, you should store them in
extra_fields. That way they will be associated with the users. Another
alternative is to use an extra cookie, but that seems like a waste of
bandwidth.
On Friday, May 23, 2014 9:06:12 PM UTC-7, Mandar Vaze wrote:
Derek,
May be
http://web2py.com/books/default/chapter/29/09/access-control?search=auth.settings.extra_fields
On Friday, 23 May 2014 23:06:12 UTC-5, Mandar Vaze wrote:
Derek,
May be I misrepresented my scenario - These aren't exactly preferences.
In both the applications - user sees SQLFORM.grid with large
A session should only be temporary storage related to the current session.
If you are storing preferences in user accounts then you should store them
with the user accounts, not using a session. I don't see what your problem
is.
On Friday, May 23, 2014 10:58:40 AM UTC-7, Mandar Vaze wrote:
I
Yes, due to a security vulnerability, the behavior was changed -- now by
default, a new session ID is created upon either login or logout, and upon
logout, the session itself is cleared. The behavior can be controlled with
these settings (default values shown):
Derek,
May be I misrepresented my scenario - These aren't exactly preferences.
In both the applications - user sees SQLFORM.grid with large number of
records. User will use filter to reduce the count.
Depending on the user - user is likely to use same filters for quite some
time - across
5 matches
Mail list logo
