RCMCardDAV v4.0.2

• Fix #316: Incompatibility with Sabre/VObject version 4 preventing saving contacts using custom labels
• Fix: Default refresh time set to 1 sec in settings

RCMCardDAV v4.0.1

• Fix: Plugin version was not shown in about window for tarball installations
• Fix: Collation behavior was case-insensitive for MySQL (only). Now unified across the different supported DBMS.
• Fix #306: With MySQL, sync failure could occur when several custom labels where used that only differed in case
  (effect of previous issue).
• Fix #308: With SQLite, the initial sync after adding a new addressbook was not automatically triggered.

RCMCardDAV v4.0.0

This release contains changes to DB schema. The database will be migrated automatically upon login to roundcube.

• All changes from 4.0.0-alpha1
• Fix: Deletion of empty CATEGORIES-type groups
• Fix: Delete CATEGORIES-type groups from DB that become empty during a sync
• Fix: Renaming of empty CATEGORIES-type groups
• Fix: During deletion, do not rely on the DB's ON CASCADE DELETE because this is disabled by default for SQLite
• Fix: It was not possible to discover multiple addressbooks for an admin preset because of a wrong UNIQUE constraint in
  MySQL
• Fix: Catch exceptions thrown inside the plugin (avoid "white page" on error)
• Increase the maximum lengths of password, email and url fields
• Use transactions to synchronize concurrent operations on the same addressbook
  (data consistency issues may still occur with MySQL because of roundcube DB
  layer bug). For details, see DBSYNC.md.
• Unified database indexes across the different database backends: Create indexes for foreign key columns (PostgreSQL,
  SQLite)
• Fixed issues in the migration scripts and added SQL scripts showing the current DB schema
• Update hungarian translation (thanks to @tsabi)

RCMCardDAV v4.0.0-alpha1

Note: The Changelog for this version is not complete

This is an alpha release because I did not perform any tests on it. Nevertheless, it has many bugs fixed and I encourage
you to upgrade and report issues as you find them. The last release 3.0.3 has many issues that have been fixed with in
v4. I push this release early mainly because of the security issue reported. I'll continue working on remaining issues I
want to fix (note: all of them are also present in 3.0.3) for v4 and I intend release a more tested version and a more
detailed changelog within the next weeks.

• Security issue: It was possible for logged on users to read data from other user's addressbooks. Depending on the configuration, it
  might also have been possible to change data in their addressbooks. Thanks to @cnmicha for reporting this issue. This
  issue affects all previously released versions of RCMCardDAV using a database cache.
• Many bugs you reported and several more I discovered during refactoring have been fixed.
• The password scheme now defaults to encrypted (if you have not configured a password scheme, this will take effect
  automatically for newly stored password. If you don't want this, configure a password scheme in settings.php).
• The URL is not changeable after creation of an addressbook anymore. It used to work in specific, but not all cases. As
  the behavior is potentially broken and not easy to fix, it is removed for now.
• The two kinds of contact groups (VCard-based vs. CATEGORIES-based) are now transparently supported to the possible
  extent. The configuration switch is only meaningful concerning the type of group used when a new group is created
  from RCMCardDAV.
• The CardDAV interaction is moved to a library. It is essentially a
  complete rewrite of the code communicating with the CardDAV servers and includes interoperability tests with many
  common servers, see here.

RCMCardDAV v3.0.3

This is a patchlevel release with minor bugfixes and feature improvements:

• Translate the string "(from preset ...)"
• GSSAPI/NEGOTIATE/kerberos authentication support
• Proper array key quoting
• Add documentation of use_categories option for presets
• Correctly check field lengths for new addressbooks
• Support 'elastic' on Roundcube beta branch

v3.0.2

This release fixes an error in the latest migration that tried to access the now non-existant column sortorder.

DO NOT USE! USE 3.0.2 INSTEAD!

This release addresses issue #221 where 4-byte Unicode characters in vcards would not synchronize when using MySQL as backend.

It's about time

This release addresses a lot of issues since the 2.0.4 release, too numerous to list (mostly because I, too, forgot which they are).
I know there are still a lot of open issues at this moment, but keeping the 2.0.4 release would just add to the problem because people keep using that old version and reporting bugs and issues that were long since fixed.

v2.0.4

Finally, really fix TIMESTAMP datatype for newer MySQL versions.

v2.0.3

• Fix timestamp default value for good this time.