[CalendarServer-users] Problem creating multiple calendars for the same user

Glyph glyph at twistedmatrix.com
Wed Jun 20 10:24:01 PDT 2012


Le Jun 19, 2012 à 2:46 PM, Jane Atkinson <jea62q at xtra.co.nz> a écrit :

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 19/06/12 05:46, Glyph wrote:
>> 
>> Le Jun 17, 2012 à 8:51 PM, Jane Atkinson a écrit :
>> 
>>> I'd like to add other calendars for myname (e.g. 
>>> http://servername:8008/calendars/users/myname/workcal), but I'm
>>> having problems. I've looked extensively and can't see any
>>> reference to a solution.
>>> 
>>> I can't add these using a client. It won't create the new
>>> directory in the manner that it creates the original calendar
>>> directory.
>> 
>> What is "a client"?  How are you attempting to add it?
> 
> By this, I mean using either Lightning or Evolution to define a
> calendar that doesn't exist yet.
> 
> When calendarserver 2.4 is first set up, the calendar directory
> doesn't exist yet. Attempting to connect to the default calendar using
> Evolution or Lightning triggers the creation of the directory. I
> thought the same thing might happen with a second calendar, but it
> doesn't.
> 
> Evolution and Lightning no doubt are buggy, but they are all that I
> have. If anyone can tell me of a better one (Linux compatible) I'd be
> interested.

If you can set up Calendar Server 3.0+, I'd be happy to help you diagnose the bad 'create' behavior on the part of these clients.  But, for all I know, it's a bug in the old version of calendar server, and when you try a newer version, it might just work.

(These clients aren't going to get any better unless people use them and report bugs against them though, so please do that too.)

>>> I've also tried manually adding a directory alongside the
>>> calendar directory and changing ownership and permissions to
>>> match the other.
>> 
>> Don't do that.  The fact that the data store is a filesystem is an
>> accident of implementation, not something you should rely on.  (In
>> fact, in less ancient versions of the server, it's a database,
>> instead.)
>> 
> 
> At the risk of sounding like an ignorant newb, I'm going to ask, what
> is the correct (or best) way to add a new calendar? Command line is
> OK. I suspect that once the calendars are added correctly,
> Lightning/Evolution will find them.

Creating a calendar is best accomplished via a client, the way you've been doing it.  You could try using a Mac as your client, since it's pretty likely that iCal will do something that Calendar Server 2.4 will understand.

You could also try doing a DAV request, a MKCOL with an appropriate DAV:resourcetype via something like curl, but if it isn't immediately obvious to you how to do that you probably don't want to bother with it

-glyph



More information about the calendarserver-users mailing list