Release: 2.0.3.5 (canary) 2018-04-13

2.0.3.5-2.0.3.5_canary_2018-04-13

  • 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
4 Likes

Maybe I missed something in another topic, but:

  1. did filter groups replace the OS level filters?
  2. is there somewhere that explains how to use filter groups?

Thanks.

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:
https://duplicati.readthedocs.io/en/latest/appendix-d-filters/

2 Likes

Perfect!

Thanks for the clarification, and sorry for not seeing the Exclude filter group section in the filters select list.
image

1 Like

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-2.0.3.5 (so it’s excluding default OS level files) then upgrade to 2.0.3.5+ 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.

So I also got this warning on MacOS after upgrade from 2.0.3.3beta to 2.0.4.23beta. “The supplied option —default-filters is not supported and will be ignored”. My default-filter is OSX under Advanced Options. And my Exclude Filter list has checked Hidden Files, System Files and Temporary Files. I assume something changed with the upgrade and one of the settings is no longer supported. Which one?

Default filters warning in 2.0.4.5_beta says a hard refresh solved it (but filters do reduce performance).

If it doesn’t solve it, that thread might be a good place to seek further advice on what to do to resolve it.

Warning --default-filters is not supported #3532 also reported hard refresh (its method varies) solved it.

How to Hard Refresh pages in your browser, on a Mac (Safari, Chrome, Firefox, and Opera)

v2.0.4.6-2.0.4.6_canary_2018-12-11

Added cache-buster for all local static files, thanks @LacunaSoftware

but unfortunately v2.0.4.23-2.0.4.23_beta_2019-07-14 is 2.0.4.5 plus an urgent warning, so lacks the fix.