View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002574||SOGo||Backend Calendar||public||2014-01-10 07:56||2014-02-27 04:53|
|Reporter||Jens Erat||Assigned To|
|Summary||0002574: No colors selectable if ressource ID contains space character|
After migrating some data to SOGo using the CalDAV interface, we experienced an issue with some resources for which we cannot select a resource color. All these Calendars have in common that they include whitespace in their name. We have also been able to reproduce the problem using the restore feature in
|Steps To Reproduce|
If another calendar with ID
|Tags||No tags attached.|
How did you end up having a space in the calendar ID? If it's by messing around the data, you're shooting yourself in the foot.
We got the space by creating a calendar via davfs.
We created these calendars using DAV, by creating directories (which might be not valid regarding the standard, but worked fine nonetheless). It seems this is a way to sink invalid data into SOGo and those invalid UIDs might be better subject to verification before being accepted (and breaking later in other places).
We might better create calendars using the "official" way be sending an
Anyway, in my reading UIDs containing spices are valid as defined by RFC 5545.
It might be well possible that I read over some limitations, but the grammar definitely includes the space character.