[#5535] Turba share support issues
Summary Turba share support issues
Queue Turba
Queue Version HEAD
Type Bug
State Resolved
Priority 2. Medium
Requester mrubinsk (at) horde (dot) org
Created 2007-07-07 (5226 days ago)
Updated 2007-07-12 (5221 days ago)
Resolved 2007-07-12 (5221 days ago)
Patch No

2007-07-12 00:19:28 Michael Rubinsky Comment #3
State ⇒ Resolved
Reply to this comment
2007-07-08 14:00:08 Michael Rubinsky Summary ⇒ Turba share support issues
2007-07-08 13:50:31 Michael Rubinsky Taken from Michael Rubinsky
2007-07-08 13:50:09 Michael Rubinsky Comment #2
Version ⇒ HEAD
Queue ⇒ Turba
State ⇒
Reply to this comment
Moving to the Turba queue since this a actually part of a larger 
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.
2007-07-07 22:05:35 Michael Rubinsky Comment #1
Type ⇒ Bug
State ⇒ Assigned
Priority ⇒ 2. Medium
Summary ⇒ Net_IMSP share support broken
Queue ⇒ Horde Framework Packages
Assigned to Michael Rubinsky
Reply to this comment
With recent changes to flatten the datatree/shares - and Turba's 
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.

Saved Queries