Tickets :: Comment on [#11713] Kolab backend: Newly created calendars lose all permissions

* Your Email Address
* Spam protection	Enter the letters below: . .. ..___. .. . \|\ \|\|\/\| \| \|\ / \| \\|\| \| \| \__\| \/
Comment	> The analysis from Thomas is correct: The section "// Process creator > permissions." within Kronolith::readPermsForm currently removes all > creator permissions. > > I'm totally fine with removing the permission mapping between > "creator" and "share owner". There is no correct mapping between the > Horde permission world and the Kolab permission world at the moment. > > The question is how much the removal of the creator permission > mapping would impair usability. Would it still be displayed even with > the Kolab backend and even though any setting there has no effect? Of > course the current Kronolith "DELEGATE" permission currently has the > same problem. > > In the long run one would probably need to modify Horde so that it > allows for different permission models depending on the selected > backend. But I guess that would be a major undertaking. > > Right now I don't see how I can fix anything here. I could apply > Jan's fix but would rather leave that to him.
Attachment
Watch this ticket