| Summary | Share renaming is handled incorrectly in the kolab share driver |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | wrobel (at) pardus (dot) de |
| Created | 03/08/2007 (6743 days ago) |
| Due | |
| Updated | 03/08/2007 (6743 days ago) |
| Assigned | |
| Resolved | 03/08/2007 (6743 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Share renaming is handled incorrectly in the kolab share driver
Queue ⇒ Horde Framework Packages
New Attachment: framework-Share-Share-kolab.php_share_renaming_20070308.patch
underlying IMAP folder. This requires that all caches get updated with
the new name which is currently missing from the driver.
The patch is not elegant. The original problem originates from the
fact that share renaming has a completely different meaning for the
kolab driver than the datatree driver.
The datatree driver operates with a unique random id that is the
ultimate reference to the share. So renaming just means that the
'name' attribute is modified. For the kolab driver the share name
matches the IMAP folder name and so renaming has a much larger impact.
I still don't know how to fix that properly within the boundaries of
backward compatibility but I am thinking about possible solutions :)