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

[Bug]: Move the sub folder settings json away from the UI's "config states" folder #362

Open
Lumerica opened this issue Nov 10, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Lumerica
Copy link

Describe the bug.

The new method to create custom sub folders saves the configuration to the json file "civitai_subfolders.json" in the sub folder "config states".
The sub folder "config state" is being continuously read in the background by the UI (at least in my test case Forge UI).
Since the civitai_subfolders.json does not meet the requirement format the console generate the line expecting "created_at" to be defined in the json file.

I think the configuration file itself should stay in the extension folder rather than put its configuration in a sub-folder that is being used by default.

Ps. its a minor issue if you ask me. not causing harm imo, just that its scary to think that an extension can put its config files in a default sub folder of the root directory of the UI.

Steps to reproduce the problem.

configure some sub folder. Any startup of the UI will generate the error
[ERROR]: Config states N:\GIT\ForgeManual\config_states\civitai_subfolders.json, "created_at" does not exist

Expected behavior

have the config file stored within the extension folder itself instead.

System info

Extension version: 807a21c
OS: Win 10
SD-WebUI version: Forge UI
Python: 3.10.10

Console logs

[ERROR]: Config states N:\GIT\ForgeManual\config_states\civitai_subfolders.json, "created_at" does not exist

Additional information

No response

@Lumerica Lumerica added the bug Something isn't working label Nov 10, 2024
@D0n-A
Copy link

D0n-A commented Nov 12, 2024

Duplicate: #349

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants