-
Notifications
You must be signed in to change notification settings - Fork 2k
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]: AttributeError: 'NoneType' object has no attribute '_id' #2136
Comments
in your |
Nothing on presets folder because I removed controlnet and tried to reinstall again, same problem. |
same issue here |
I don't know what caused this, but a new fresh install of SD got it to work again :/ |
I tried a lot of fixes, but none worked. Finally I had to reinstall as well. Took me half a day... But I can make my waifus again now, so overall not bad... |
Delete your AUTO1111 will complain the files don't exist on starting the server; don't worry, it's just a warning. You can recreate them by going to Hopefully this saves others from having to completely rebuild their install. |
For me it was the "txt2img/img2img UI item order" setting (Settings > User Interface). If you have changed it at all this extension throws all those errors on start up. Very annoying as I like having Scripts at the top of my UI. |
@huchenlei This issue is still happening on the latest commit if I alter the order of the UI. You marked this as closed, Was it supposed to have been fixed? |
Please follow instructions in this comment: |
That doesn't fix the issue. See #2136 (comment) It appears that Control Net is assuming the UI will have a specific structure but because the order of the UI was changed it leads to the gradio error. I don't mean to be pushy but this is a repeatable and narrow issue with the extension where it does not support a built in setting of Automatic1111 so I think this issue is deserving of a proper fix. |
I print the list |
Is there an existing issue for this?
What happened?
Can't even launch the WebUI when ControlNet is installed.
I updated the ControlNet and that's it.
Steps to reproduce the problem
Just open the WebUI
What should have happened?
The WebUI started normally.
Commit where the problem happens
webui: 5ef669de080814067961f28357256e8fe27544f4
controlnet: e67e017
What browsers do you use to access the UI ?
Mozilla Firefox
Command Line Arguments
List of enabled extensions
Pixel Art
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: