Summary | Maintenance task causes the interface to switch to imp |
Queue | DIMP |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | Horde Developers (at) , slusarz (at) horde (dot) org |
Requester | nicholas.inglis (at) bluebottle (dot) com |
Created | 01/31/2008 (6372 days ago) |
Due | |
Updated | 04/03/2008 (6309 days ago) |
Assigned | 04/02/2008 (6310 days ago) |
Resolved | 04/03/2008 (6309 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | 1 |
Patch | No |
State ⇒ Resolved
http://lists.horde.org/archives/cvs/Week-of-Mon-20080331/076913.html
State ⇒ Feedback
Ticket 6312.#2- Should be fixed (commit message not currently available)request #6312.- nick
request #6312.user on login cause the interface to end up in imp. This is bad
because we want to stay in the dimp interface.
it returns to the imp/redirect.php script, which then pushes you into
imp.
the redirect script was our first point of call before maintenance,
and it included a hidden variable 'select_view' = 'dimp'
After maintenance this hidden variable is missing, so we end up in the
imp interface rather than the dimp one. (I think this is what is
happening).
does this mean that we need to store the interface before going into
maintenance, and restore it afterwards?
- nick
Assigned to
State ⇒ Assigned
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Queue ⇒ DIMP
Summary ⇒ Maintenace task causes the interface to switch to imp
Type ⇒ Bug
user on login cause the interface to end up in imp. This is bad
because we want to stay in the dimp interface.