diff --git a/docs/website/clients/Chandler-details.php b/docs/website/clients/Chandler-details.php index ba301955..8214309f 100644 --- a/docs/website/clients/Chandler-details.php +++ b/docs/website/clients/Chandler-details.php @@ -7,7 +7,7 @@ written in Python.

  1. Select "Subscribe" from the "Share" menu (or in older builds it was in the "Collection" menu).
    2. -
  2. Enter a URL like: "http://calendar.example.net/caldav.php/username/home/" (click "Subscribe")
     
    3. +
  3. Enter a URL like: "http://calendar.example.net/caldav.php/username/calendar/" (click "Subscribe")
     
  4. You will then be prompted for a username/password with in an expanded dialog. Enter these and click "Subscribe" again.
     
  5. You should now have a new calendar showing.
diff --git a/docs/website/clients/Evolution-details.php b/docs/website/clients/Evolution-details.php index 39691d1f..1727cb57 100644 --- a/docs/website/clients/Evolution-details.php +++ b/docs/website/clients/Evolution-details.php @@ -5,7 +5,7 @@ was little in the way of a repository available to test against until recently.<
  1. Select "File" then "New" then "Calendar" from the menus.
    2. -
  2. Choose a type of "CalDAV", enter a name, and a URL such as caldav://server.domain.name/caldav.php/username/home/, enter your user name for DAViCal and click "OK".
     
    3. +
  3. Choose a type of "CalDAV", enter a name, and a URL such as caldav://server.domain.name/caldav.php/username/calendar/, enter your user name for DAViCal and click "OK".
     
  4. You should now be prompted for a password for that username. Enter the password and your calendar should now show.
diff --git a/docs/website/clients/Interoperability-details.php b/docs/website/clients/Interoperability-details.php index 0a226fba..4bee40ac 100644 --- a/docs/website/clients/Interoperability-details.php +++ b/docs/website/clients/Interoperability-details.php @@ -10,13 +10,25 @@ that Mulberry does it.

  • Calendar namespace
    • -

    The host name is, of course, up to you. The 'root path' should be /caldav.php/ and anything following that is the calendar namespace.

    -

    Within the calendar namespace DAViCal uses the first element of the path as the user or resource name, so that a client connecting at the root path -can see all of the (accessible) users and resources available to them (Mulberry displays this hierarchy) with any calendars below that.

    -

    Effectively this means that in Evolution, Sunbird and Lightning you should really specify a calendar URL which is something like:

    +

    The host name is, of course, up to you. The 'root path' should be +/caldav.php/ and anything following that is the calendar +namespace.

    + +

    Within the calendar namespace DAViCal uses the first element of the +path as the user or 'princpal' name, so that a client connecting at the +root path can see all of the (accessible) users and resources available +to them (Mulberry displays this hierarchy) with any calendars below that.

    + +

    This means that in Evolution, Lightning and other software wanting a +'calendar' URL you should specify a URL which is something like:

    -http://calendar.example.net/caldav.php/username/home/
+http://calendar.example.net/caldav.php/username/calendar/
    -

    Then, when more calendar client software sees it as useful to be able to browse that hierarchy, you won't be up for any heavy database manipulation.

    -

    I may well enforce this standard in some way before release 1.0, as well as auto-creating the collection records when Evolution, Lightning -or Sunbird attempt to store to a non-existent collection.

    + +

    DAViCal creates two collections automatically when a user is created. In +recent versions these are called 'calendar' and 'addressbook'. Some software +also makes it easy to create more calendars and addressbooks, or you can create +more through DAViCal's web interface, also.

    + +

    In older versions of DAViCal (pre 0.9.9.5) the default calendar was named 'home' +and there was no default addressbook.

    diff --git a/docs/website/clients/Mozilla-details.php b/docs/website/clients/Mozilla-details.php index 9a637fd9..99cbdc7c 100644 --- a/docs/website/clients/Mozilla-details.php +++ b/docs/website/clients/Mozilla-details.php @@ -8,7 +8,7 @@
    1. Select "New Calendar" from the "File" menu.
    2. Choose "On the Network" (click "Next")
       
      3. -
    3. Choose a format of "CalDAV" and enter a URL like: "http://calendar.example.net/caldav.php/username/home/" (click "Next")
       
      4. +
    4. Choose a format of "CalDAV" and enter a URL like: "http://calendar.example.net/caldav.php/username/calendar/" (click "Next")
       
    5. Give the calendar an appropriate display name, and choose a colour for events on this calendar. (click "Next")
       
    6. click "Finish"
    diff --git a/docs/website/clients/Other-details.php b/docs/website/clients/Other-details.php index 0ca4ca8e..f88cb9b7 100644 --- a/docs/website/clients/Other-details.php +++ b/docs/website/clients/Other-details.php @@ -6,3 +6,24 @@ against, but so far these are the only ones I have access to.

    If you want to point me at more free software that supports CalDAV, or send me free copies of such proprietary software, then I will add it to the list as well as make DAViCal work with it.

    + +

    In the general CalDAV terminology, client software will want to know +several facts about the CalDAV server. Some (like iCal and iOS) will try +and discover these facts for themselves, and others (like Lightning and +Evolution) will require you to enter some information. When they ask for +that information they will be asking for the following things:

    +
      +
    1. Where is the user's "home" collection?
      2. +
    2. Where is the user's "calendar" collection?
      3. +
    3. What is the server's domain name
      4. +
    + +

    Typically the answers, in DAViCal's case, are:

    +
      +
    1. .../caldav.php/username/
      2. +
    2. .../caldav.php/username/calendar/ (although in older versions the default calendar was called 'home' rather than 'calendar')
      3. +
    3. I can't help here - whatever you called it, I guess!
      4. +
    + +

    There could well be a wider range of information about many and varied client + software on the DAViCal Wiki as well. \ No newline at end of file