- Improved progress bar messages and layout, thanks @SanduRajapakse
- Improved icon status images, thanks @dbddhkpde
- Code and test cleanups, thanks @warwickmm
- Fixed an issue with rclone backend ignoring options, thanks @Bruceforce
- Added a fix for browsers with scripting disabled, thanks @Pectojin
- Added a button to dismiss all messages, thanks @Pectojin
- Added KeyStone v3 support to OpenStack backend, thanks @epol
- Updated translations, thanks to all translators!
- Fixed an issue that caused large log data to accumulate and break sending report/email status
- Added support for fine-grained control over how log data is reported via email, http and Jabber/XMPP
- Added support for sending JSON formatted data with the http report module
- Fixed an issue with MS Graph authentication, thanks @tygill
- Fixed a performance issue during file scanning, thanks @ltfish
- Added support for serializing results into json for all report modules and the run-script module as well, thanks @StephenGregory
- Added filter groups and a UI for it, thanks @tygill
- Fixed an issue where some paths were not reported via test-filters
- Fixed some issues with handling internal server settings, thanks @warwickmm
Proposal for a modification to the "State" display bar (Green info bar at the top)
Maybe I missed something in another topic, but:
- did filter groups replace the OS level filters?
- is there somewhere that explains how to use filter groups?
Default filters warning in 220.127.116.11_beta
Yes, filter groups are the new thing, and work cross-os.
Not sure if it was discussed here on the forum, but it was mentioned on Github:
Yes, the manual is updated:
Thanks for the clarification, and sorry for not seeing the
Exclude filter group section in the filters select list.
Backup stuck (?) at "Waiting for upload"
Duplicati 18.104.22.168_beta much slower than 22.214.171.124_beta
Verifying Backend Data
I’m assuming this is the cause of the “The supplied option
--default-filters is not supported and will be ignored” warnings I’ve seen some people reporting.
Am I correct in assuming this means that if you have
--default-filters enabled on pre-126.96.36.199 (so it’s excluding default OS level files) then upgrade to 188.8.131.52+ and do NOT shift to using the
Exclude filter group your backups will start INCLUDING those default OS level files (possibly making them run longer, take more destination space, and maybe more likely to run into open-file issues)?
Yes, I think so. We should perhaps have just deprecated the option and made it use the other exclude stuff, but since they have different exclude lists, maybe we are better of alerting users that things have changed.
That sounds like a good way to handle it.