Summary | Namespace matching bug |
Queue | Kolab |
Type | Bug |
State | Assigned |
Priority | 1. Low |
Owners | thomas.jarosch (at) intra2net (dot) com |
Requester | matthias (at) familie-burghardt (dot) net |
Created | 03/26/2013 (4432 days ago) |
Due | |
Updated | 08/27/2013 (4278 days ago) |
Assigned | 08/27/2013 (4278 days ago) |
Resolved | |
Milestone | |
Patch | No |
server are you using?
My own calendar is as "INBOX/Kalender" and will be seen by other
users as "user/something/Kalender".
namespaces are reported by the server. Mine said
* NAMESPACE (("" "/")("kolab/" "/")) (("kolab_shared/" "/"))
(("kolab_public/" "/"))
The own calendar was then
* LIST (\HasNoChildren) "/" "kolab/Kalender"
ans was seen by other users as
* LIST (\HasNoChildren) "/" "kolab_shared/[my user name]/Kalender"
Maybe it was also due to the non-standard Kolab setup that I did.
Anyway, I changed "kolab" to "kolab_personal" so the error has vanished.
HTH
Matthias
any account other than the calendar owner, when opening kronolith
server are you using?
My own calendar is as "INBOX/Kalender" and will be seen by other users
as "user/something/Kalender".
I'm asking these details as I want to write a unit test that fails for
your case, fix the code and then run the test again. Thanks.
Any easy steps to reproduce it?
any account other than the calendar owner, when opening kronolith
Assigned to Thomas Jarosch
Kolab/Storage/Folder/Namespace/Element.php:102 gives wrong result if
one namespace name is a left-anchored substring of another, e.g.
'kolab' and 'kolab_shared'.
How did you discover this bug?
Any easy steps to reproduce it?
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Namespace matching bug
Queue ⇒ Kolab
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Kolab/Storage/Folder/Namespace/Element.php:102 gives wrong result if
one namespace name is a left-anchored substring of another, e.g.
'kolab' and 'kolab_shared'.