Config file is reset to default after every restart

[rjpeterson]

Describe the bug Any time I close and re-open Anki, any edits I've made to the Add-on config file reset to default.

To Reproduce Steps to reproduce the behavior:

1. Go to Anki Add-on menu and view config file for Anki Support.
2. Change "Also Written" to "Alsox Written"
3. Click "OK" and exit Anki
4. Reopen Anki and navigate to config file
5. See "Also Written"

Expected behavior Changes to config file are persistent through restarts.

Screenshots If applicable, add screenshots to help explain your problem.

Specs (please complete the following information):

• OS: Windows 7
• Anki Version 2.1.6
• Chinese Support Redux V091

[jdlorimer]

Thanks. The configuration code is next in line for a rewrite, and this should be an obsolete issue once the changes are made.

[rpetersnil]

I am having the same problem. Specifically, I am trying to change the TTS setting from Google (PRC) to Google (Taiwan). I assume that the correct way to do this (on Mac OS latest Anki client) is to go the Tools -> Add-ons -> Chinese Support Redux v0100 and hit the Config button. I get a text box with the config in it. Changing the text in the box does not take effect in the app, and restarting the app resets the text. I also tried changing the config.json directly after hitting View Files, but perhaps it isn't being rebuilt, as that seems to have no effect as well.

[vintotal]

The problem is unfortunately still present using Anki 2.1.9. Field edition is not saved (I wanted Taïwan pronunciation too!). :+1: I tried to edit the config.json file directly to see if changes can be persistent this way like rpetersnil; they are not. When I click restore defaults when modifying config within Anki, it shows the modified config.json though.

[jdlorimer]

This issue is different to what I initially thought, since I didn't read carefully enough.

The only configuration that is expected to persist between restarts is controlled by the Chinese menu options. Everything else is unsupported at this stage.

As I said, this will be overhauled in the future (although "next in line" was a lie).

Thanks for your patience.

[666David]

I'm still experiencing this issue in November 2019. Will there be a fix soon? Or am I doing something wrong?

[vintotal]

I'm still experiencing this issue in November 2019. Will there be a fix soon? Or am I doing something wrong?

The problem is still in place and is supposed to be fix when reaching version 1.0, which has no release date yet. We have to be patient. I hope it will be release before Anki 2.0 becomes unusable on 1 January 2020. Maybe there is a way to manually edit the fields of the config.json inside a zip package, then install it manually to Anki without downloading using the numbered install code? :-)

[jdlorimer]

I'll probably have time to have a look at this again, once the next release is live.

I really think Damien took the wrong approach to config management. I find the whole thing completely unintuitive, so I've just tried to go with sane defaults + some menu options, while avoiding the time-wasting configManager stuff built into Anki. But as you can see, this approach has not exactly been a success so far.