Difference between revisions of "Tine2.0"

From dmfswiki
Jump to: navigation, search
Line 27: Line 27:
 
== Automatic service discovery ==
 
== Automatic service discovery ==
  
The following redirect rules are recommended for Apache users to make CalDAV-Sync and CardDAV-Sync (and other sync clients) work properly with Tine 2.0. These rules are known to work with recent releases, though other rule sets might work too.
+
The following redirect rules are recommended for Apache users to make CalDAV-Sync and CardDAV-Sync (and other sync clients) work properly with Tine 2.0 (see [https://www.tine20.org/wiki/index.php/Admins/Thunderbird-Synchronisation Tine 2.0 Wiki - Thunderbird-Synchronisation]). These rules are known to work with recent releases, though other rule sets might work too.
  
 
<pre>
 
<pre>

Revision as of 12:09, 6 November 2013

Tine 2.0 is an open source groupware solution.

Setup

CalDAV-Sync

Tine 2.0 supports CalDAV since version Milan. Please note that support for task sync via CalDAV has been added in Collin.

If the server is configured properly it should be sufficient to enter just the host name (see Automatic service discovery).

  • Server: the server name
  • Use SSL: tick accordingly
  • Username: your username
  • Password: your password

CardDAV-Sync

Tine 2.0 supports CalDAV since version Milan.

If the server is configured properly it should be sufficient to enter just the host name (see Automatic service discovery).

  • Server: the server name
  • Use SSL: tick accordingly
  • Username: your username
  • Password: your password

Automatic service discovery

The following redirect rules are recommended for Apache users to make CalDAV-Sync and CardDAV-Sync (and other sync clients) work properly with Tine 2.0 (see Tine 2.0 Wiki - Thunderbird-Synchronisation). These rules are known to work with recent releases, though other rule sets might work too.

# (Mobile) Synchronization
<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond   %{REQUEST_METHOD} !^(GET|POST)$

    # CalDAV / CardDAV
    RewriteRule ^$            /index.php?frontend=webdav [E=REMOTE_USER:%{HTTP:Authorization},L,QSA]
    RewriteRule ^addressbooks /index.php?frontend=webdav [E=REMOTE_USER:%{HTTP:Authorization},L,QSA]
    RewriteRule ^calendars    /index.php?frontend=webdav [E=REMOTE_USER:%{HTTP:Authorization},L,QSA]
    RewriteRule ^principals   /index.php?frontend=webdav [E=REMOTE_USER:%{HTTP:Authorization},L,QSA]
    RewriteRule ^webdav       /index.php?frontend=webdav [E=REMOTE_USER:%{HTTP:Authorization},L,QSA]

    # ActiveSync
    #RewriteRule ^Microsoft-Server-ActiveSync(.*) /index.php?frontend=activesync [E=REMOTE_USER:%{HTTP:Authorization},L,QSA]
</IfModule>

Known Issues

The latest release of Tine 2.0 (Collin) has a bug when it comes to shared calendars, see 0009204: "Foreign" events won't sync/show up via CalDAV.. Users don't see events in shared calendars unless they are an attendee of the event. To workaround that issue, either change the file Calendar/Frontend/WebDAV/Container.php as mentioned in the bug report or enable the option Synology Workaround (in newer releases this option is called Use compatible sync method) in the CalDAV-Sync account settings. Using the compatible sync method will cause more traffic and higher battery drain, so you probably want to try the first way first.