[#6312] Redirect to correct view on direct access
Summary Redirect to correct view on direct access
Queue IMP
Queue Version Git master
Type Enhancement
State Assigned
Priority 1. Low
Owners Michael Slusarz <slusarz (at) horde (dot) org>
Requester Jan Schneider <jan (at) horde (dot) org>
Created 02/24/2008 (496 days ago)
Due
Updated 06/01/2009 (33 days ago)
Assigned 06/01/2009 (33 days ago)
Resolved
Attachments
Milestone
Patch No

History
06/01/2009 Chuck Hagenbuch Assigned to Michael Slusarz
State ⇒ Assigned
Version ⇒ Git master
 
04/03/2009 Jan Schneider Comment #12
State ⇒ Feedback		 Reply to this comment
This is not what this ticket was about. You only redirected to view if 
you access IMP's index.php, you still get the old interface if you go 
to a mailbox, e.g. by clicking on a folder in the sidebar.
04/01/2009 Chuck Hagenbuch Comment #11
State ⇒ Resolved		 Reply to this comment
Works for me.
04/01/2009 Michael Slusarz Comment #10 Reply to this comment
What happens currently in IMP 5?
You are redirected to the view they logged in with.  If not logged in, 
they should be redirected to the login page.  This properly takes into 
account the users' view preference (which is stored in a cookie, not 
in a preference).
03/30/2009 Chuck Hagenbuch Comment #9 Reply to this comment
What happens currently in IMP 5?
03/30/2009 Michael Slusarz Comment #8
State ⇒ Feedback		 Reply to this comment
Can this ticket be dismissed?  Theoretically, this kind of code could 
be added to IMP 4.x, but it isn't coming from this guy ever. :)
12/14/2008 Chuck Hagenbuch Priority ⇒ 1. Low
State ⇒ Accepted
 
11/06/2008 Jan Schneider Comment #7 Reply to this comment
This could easily be added to IMP 4.2.x if someone feels like it, so 
I'd keep it as an option for a pre-5.0 release.
11/05/2008 Chuck Hagenbuch Comment #6
State ⇒ Feedback		 Reply to this comment
Given other changes, do we still want to do anything here before IMP 5 
and folding the other views directly into the IMP code?
04/03/2008 Jan Schneider Comment #5
Milestone ⇒ 		Reply to this comment
I agree.
04/03/2008 Michael Slusarz Comment #4 Reply to this comment
I don't see this as a showstopper.  We already have the code that will 
redirect to the correct view at login/first access.  While it might be 
nice (in certain cases) to enforce restrictions, the only way to 
access the other views is to manually change the URL as far as I can 
tell.  I don't think this is critical to get 4.2 out the door.  The 
major issue - making sure we access the correct view after login 
whether dealing with maintenance or not - has previously been fixed.
04/02/2008 Jan Schneider Comment #3 Reply to this comment
I have some concerns about this.  From what is described here, does 
this prevent any switching between modes once you are authenticated? 
  That is unacceptable if yes.
Yes, that was the intention. But I see how this might not be a good 
idea. It should be limited to cases where the admin disallowed the 
users to select the view.
04/02/2008 Michael Slusarz Comment #2 Reply to this comment
I have some concerns about this.  From what is described here, does 
this prevent any switching between modes once you are authenticated?   
That is unacceptable if yes.

Also, we already auto-detect the current view for purposes of compose 
link handling - at this point in 4.2, what else do we need?
04/01/2008 Jan Schneider Milestone ⇒ 4.2
 
02/24/2008 Jan Schneider Comment #1
Summary ⇒ Redirect to correct view on direct access
Type ⇒ Enhancement
Priority ⇒ 2. Medium
State ⇒ Accepted
Queue ⇒ IMP		 Reply to this comment
When users (or admins) have chosen a certain UI (DIMP or MIMP), all 
access directly to one of IMP's controller scripts should redirect to 
the correct url of the initially selected UI.
I envision an API method like 'getViewUrl' that takes the requested 
view (mailbox, message, etc) and additional parameters as arguments 
and returns the correct url to redirect to.