Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

export settings #28840

Open
mj2ks opened this issue Jan 9, 2025 · 2 comments
Open

export settings #28840

mj2ks opened this issue Jan 9, 2025 · 2 comments

Comments

@mj2ks
Copy link

mj2ks commented Jan 9, 2025

Is your feature request related to a problem?

every time after update/rollback failures you have to re-authorize. that's okay - every time all the settings are lost and you have to set them up again.

do at least import/export settings. but in general it's a bug. okay authorization can fail for security reasons. but what do the settings have to do with it?

Describe the solution you'd like

the settings shouldn't be reset

Describe alternatives you've considered

Additional context

No response

@john-preston
Copy link
Member

@mj2ks What do you mean by update/rollback failures? If you update older version to a newer version, everything should persist (authorization, settings), version rollback isn't supported, older version doesn't read data files of a newer version.

@mj2ks
Copy link
Author

mj2ks commented Jan 9, 2025

@john-preston if there are problems in the new version, we return the old version and have to re-authorize and configure.

for example, after yesterday's update - the new version did not start at all - "segmentation error". I return the "backup" file - everything again authorization, configuration.

why should I update if the probability of such problems is 90%. works - do not touch. I turn off auto-update.

if there was import/export of settings - it would be much easier.

the program has data export, but no export of settings. fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants