<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>hierarchical folder structure in portal view</title> 
  <pubDate>Sun, 05 Apr 2026 20:30:07 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/3004</link> 
  <atom:link rel="self" type="application/rss+xml" title="hierarchical folder structure in portal view" href="https://bugs.horde.org/ticket/3004/rss" /> 
  <description>hierarchical folder structure in portal view</description> 
 
   
   
  <item> 
   <title>Since some months ago, the default view on the IMAP folders </title> 
   <description>Since some months ago, the default view on the IMAP folders is not structured as before (below INBOX).

Attached are two  diff -c  for  horde/framework/IMAP/IMAP/Tree.php  and  horde/imp/config/conf.xml

which allow to set a new parameter to get back the hierarchical view of mailbox folders in the portal view.

If it is NOT set, everything stays as it is now !

Unfortunately I am not familiar in php and also not in creating patch-files - sorry.

Because of this fact, I have not yet figured out, how to apply this change on  horde/imp/folders.php  ;

so  horde/imp/folders.php  will not show you any folders below INBOX when

  $conf[&#039;server&#039;][&#039;dont_strip_namespace&#039;]  is set !



It would be nice if this (presumably a bit more professional) could be apllied to the current HEAD.



Stefan



P.S.: Inspired by a &quot;quick suggestion&quot; of Michael Slusarz in Ticket #2422 - Thank you again !

</description> 
   <pubDate>Sat, 19 Nov 2005 12:04:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3004#t13874</link> 
  </item> 
   
  <item> 
   <title>corrected diff-file (should be valid for  patch -p 0  in hor</title> 
   <description>corrected diff-file (should be valid for  patch -p 0  in horde) attached;

imp/folders.php will now also work correctly.</description> 
   <pubDate>Tue, 22 Nov 2005 21:11:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3004#t13951</link> 
  </item> 
   
  <item> 
   <title>This was mentioned in Bug 2422 as a &quot;quick suggestion&quot;, but </title> 
   <description>This was mentioned in Bug 2422 as a &quot;quick suggestion&quot;, but only for people who want to code this on their local server.  As discussed in that Bug, the current (new) way of displaying mailboxes is the decision we have made and providing preferences to allow &quot;old&quot; behavior are not going to be accepted.



As explained previously, the simple fact is users should *not* be expected to understand the concept of namespaces.



Additionally, if you read the RFCs, it is *not* correct to put the default namespace under &#039;INBOX&#039;, even if the default namespace is &#039;INBOX.&#039;    This is because &#039;INBOX&#039; must ALWAYS appear in the default namespace; obviously, INBOX can not be a subfolder of itself - it must be at the same level as the other mailboxes in the default namespace.  People need to understand that the namespace name (e.g. &#039;INBOX&#039;, &#039;#shared&#039;, etc.) are not mailbox names in and of themselves.  Rather, they are simply internal labels used to delimit between the various namespaces (labels != mailboxes)



Since several people have disagreed with our interpretation, these patches might be a good thing for the wiki - feel free to create a page there.  However, they are not going to be implemented into the code.</description> 
   <pubDate>Wed, 23 Nov 2005 02:23:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3004#t13973</link> 
  </item> 
   
  <item> 
   <title>I understand the reasons for making INBOX.subfolder appear a</title> 
   <description>I understand the reasons for making INBOX.subfolder appear as &#039;subfolder&#039; at the same level as INBOX instead of under INBOX. However, this causes a lot of trouble as well. Shared folders cannot be distinguished this way from the user&#039;s own folders! They are listed among the user folders. If a user has a folder with the same name as a shared folder, it looks like a duplicate. My users at least had some idea, that shared folders are different, because they were listed at the bottom. Now they will be confused for sure.

Could you reconsider your decision about rejecting a config setting that allows the old behaviour?</description> 
   <pubDate>Wed, 22 Mar 2006 21:21:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3004#t18035</link> 
  </item> 
   
  <item> 
   <title>&gt; I understand the reasons for making INBOX.subfolder appear</title> 
   <description>&gt; I understand the reasons for making INBOX.subfolder appear as 

&gt; &#039;subfolder&#039; at the same level as INBOX instead of under INBOX. 

&gt; However, this causes a lot of trouble as well. Shared folders cannot 

&gt; be distinguished this way from the user&#039;s own folders!



See Bug 3581.



&gt; Could you reconsider your decision about rejecting a config setting 

&gt; that allows the old behaviour?



I am looking into this.</description> 
   <pubDate>Wed, 22 Mar 2006 21:43:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3004#t18037</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git (master):

commit 6a8bb7f1be18</title> 
   <description>Changes have been made in Git (master):

commit 6a8bb7f1be18501f1559aeb73773e59966686668
Author: Paul M Jones &lt;pmjones@ciaweb.net&gt;
Date:   Mon Mar 7 13:25:18 2005 +0000

    fixed bug 3004 (Wrong path for rule &quot;image&quot;) -- patch provided by reg at dav-muz dot net
    
    
    git-svn-id: https://svn.php.net/repository/pear/packages/Text_Wiki/trunk@181536 c90b9560-bf6c-de11-be94-00142212c4b1

 Text/Wiki/Render/Xhtml/Image.php | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

http://github.com/horde/horde/commit/6a8bb7f1be18501f1559aeb73773e59966686668</description> 
   <pubDate>Wed, 06 Sep 2017 08:17:19 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3004#t92171</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
