| Summary | Turba share support issues |
| Queue | Turba |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | mrubinsk (at) horde (dot) org |
| Created | 07/07/2007 (6557 days ago) |
| Due | |
| Updated | 07/12/2007 (6552 days ago) |
| Assigned | |
| Resolved | 07/12/2007 (6552 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Version ⇒ HEAD
State ⇒
Queue ⇒ Turba
problem in Turba.
Turba seems to assume that there will only be a single share-enabled
source, yet will look for default shares in all sources that have them
enabled. This leads to share name collisions since Turba uses the
horde username as the default share (which also assumes that any
backend with shares enabled will use the same username - which isn't
always the case with IMSP).
I need to look into this more deeply, but it looks like we will need
to put some more meaning back into the share names - like prepending
the source name again - and maybe moving the check for default shares
back into the individual drivers, since they should know about any
naming rules for their own backend.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Net_IMSP share support broken
Queue ⇒ Horde Framework Packages
Assigned to Michael Rubinsky
State ⇒ Assigned
recent move to the framework share code - share support for IMSP
sources is currently broken.
Among other things, there are share name collisions when user's horde
username == imsp username and issues when trying to create / check
existence of the share representing the default IMSP addressbook.