OK, I’ve pushed version 1.5.2, this should make it work again on Stash versions without custom field support for tags.
Maybe use the “Download Config“ feature to back up your settings, just in case, I couldn’t really test with an older version, so I just tested with a non-existant field in the current one as error trigger.
Hey thanks for taking the time! By download config do you mean a backuped .sqlite.? I’m having a hard time finding download config in stash
No, directly in the settings dialog of the Plugin, there are Buttons for “Download Config“ and “Upload Config“, just as a config import export mechanism specifically for the plugin.
It worked! Thank you!
Help, I have potentially fucked my FastTagger in trying to circumvent a bug!
Fast Tagger has the option to set a Tag Group to only appear if you select a specific tag. However, an issue arises if you want to reset that Tag Group back to always appear, instead of only with that specific tag: You MUST set that tag group to a new tag, and there are no options for a “None” tag or something similar. If you try to deselect that original tag, it’ll force that Tag Group to be set under that tag again.
The only workaround I’ve found so far is to completely delete and remake the affected Tag Group. However, that is not the issue I face now.
I set a Tag Group to be for a specific tag, then attempted to fix the above issue by deleting that set tag. This immediately caused a “something went wrong” issue, and now every time I open Settings under Quick Tag Editor, it again causes that “something went wrong issue”. I am now prevented from organizing or making new tag groups.
I’ve tried uninstalling the plugin, but the issue still persists after a reinstall. Please help!
I would try to delete the condition tag in the .json file (or in your config file). Or the tag group itself.
Or you could create a tag with the same “tag id” that you deleted, that might fix it.
The deleted tag issue should be fixed in 1.5.3 released earlier today (thanks again for the report, and sorry for the inconvenience).
I’ve just pushed version 1.5.4, that should fix this behavior, the “X“ in the dropdown should now properly clear the selected tag. Let’s not talk about the cause, not my smartest moment 