<?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>recursive delete</title> 
  <pubDate>Fri, 10 Apr 2026 13:36:22 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/6962</link> 
  <atom:link rel="self" type="application/rss+xml" title="recursive delete" href="https://bugs.horde.org/ticket/6962/rss" /> 
  <description>recursive delete</description> 
 
   
   
  <item> 
   <title>Trean currently refuses to delete folders which have childre</title> 
   <description>Trean currently refuses to delete folders which have children.

This behaviour is inconvenient at times.

It even can be a real problem when a large bookmark collection has been imported in a test-run and should be deleted again.</description> 
   <pubDate>Fri, 20 Jun 2008 14:53:34 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6962#t46699</link> 
  </item> 
   
  <item> 
   <title>Just as a note, this should probably be done along with movi</title> 
   <description>Just as a note, this should probably be done along with moving Trean to the native hierarchical SQL driver.  Although currently the share driver will refuse to delete any shares with children (as did the original hierarchical DT share driver), we should allow Trean to either recursively delete each share or allow the share driver to take a new parameter which would allow it to ignore children. The second choice would be more efficient, but would mean that Trean would require Horde 3.2.2.  If we let it require 3.2.2, then Ansel could also make use of the same functionality since it, too will not delete galleries that contain any non-empty subgalleries.



Thoughts?</description> 
   <pubDate>Thu, 26 Jun 2008 13:23:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6962#t46858</link> 
  </item> 
   
  <item> 
   <title>If designed properly, the Horde 3.2.1 Share drivers would si</title> 
   <description>If designed properly, the Horde 3.2.1 Share drivers would simply ignore the parameter and return an error if we try to delete a folder which contains subfolders. 3.2.2 drivers can do the recursive deletion.</description> 
   <pubDate>Thu, 26 Jun 2008 13:29:55 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6962#t46860</link> 
  </item> 
   
  <item> 
   <title>&gt; If designed properly, the Horde 3.2.1 Share drivers would </title> 
   <description>&gt; If designed properly, the Horde 3.2.1 Share drivers would simply 

&gt; ignore the parameter and return an error if we try to delete a folder 

&gt; which contains subfolders. 3.2.2 drivers can do the recursive 

&gt; deletion.



Yea. Good point.  I guess we could also put a not-as-efficient recursive delete in Trean as well to keep the behavior consistent, if the Share driver returns the error.  Also, I think I&#039;d be more comfortable if there was an additional confirmation, or at the least, tweak the text of the existing confirmation to indicate your about to possibly nuke more than you realize.</description> 
   <pubDate>Thu, 26 Jun 2008 13:38:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6962#t46862</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; If designed properly, the Horde 3.2.1 Share drivers would</title> 
   <description>&gt;&gt; If designed properly, the Horde 3.2.1 Share drivers would simply

&gt;&gt; ignore the parameter and return an error if we try to delete a folder

&gt;&gt; which contains subfolders. 3.2.2 drivers can do the recursive

&gt;&gt; deletion.

&gt;

&gt; Yea. Good point.  I guess we could also put a not-as-efficient 

&gt; recursive delete in Trean as well to keep the behavior consistent, if 

&gt; the Share driver returns the error.



No, better not. That would only be required for BC for one or two Horde releases. That&#039;s not worth it. Plus, if there really is an error deleting folders and you try to do it recursively in Trean, you would probably end up with an error message for each folder, which could be a lot.



&gt; Also, I think I&#039;d be more 

&gt; comfortable if there was an additional confirmation, or at the least, 

&gt; tweak the text of the existing confirmation to indicate your about to 

&gt; possibly nuke more than you realize.



Yes.</description> 
   <pubDate>Thu, 26 Jun 2008 14:19:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6962#t46866</link> 
  </item> 
   
  <item> 
   <title>Folders are going away. Closing.</title> 
   <description>Folders are going away. Closing.</description> 
   <pubDate>Sun, 13 Nov 2011 00:26:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6962#t68753</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
