Summary | Keep 'nosave' pref value until the end of Session |
Queue | Horde Framework Packages |
Queue Version | Git master |
Type | Enhancement |
State | No Feedback |
Priority | 1. Low |
Owners | |
Requester | goncalo.queiros (at) portugalmail (dot) net |
Created | 11/30/2011 (4964 days ago) |
Due | |
Updated | 11/21/2016 (3146 days ago) |
Assigned | |
Resolved | 11/21/2016 (3146 days ago) |
Milestone | |
Patch | Yes |
State ⇒ Feedback
Priority ⇒ 1. Low
New Attachment: 0001-When-nosave-parameter-is-true-keep-pref-value-until-.patch
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ Keep 'nosave' pref value until the end of Session
Type ⇒ Enhancement
State ⇒ New
#9728, speaciallyhttp://bugs.horde.org/ticket/?id=9728#c18, and found that the correct
way to set a pref value is when the appinitialized hook runs.
I was expecting that the 'nosave' parameter would maintain the pref
value until the end of the session and not until the end of the
request, since this behavior doesn't seem interesting.
I attach a patch, that will respect the 'nosave' parameter, but will
keep the pref value until the session ends.
I don't know if this is the correct way, please enlighten me if
there's a better way to set a pref value only during the current
session.