Welcome to the Release Notes for Nuxeo Drive 5.2.1
A regression introduced in previous versions that would break credentials renewal when using Amazon S3 direct upload capabilities was fixed.
More on JIRA ticket NXPY-223.
We improved how a given local folder could be used for the synchronization content. New checks are more specifics and less restrictives.
More on JIRA ticket NXDRIVE-2644.
Our Sentry usage showed lots of errors about "database or disk is full". After deep investigations, we hope the situation will now be better: temporary databases are now handled in memory (RAM) instead of a temporary folder. The later was the source of all reported problems were it may be limited in disk space and blocking our database actions while there are still enough disk space at the current location of those databases.
More on JIRA ticket NXDRIVE-2646.
Users were able to add an account using their credentials but for one reason or another they do not have enough rights to call
NuxeoDrive.* automation operations. Such case is now well handled.
More on JIRA ticket NXDRIVE-2647.
The local folder icon in the system tray menu is now disabled when the synchronization is.
More on JIRA ticket NXDRIVE-2651.
When the synchronization is disabled, there was an issue that won't start transferring files when doing a Direct Transfer right after having added a new account. This is now fixed.
More on JIRA ticket NXDRIVE-2643.
The CSV export button click area was not covering the CSV icon. One had to click on the right on the icon to apply the action. The click area is now correctly set.
More on JIRA ticket NXDRIVE-2650.
Following the work done on the version 5.2.0 where the synchronization became a feature, we polished even more the behavior.
Now, when the synchronization is disabled, the application won't do anymore actions on the local folder (like checking its existence, checking extended attributes support, calling NuxeoDrive.* operations, ...).
More on JIRA ticket NXDRIVE-2641.