<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>Redirect to correct view on direct access</title>
  <pubDate>Tue, 07 Oct 2008 04:27:50 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/6312</link>
  <atom:link rel="self" type="application/rss+xml" title="Redirect to correct view on direct access" href="http://bugs.horde.org/ticket/6312/rss" />
  <description>Redirect to correct view on direct access</description>

  
  
  <item>
   <title>When users (or admins) have chosen a certain UI (DIMP or MIM</title>
   <description>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.</description>
   <pubDate>Sun, 24 Feb 2008 07:44:05 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/6312#t42844</link>
  </item>
  <item>
   <title>I have some concerns about this.  From what is described her</title>
   <description>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?</description>
   <pubDate>Wed, 02 Apr 2008 01:19:58 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6312#t44308</link>
  </item>
  <item>
   <title>&gt; I have some concerns about this.  From what is described h</title>
   <description>&gt; I have some concerns about this.  From what is described here, does 
&gt; this prevent any switching between modes once you are authenticated?  
&gt; 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.</description>
   <pubDate>Wed, 02 Apr 2008 04:29:19 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6312#t44310</link>
  </item>
  <item>
   <title>I don't see this as a showstopper.  We already have the code</title>
   <description>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.</description>
   <pubDate>Thu, 03 Apr 2008 01:53:04 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6312#t44350</link>
  </item>
  <item>
   <title>I agree.</title>
   <description>I agree.</description>
   <pubDate>Thu, 03 Apr 2008 04:44:43 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6312#t44355</link>
  </item>
  

 </channel>
</rss>
