mirror of
https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git
synced 2026-11-05 00:17:25 +00:00
[GH-ISSUE #334] Custom settings cannot save in Forge #234
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
low priority
low priority
pull-request
question
waiting for feedback
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DominikDoom/a1111-sd-webui-tagcomplete#234
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @koopa990 on GitHub (Oct 14, 2025).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/334
I am using Forge via stability matrix.
@DominikDoom commented on GitHub (Oct 14, 2025):
Please specify the problem in more detail. Do all options not work, or just the ones you show in the screenshot? And is this a problem of the options actually not saving (so resetting to default on the next start), or just that the values you entered and saved seem to have no effect?
@koopa990 commented on GitHub (Oct 16, 2025):
just checked: this also affects other extensions. The custom values that were supposed to save, did not save on next launch.
@DominikDoom commented on GitHub (Oct 16, 2025):
Ok, so do any settings at all get saved? Not from extensions but from the base webui.
I don't know if installing via stability matrix changes something, but for the standalone webui the settings get written to a file called "config.json" in the webui root directory when you hit Apply. You could take a look at that file and check if/when it was last changed and if you can find the values from the settings UI there as you would expect. For tag autocomplete specifically, the settings will all have the prefix "tac_" you could search for.
If not, you probably either didn't apply the settings, or something prevented the file from being modified (like the file/folder being marked as read-only or insufficient permissions).
@koopa990 commented on GitHub (Oct 17, 2025):
Just tested: changing it in config.lua works. So that rules the change in UI not working
@DominikDoom commented on GitHub (Oct 17, 2025):
Just to make sure, you are hitting Apply Settings after changing the values, right? They won't save automatically just from changing the values in the UI.
Assuming yes, were you able to rule out any of the reasons I listed above, like missing write permission? That could be the case for example if you use Windows and installed the webui in Program Files or another folder not fully owned by your user, in which case the program would need to run with administrator rights to write there.
Other than what I already wrote earlier, I don't have too many other clues, so if none of that is the cause, I'd suggest opening an issue in the main forge or stability matrix repos since it doesn't seem like this or another single extension is the cause.
@koopa990 commented on GitHub (Oct 17, 2025):
Over at forge, they told me to screw off and share this to matrix and here...
Currently, I'm opening an issue with matrix
@koopa990 commented on GitHub (Oct 18, 2025):
Update: despite their one true solution to this issue, that still does not fix it. So... what now? Is Forge not 100% bug-free with SM?
@DominikDoom commented on GitHub (Oct 19, 2025):
To be frank, I don't know. I don't use Stability Matrix or Forge, so all I could do is guessing at best. And any further guessing would be useless with the amount of info I have.
It might help if you told me if you actually tried any or each of my suggestions, I'm still pretty much in the dark in regard to that. You haven't even told me if the settings in your first screenshots specifically were in any way relevant, so for all I know, it could still very easily be user error instead of an actual issue (no offense). I also can't judge the "one true solution" since you haven't said anything about that.
@koopa990 commented on GitHub (Oct 20, 2025):
I did check my folder permission to write- they look normal as intended.
What the other said was to hit Apply after making changes, then click on Restart from stability matrix console.
@DominikDoom commented on GitHub (Oct 21, 2025):
Ok, good to know. Just to throw in a few more ideas/questions, but other than that I have nothing else to suggest either: