-
Notifications
You must be signed in to change notification settings - Fork 11
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
Webui first load problem with scripts #36
Comments
Fixed in dev: Do you mean webui can't run completely, or only these js callbacks? |
None of the buttons or lists work, I temporarily refresh the interface with CTRL+F5 and then it should be fine. |
Thanks for reporting. Committed fix. If the problems are gone, you can close the issue |
I have the same some times. Unfortunately it's not because these errors. I think it's because gradio wasn't designed for such big apps and a lot of extensions |
Yes, need to disable all unused extensions. Also in settings you can hide unused tabs For me, when this bug happens, I need to reopen the page, not just reload |
We have the problematic extension. Unfortunately the extension conflicts with Supermerger :( I tried it on Auto1111 and Forge. Only one of the extensions can be enabled, otherwise the error occurs. Is it calling some function or definition that might be the same? I don't know, unfortunately I am not a programmer. I report the problem to him. |
I confirm, enabled this, and got this error 😆 But after reopening it fixes. I enable it only if I need merge loras |
I have the latest version of both the plugin and Webui installed, the error also occurred on Forge. When I open Webui for the first time, the controls are not usable on it. I see this error in the Chrome console:
If I disable the extension, the webui runs fine. But then I get this message in the cmd console:
*** Extension "sd-webui-replacer" requires "sd-webui-segment-anything" which is disabled.
The segment-anything is not disabled, so the reverse would be correct:
*** Extension "sd-webui-replacer" is disabled.
The text was updated successfully, but these errors were encountered: