<?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>Maintenance task causes the interface to switch to imp</title>
  <pubDate>Sat, 05 Jul 2008 20:08:52 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/6179</link>
  <atom:link rel="self" type="application/rss+xml" title="Maintenance task causes the interface to switch to imp" href="http://bugs.horde.org/ticket/6179/rss" />
  <description>Maintenance task causes the interface to switch to imp</description>

  
  
  <item>
   <title>The maintenance tasks of the mail client that are presented </title>
   <description>The maintenance tasks of the mail client that are presented to the user on login cause the interface to end up in imp. This is bad because we want to stay in the dimp interface.



</description>
   <pubDate>Wed, 30 Jan 2008 20:30:59 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/6179#t41682</link>
  </item>
  <item>
   <title>&gt; The maintenance tasks of the mail client that are presente</title>
   <description>&gt; The maintenance tasks of the mail client that are presented to the 
&gt; user on login cause the interface to end up in imp. This is bad 
&gt; because we want to stay in the dimp interface.
&gt;

After further investigation I find that after maintenance is complete 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



</description>
   <pubDate>Sun, 03 Feb 2008 21:08:43 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/6179#t41874</link>
  </item>
  <item>
   <title>This should be solved with implementing request #6312.</title>
   <description>This should be solved with implementing request #6312.</description>
   <pubDate>Thu, 28 Feb 2008 10:49:33 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/6179#t43244</link>
  </item>
  <item>
   <title>&gt; This should be solved with implementing request #6312.

</title>
   <description>&gt; This should be solved with implementing request #6312.

that sounds like a good idea.

- nick</description>
   <pubDate>Thu, 28 Feb 2008 21:24:09 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/6179#t43258</link>
  </item>
  <item>
   <title>#1 - This is a different issue than Ticket 6312.
#2 - Shoul</title>
   <description>#1 - This is a different issue than Ticket 6312.
#2 - Should be fixed (commit message not currently available)
</description>
   <pubDate>Wed, 02 Apr 2008 01:35:24 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6179#t44309</link>
  </item>
  <item>
   <title>This is the commit message:
http://lists.horde.org/archives</title>
   <description>This is the commit message:
http://lists.horde.org/archives/cvs/Week-of-Mon-20080331/076913.html</description>
   <pubDate>Wed, 02 Apr 2008 22:43:06 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6179#t44346</link>
  </item>
  

 </channel>
</rss>
