Description: Currently document versions must be created either manually or upon saving while closing (saving before closing cannot create a new version). For users wishing to automatically save versions of their document, the current functionality is risky as it encourages closing before saving, creating the possibility of accidentally pressing the "discard changes" button. To fix this, change the "always save new version on closing" function to always create a new version from the most recent save whenever the the program is closed (assuming there are actually changes from the previous version). Additionally, it would be nice to have an option to create a version from every save (not just when closing), and another option to enable automatic version creation by default for new documents. Steps to Reproduce: 1.Check "Always save new version on closing" in File>Versions 2.Save changes to document 3.Close Writer Actual Results: No new version is created. Expected Results: A new version is created from the most recent save prior to exiting. Reproducible: Always User Profile Reset: No Additional Info: Version: 24.8.3.2 (X86_64) / LibreOffice Community Build ID: 48a6bac9e7e268aeb4c3483fcf825c94556d9f92 CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
I wonder if we can merge this with bug 88994. The mockup suggests to have the version control option on the Save-As dialog (and keep the setting for Save).
(In reply to b.e.m.008 from comment #0) > Description: > Currently document versions must be created either manually or upon saving > while closing (saving before closing cannot create a new version). For users > wishing to automatically save versions of their document, the current > functionality is risky as it encourages closing before saving, creating the > possibility of accidentally pressing the "discard changes" button. Note that there's an extension that handles versioning: https://extensions.libreoffice.org/en/extensions/show/5744
*** This bug has been marked as a duplicate of bug 88994 ***