Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
home:lrupp:roundcube
roundcubemail-plugin-rcmcarddav
roundcubemail-plugin-rcmcarddav.changes
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File roundcubemail-plugin-rcmcarddav.changes of Package roundcubemail-plugin-rcmcarddav
------------------------------------------------------------------- Fri Jun 7 17:56:30 UTC 2024 - Lars Vogdt <lars@linux-schulserver.de> - update to 5.1.0 * Allow to hide contacts without email also for user-defined addressbooks (Fixes #429) * Re-introduced option preemptive_basic_auth to send HTTP basic Authorization header with every request. Also settable via user-interface. (Fixes #407) * Support setting roundcube's default addressbook to an addressbook from a preset (Fixes #440) * New option ssl_noverify to disable verification of the CardDAV server`s SSL certificate in HTTPS connections. Also settable via user-interface. ------------------------------------------------------------------- Mon Apr 24 10:56:21 UTC 2023 - lars@linux-schulserver.de - 5.0.1 - update to 5.0.1 * Fix: Removed string interpolation variants deprecated with PHP 8.2 Changes since 5.0.0: NOTE: Before upgrading to v5, please read the upgrade notes in /usr/share/doc/packages/roundcubemail-plugin-rcmcarddav/README.md * Minimum supported PHP version for 5.0 is PHP 7.4 (Fixes #414) * Fix: Internal server error with PHP8 when searching address fields of contacts (Fixes: #410) * Fix: Assertion failure in DelayedPhotoLoader (Fixes: #404) * Fixes for better handling of incoming vCard4 (Fixes: #411) + Handle data-URI-style inline PHOTO as used in vCard4 + Use VCard conversion to handle v4 properties such as KIND=group for which extensions are used in v3 vCards * Fix: Do not attempt to download photos from URIs with unsupported URI scheme (supported are http and https) (#411) * When an invalid value is submitted in one of the settings forms, RCMCardDAV will now abort with an error. Previous versions of RCMCardDAV would ignore the value when possible an instead keep the existing value or use a default value. * Backend will refuse Frontend request to remove user account created from preset * On initial installation of RCMCardDAV, the database schema is created from a single script with the current schema version. Previous versions incrementally executed all migration scripts since the very beginning (Fixes #395) * In the settings forms, some simple browser form validation has been added (Fixes #400) * Changes to the data model RCMCardDAV never had the notion of an account in its data model. In its early releases, it was necessary for the user to individually specify each addressbook by its URL. Later on, auto-discovery of all addressbooks on the server was added, but after the discovery these addressbooks existed as independent objects in the database and RCMCardDAV did not keep any track that they belong to one account. The addressbooks created from admin presets are an exception to this, as they are linked by virtue of belonging to the same admin preset. This is why it was possible to add re-discovery (only) for admin presets in v4.3. The old data model has a number of issues: Smaller annoyances, such as the user having to edit a changed password in each addressbook of the account upon password change. But also larger issues, such as the inability to perform a rediscovery on a user-added account, as for being able to determine new and removed addressbooks, we need to have an idea of which addressbooks belong to one account. With v5, RCMCardDAV gets accounts in its data model, which maintain the data common to all addressbooks of an account (particularly the credentials), with each addressbook belonging to an account. The database migration scripts try to identify the addressbooks belonging to the same account. For addressbooks created from an admin preset, this is easy and one account will be created. For user-created addressbooks, an account will be created for the addressbooks that have a common parent URL (i.e. URL with the last path component removed is the same) and use the same username. If this heuristic fails, additional accounts will result and the user will have to delete the extra accounts and perform a rediscovery on the remaining account to have the addressbooks wrongly assigned to other accounts added to the retained account. This change also means that it is now possible for RCMCardDAV to store accounts with no addressbooks at all, which is a state that may exist on the server and lays the basics for possible future features such as adding new addressbooks to the server from within RCMCardDAV. Older changes: * 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. * 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. * 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. * 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. * MySQL/PostgreSQL: Increase maximum length limit for addressbook name (Fixes #382) * Properly set and interpret TYPE parameters, especially for TEL (Fixes #390) * RCMCardDAV now sets the PRODID property when it creates or modifies a vcard * 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) * 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. Updated translations * Fix #348: Load the carddav plugin in the calendar task. This enables usage of carddav addressbooks within the calendar * Fix: Display error message when the sync fails * 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 * Updated translations * 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. ------------------------------------------------------------------- Wed Jun 23 11:04:40 UTC 2021 - lars@linux-schulserver.de - 4.1.2 - update to 4.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. ------------------------------------------------------------------- Mon May 10 17:02:20 UTC 2021 - lars@linux-schulserver.de - 4.1.1 - update to 4.1.1 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. * 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. * 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. * 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. * 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 * 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 * 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 #316: Incompatibility with Sabre/VObject version 4 preventing saving contacts using custom labels * Fix: Default refresh time set to 1 sec in settings * 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. * Allow release 1.0 of carddavclient in composer dependencies * 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 - create and use vendor-tarball - remove documentation files from plugin directory ------------------------------------------------------------------- Sat Jul 4 20:35:47 UTC 2020 - Lars Vogdt <lars@linux-schulserver.de> - require mod_php_any instead of mod_php ------------------------------------------------------------------- Wed Jun 10 13:55:18 UTC 2020 - lars@linux-schulserver.de - 3.0.3 - initial version
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor
