RCMCardDAV v4.4.0

• MySQL/PostgreSQL: Increase maximum length limit for addressbook name (Fixes #382)
• Fix: log messages could go to the wrong logger (carddav_http.log) for a small part of the init code
• Support setting roundcube's collected senders/recipients to addressbooks from preset (Fixes #383)
• Provide tarball releases in two variants: Guzzle v6 (roundcube 1.5) and v7 (roundcube 1.6) (Fixes #385)

RCMCardDAV v4.3.0

• New: For preset addressbooks, are re-discovery is performed upon every login by default. This means that newly added
  addressbooks on the server are discovered and added, whereas addressbooks that have been removed from the server are
  also removed from roundcube.
  • NOTE TO ADMINS: If you are using addressbook presets, please read the documentation on the new preset setting
    rediscover_mode to decide if re-discovery is desired or not. The new default is functionally safe, but performance
    can be improved if the new behavior is not needed.
  • For manually-added addressbooks, this will require changes to the rcmcarddav data model, which is planned for
    version 5.
  • Version 5 will also have a more elaborate version of re-discovery that will allow to configure it such that it does
    not happen on every login.
• MySQL: Convert potentially used row format COMPACT (was default up to MySQL 5.7.8, Maria DB 10.2.1) to DYANMIC in
  migration 12, which would otherwise fail (Fixes #362). It requires some other settings that have to be configured in
  the MySQL server configuration additionally, all of which are also defaults since MySQL 5.7.7 / Maria DB 10.2.2.

RCMCardDAV v4.2.2

Fix #361: Detect login via OAuth and prevent usage of encrypted password scheme in this case. The passwords encrypted cannot be decrypted anymore when the access token changes. In case such passwords have already been stored to the DB, the user must enter and save the password via the preferences again. In case of an admin preset where the password is marked as a fixed field, the password should be updated on next login of the user.

RCMCardDAV v4.2.1

• Updated French translation (#355)
• Updated German translation
• Fix: Display error message when the sync fails (instead of showing a success message with a duration of -1 seconds)
• Fix: Display error message when a card cannot be updated because it changed on the server since the last sync.
• Fix #356: Don't create group vcards with duplicate members, don't fail to process them if we receive one from the
  server
• New: Action in the preferences to clear the local cache of an addressbook, to allow a full sync from scratch. This is
  meant to fix errors in the local state that cannot be repaired from incremental syncs, as might be the result of issue
  #356.

RCMCardDAV v4.2.0

• New: Support OAUTH2 authentication in a single-sign-on setup in conjunction with roundcube 1.5 OAUTH2 authentication.
  This enables to use the bearer token acquired during login by roundcube to also be used to authenticate with the
  CardDAV server. It is currently not possible to add addressbooks using a custom OAUTH2 provider, i.e. a different one
  than that used to log into roundcube.
• Fix #348: Load the carddav plugin in the calendar task. This enables usage of carddav addressbooks within the calendar
  plugin, for example for the purpose of the birthday calendar.

RCMCardDAV v4.1.2

• Fix #345: Crash during cropping of photos with X-ABCROP-RECTANGLE parameter when error occurred during crop, e.g. picture format not supported by php-gd.
• New: When exporting a VCard from a carddav addressbook, the export is now handled by rcmcarddav. The exported card is exactly the card on the server, including any properties not supported by roundcube / rcmcarddav. The only exception is the photo property: photos referenced by URI will be downloaded and stored inside the card; photos with X-ABCROP-RECTANGLE will be stored cropped. This is to improve interoperability with the importing application.
• Fix #345: When exporting a VCard from a carddav addressbook, the PHOTO property in the exported card contained an invalid value.

RCMCardDAV v4.1.1

• Fix: A fatal error would be raised when a password could not be decrypted, only on photo download. This would not be notable to the user (except for the photo not being displayed), but show up in the logs.
• Fix #339: Allow adding public/shared addressbooks by giving full URL. Discovery is still used if the given URL does not point to an addressbook directly, or points to an addressbook inside the user's addressbook home.

RCMCardDAV v4.1.0

UPDATE: I decided to go back to including the dependencies in the release tarball, since there are people with hosting packages that do not allow to run commands such as composer on the server. For those it is more convenient to get a tarball that just can be extracted to the plugins directory. I therefore updated the tarball carddav-v4.1.0.tar.gz. The instructions inside the tarball still are unchanged, but you can simply skip the composer steps. See an updated INSTALL.md on the master branch.

Original Release Notes:
This release adds support for instant messaging fields and speeds up sync with addressbooks where photos are stored separately from the vcards. Apart from that, there have been quite extensive refactorings to improve testability and static analysis, unfortunately bearing the risk that something got broken. Tests now exists for large parts of the backend, but the frontend is basically untested and will be focus for new features and tests in 4.2.0.

Database compatibility: For Postgres and SQLite3, the schema is unchanged to 4.0.4, meaning you can downgrade from 4.1.0 to 4.0.4 without changing the database. For MySQL, there was a small change (addition of a NOT NULL constraint) and it is not possible to downgrade to 4.0.4 without manually adapting the database schema.

Detailed list of user-visible changes:

• Fix: Prefer labels from X-ABLabel extension if available over standard labels
• Fix #317: Support specification of department with empty organization
• Support several levels of departments separated by semicolon that end up as structured value in the VCard
• Fix #318: Some attributes (e.g. gender) could not be deleted when updating a contact
• Fix #53: Only create displayname when not present in VCard / not provided by roundcube
• Fix #325: Roundcube setting for contact sorting field was not used
• Fix #279: More specific error message when syntactically wrong URL is entered for new addressbook
• Fix #328: Contact search with MySQL might not have returned all results
• Fix #332: When adding a new contact via "add to addressbook" from mail view, the email address was missing in the new
  card
• New: Download externally referenced photos on demand, drastically speeding up sync with when photos are stored
  separately from the VCard (e.g. iCloud). For details see #247.
• New: Support for instant messaging data fields and maiden name (resolves #46). Interoperability with other
  CardDAV clients suffers some caveats, but I tried my best to achieve maximum possible interoperability. See
  IMPP.md for the gory details.
• Removed a workaround that appears to be needed in the part to provide address data to the calendar plugin. It seems
  this is no longer the case for current versions of calendar.

RCMCardDAV v4.0.4

• Fix #321: Boolean settings in presets caused errors when trying to store the preset's addressbooks to the database
• Fix #322: The refresh time string from admin presets was not converted to seconds, causing errors or wrong values when
  storing the preset's addressbooks to the database
• Fix #324: Changes not immediately visible with postgresql (delete contact, add/remove contact to/from group)
• Fix: spurious error returned when creating VCard on Google

RCMCardDAV v4.0.3

• Allow release 1.0 of carddavclient in composer dependencies
• No changes to the plugin itself

Release 1.0.0 of the carddavclient library includes a workaround to enable use of the efficient sync methods with sabre/dav. People using Baïkal with digest authentication can benefit from this.

You can read more about it in #294 and #188. Note that older versions of the carddavclient library work fine, too, but will fallback to slower methods for the synchronization.