On Wednesday 16 April 2014 02:14 AM, Andre LaBranche wrote:
From twistedcaldav/stdconfig.py, here's the comment for the
RestrictCalendarsToOneComponentType plist setting:
# Only allow calendars to be created with a single component type
# If this is on, it will also trigger an upgrade behavior that will
# split existing calendars into multiples based on component type.
# If on, it will also cause new accounts to provision with separate
# calendars for events and tasks.
In other words, a 404 might be expected depending on the above setting, and
when your account was provisioned relative to any upgrades or changes to this
setting.
-dre
Awesome!!! This was what I was looking for :).
One last query. So , in versions prior to calendarserver 5.x, the guid
used to be automatically generated for XML records which did not have
guid. But since 5.x, this auto-generation is removed and as I
understand, users are supposed to explicitly mention the guid. So, if
they want to have access to the migrated data, they should know what
auto-generated guid was being used earlier. I have written a script
which will tell them this if they give the realm, recordType and uid.
However, I am wondering if there is already a solution for this provided
out-of-the-box or a more elegant way of doing it.
Thanks a ton for all the prompt responses.
Regards,
Rahul.
_______________________________________________
calendarserver-dev mailing list
calendarserver-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/calendarserver-dev
