That is the plan, I assume this is the one:
opened 10:17PM - 27 Feb 25 UTC
Stable blocker
Here are a few improvement suggestions:
https://forum.duplicati.com/t/release-2-… 1-0-109-canary-2025-02-11/20124/20
- [x] Inability to select from dropdown
- [x] Advanced options snapshot-policy doesn’t work.
- [x] General backup settings Encryption doesn’t work.
- [ ] Filters builder dropdown doesn’t work. Note that it’s hard to see invisible effects,
- [ ] Widespread lack of three-dot menu to see what the GUI is actually preparing.
- [ ] Job Database Placement editing was slightly unusual before, where buttons activated based on changes to the field. Now, the buttons don’t seem to give any sign of working.
- [x] Is the status bar hugely reduced? I can sometimes see it say Loading… but that’s not much status.
- [ ] Notifications are not highly visible. A notification stays inside the area which changes colors, but it is easy to overlook.
- [x] Edit of an existing ngax backup without a schedule shows me “Automatically run backups” toggled on.
- [ ] That backup has upload-unchanged-backups turned on in Advanced options, but not in ngclient.
- [ ] Job Create error report doesn’t seem to do anything. (bugreport?)
- [ ] About duplicati → Libraries → Details closes the text window but leaves an empty window with a Close button that doesn’t work. Need to exit the page to clear that up.
- [ ] About duplicati should maybe be About Duplicati. Isn’t the name capitalized? It used to be, but now the upper left corner also says duplicati
- [x] Current channel not displayed (stable (no label)/beta/experiemental/canary/debug)
- [ ] About used to give current version, and allow check for new. Is check anywhere now? I guess I can get current from About duplicati → System info. It’s right at the top, however further down is a huge number of things to expand. Under Options there are 138. The previous display was long, but at least right there. New is unreasonably hard.
Please keep posting issues, we will work on them.the backlog as exceedingly big, and most of the things just require minor fixes.
Is this different than ngax? It is picking the time-based retention, and expecting the user to enter some amount of days. What would you want it to do instead?
I created an issue for that .
I have added an issue for that .
Fixed in source.
ts678:
The Repair, Delete, and Restore buttons don’t reflect the DB existence as ngax does.
“Placement” section isn’t healthy either. It looks like it wants to follow the ngax model, however it’s not doing well at button highlighting or a response to pushing the buttons. Buttons seem to highlight only when the correct DB path is used, which is backwards. Current ngax model feels a little reversed (like RPN ) for new user, but is it to be kept?
I have created an issue , feel free to add details.
I have confirmed this and created an issue .
Thanks. There are more of these on the way.
Finally
1 Like
, thanks for confirming.