<?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>Add another webdav directory level for share owners</title> 
  <pubDate>Fri, 10 Apr 2026 06:34:48 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/6595</link> 
  <atom:link rel="self" type="application/rss+xml" title="Add another webdav directory level for share owners" href="https://bugs.horde.org/ticket/6595/rss" /> 
  <description>Add another webdav directory level for share owners</description> 
 
   
   
  <item> 
   <title>See bug 3032 and http://lists.horde.org/archives/cvs/Week-of</title> 
   <description>See bug 3032 and http://lists.horde.org/archives/cvs/Week-of-Mon-20080407/077263.html



From Jan:

Calendars in Kronolith for example are available now as:



/kronolith/owner/calname/event

/kronolith/owner/calname.ics



The idea is a) to have more structure, but more important b) to later   allow to create shares/resources from WebDAV (CalDAV) actually. To avoid share name clashing we discussed that users can create those share, but they will be prefixed with the user name. The WebDAV structure is going to do something similar. We could maybe even add some black magic to automatically strip and the user prefix from/to share names when displayed/added through the DAV interface.</description> 
   <pubDate>Fri, 11 Apr 2008 03:16:40 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44579</link> 
  </item> 
   
  <item> 
   <title>I will work on this issue.



One thing to note:  This chang</title> 
   <description>I will work on this issue.



One thing to note:  This change will break some aspects of backward compatibility with Horde 3.1/Nag 2.1.  In the case where a requested URL is the old style (&quot;/rpc.php/nag/userid.ics&quot; or &quot;/rpc.php/nag/tasklistID.ics&quot;) we can serve up the task list.  However if someone tries to browse their own task list entries it will conflict with the new schema.  Example:



Nag 2.1: &quot;/rpc.php/nag/userID-as-tasklistID&quot;

Nag 2.2: &quot;/rpc.php/nag/userID/userID-as-tasklistID&quot;



In the interest of keeping the code simple I will not attempt to handle old-style requests to get task list items by browsing the task list ID as it was done in Nag 2.1</description> 
   <pubDate>Tue, 22 Apr 2008 19:51:35 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44812</link> 
  </item> 
   
  <item> 
   <title>Testing DELETE yields permission errors:



When deleting th</title> 
   <description>Testing DELETE yields permission errors:



When deleting the .ics file, the issue is in the api code (around line 659) when we test $parts[1] - it contains the &#039;.ics&#039; extension so the compare fails.



Once we&#039;re past that, that task items appear to be deleted, but then a &quot;Shares must be Horde_Share_Objects or extend that class&quot; error being returned I&#039;m guessing on line 681 of api.php



Too late for me to look further though ... gotta get to bed :)



</description> 
   <pubDate>Thu, 24 Apr 2008 05:42:42 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44867</link> 
  </item> 
   
  <item> 
   <title>OK. The deletion issue is fixed. We weren&#039;t checking for the</title> 
   <description>OK. The deletion issue is fixed. We weren&#039;t checking for the .ics extension before comparing, and we were passing the share name instead of the share_object to removeShare().



The issue of creation is still problematic. The underlaying issue is that RPC/webdav.php is attempting to call a _nag_mkcol api method instead of _nag_put when adding an entire task list.  Trying to add a single task into an existing task list folder gives no errors, but silently fails.



</description> 
   <pubDate>Thu, 24 Apr 2008 18:31:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44897</link> 
  </item> 
   
  <item> 
   <title>I have now made all the necessary changes to allow PUT to wo</title> 
   <description>I have now made all the necessary changes to allow PUT to work via WebDAV as well as of HEAD nag/lib/api.php version 1.167.  



mrubinsk:  I could not recreate the behavior you saw with MKCOL.  Would you retest and let me know if it&#039;s still a problem?



At this point browse, put, and delete seem to be working, at least for me.</description> 
   <pubDate>Tue, 29 Apr 2008 21:53:41 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44991</link> 
  </item> 
   
  <item> 
   <title>One other question came up:  Do we want to allow automatic c</title> 
   <description>One other question came up:  Do we want to allow automatic creation of tasklists if a .ics file is uploaded or a directory is created for a non-existing tasklist?</description> 
   <pubDate>Tue, 29 Apr 2008 21:55:15 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44992</link> 
  </item> 
   
  <item> 
   <title>&gt; mrubinsk:  I could not recreate the behavior you saw with </title> 
   <description>&gt; mrubinsk:  I could not recreate the behavior you saw with MKCOL.  

&gt; Would you retest and let me know if it&#039;s still a problem?



What I&#039;m seeing right now is:

1) When PUTing a file, pear&#039;s HTTP_WEBDAV_Server is chocking in http_PUT(). The switch block that checks the headers encounters a HTTP_CONTENT_LENGTH header that drops in to the default case and returns a 501 error. 



2) Commenting out the default case let&#039;s me get passed that error, but then I get an error from nag that says the task list does not exist or I don&#039;t have permissions to modify it.



Still digging...</description> 
   <pubDate>Wed, 30 Apr 2008 00:05:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44993</link> 
  </item> 
   
  <item> 
   <title>&gt; One other question came up:  Do we want to allow automatic</title> 
   <description>&gt; One other question came up:  Do we want to allow automatic creation 

&gt; of tasklists if a .ics file is uploaded or a directory is created for 

&gt; a non-existing tasklist?



Ideally yes, but wouldn&#039;t we need to support arbitrary share_names first?</description> 
   <pubDate>Wed, 30 Apr 2008 00:09:30 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44994</link> 
  </item> 
   
  <item> 
   <title>OK. I think i was misunderstanding what to test.  I was down</title> 
   <description>OK. I think i was misunderstanding what to test.  I was downloading a task list, deleting it, then trying to upload it. That fails, but if rename the task list I&#039;m uploading to an existing one, it works, and replaces the existing one.



So, delete works, and put works, but not directly after one another :)



(The MKCOL error still occurs, but only when trying to upload a directory of *.ics task files, or create a new directory)</description> 
   <pubDate>Wed, 30 Apr 2008 00:33:29 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44996</link> 
  </item> 
   
  <item> 
   <title>...and to clarify, the issue mentioned below regarding HTTP_</title> 
   <description>...and to clarify, the issue mentioned below regarding HTTP_CONTENT_LENGTH is still an issue. I can&#039;t upload the tasklist unless I comment out that block in HTTP/WebDAV/Server.php</description> 
   <pubDate>Wed, 30 Apr 2008 00:36:23 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t44997</link> 
  </item> 
   
  <item> 
   <title>What&#039;s left here? the HTTP_CONTENT_LENGTH issue is a bug in </title> 
   <description>What&#039;s left here? the HTTP_CONTENT_LENGTH issue is a bug in Http_WebDav_Server, so that doesn&#039;t need to hold this up.



Also, do we want to/can we support uploading of single .ics files to replace/add individual tasks in put()?</description> 
   <pubDate>Fri, 02 May 2008 00:59:13 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t45081</link> 
  </item> 
   
  <item> 
   <title>&gt; What&#039;s left here? the HTTP_CONTENT_LENGTH issue is a bug i</title> 
   <description>&gt; What&#039;s left here? the HTTP_CONTENT_LENGTH issue is a bug in 

&gt; Http_WebDav_Server, so that doesn&#039;t need to hold this up.

&gt;

I got a note back from Hartmut indicating this bug is now fixed in PEAR CVS



&gt; Also, do we want to/can we support uploading of single .ics files to 

&gt; replace/add individual tasks in put()?

Uploading a single .ics does work with the code in CVS right now as that is what I primarily tested.  There are two things left:



1) Fully test PUTting individual tasks into the tasklist folder.  I think mrubinsk may have tested this a bit but I haven&#039;t yet myself.



2) Deny deleting the .ics file or tasklist folder itself.  Based on testing feedback and conversations in IRC the ability to delete an entire tasklist from WebDAV will probably end up being more confusing for users than useful.  This should be the case at least until we get tasklist creation working either by creating a folder or by PUTting a new .ics file.  We will still allow deletion of individual tasks within the tasklist folder though.



Both of those items are fairly straightforward though so barring any more bugs we should be able to close this one pretty quickly.

</description> 
   <pubDate>Fri, 02 May 2008 01:10:23 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t45082</link> 
  </item> 
   
  <item> 
   <title>&gt; 1) Fully test PUTting individual tasks into the tasklist f</title> 
   <description>&gt; 1) Fully test PUTting individual tasks into the tasklist folder.  I 

&gt; think mrubinsk may have tested this a bit but I haven&#039;t yet myself.



Yeah, that&#039;s what I meant about uploading individual .ics files - not clear. I guess those aren&#039;t technically .ics files either.</description> 
   <pubDate>Fri, 02 May 2008 04:02:37 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t45085</link> 
  </item> 
   
  <item> 
   <title>With the final commit today to prevent deleting entire taskl</title> 
   <description>With the final commit today to prevent deleting entire tasklists I consider this issue closed.</description> 
   <pubDate>Mon, 05 May 2008 21:52:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6595#t45180</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
