Deck won't round-trip. about crowdanki HOT 7 CLOSED

What seems to have happened is that the deck config uuid, which is listed twice in the json file, had got out of sync with itself somehow.

Fiddling it by hand in the json and then importing the deck has fixed the issue for me.

from crowdanki.

huh, let me know if it happens again!

from crowdanki.

It happened again. I think all you need to do to provoke it is to change the options group of your deck. It would be much better if the options stuff wasn't exported anyway!

from crowdanki.

Specifically the deck_config_uuid doesn't change, but the deck_configurations/crowdanki_uuid does, and this makes the file un-importable.

from crowdanki.

I am also experiencing this problem, also triggered by differing options groups.

Since this breaks one of the core use cases of the plug-in (sharing decks between people, who will typically want different rates of new cards per day, etc.), would it make sense to disable options group export/import for now and then make re-enabling it a feature for the future?

from crowdanki.

there is no easy way to just disable it. setting https://github.com/Stvad/CrowdAnki/blob/master/crowd_anki/representation/deck.py#L130 to false can be a quick hack for the update use case. but just setting it to false would likely break the fresh import scenario.
To make this work, the default behavior that'd choose the deck config to be default if it's not found or something like that is required here

from crowdanki.

Looking at the error message and the description, I think that the root issue here is the same as #106 and #116!

(This issue also includes a request to avoid exporting/importing the deck config:

Since this breaks one of the core use cases of the plug-in (sharing decks between people, who will typically want different rates of new cards per day, etc.),

but that's already fully covered by #31.)

from crowdanki.