ransome1 / sleek

todo.txt manager for Linux, Windows and MacOS, free and open-source (FOSS)
https://github.com/ransome1/sleek/wiki
MIT License
1.28k stars 99 forks source link

On software version updates, the settings are erased #610

Closed DeflateAwning closed 6 months ago

DeflateAwning commented 6 months ago

Bug Report

App Version: 2.0.2 (and during the update to every previous version)

Platform: Linux and Windows

Installation Method: GitHub Release

Bug Description: Settings (like "Append creation date...") always get erased when an update is performed. It'd be nice not to have to worry about updates erasing these settings.

It might not have been a priority before, but having a settings migration procedure would be awesome now that there are v2 "stable" releases.

Steps to Reproduce:

  1. Change a setting.
  2. Update.
  3. See that the settings are erased.

Expected Behavior: Settings not be reset to default.

Actual Behavior: Settings get reset to default.

Additional Information: Happens cross-platfrom and on every version update.

ransome1 commented 6 months ago

With 2.0.1 the migration has been implemented. I just double checked it by downloading 2.0.1 from GitHub, starting and configuring it and then doing the update to 2.0.2. The update is done by just deleting 2.0.1 and downloading 2.0.2. All settings persisted on my end (macOS).

Happens cross-platfrom and on every version update. Can you please provide more details on how you update. What versions you use and so forth.

DeflateAwning commented 6 months ago

Hmm this upgrade was from 2.0.0 to 2.0.2. Do you expect it would've upgraded well? Perhaps I won't have the issue next upgrade.

ransome1 commented 6 months ago

mmhh, I also tried the jump from 2.0.0 to 2.0.2 just now and it upgraded without loosing the settings.

DeflateAwning commented 6 months ago

Hmm, was on Linux Mint, installed via the .deb I believe.

Perhaps we can leave it for now, and I'll provide a better repro if it happens again.

Feel free to close the issue if you'd prefer, and I can re-open one next time. I'm not certain I didn't imagine it happening.

DeflateAwning commented 6 months ago

Just upgraded from 2.0.2 to 2.0.3, and did not have this issue. Sorry for the false alarm!

ransome1 commented 6 months ago

Sorry for the false alarm!

No worries :)