ljleb

At some point we could consider using the existing ui to generate a string to append to the prompt instead of driving the controlnet settings directly. This would make it...

Are you sure? If you scroll up a bit, they should be there. To reuse the code from `/sdapi/v1/txt2img` and `/sdapi/v1/img2img` routes and extend them, we had to monkey patch...

Maybe we should move everything into the hijack to make sure all `/controlnet` routes stick together in the docs. Alternatively, find a way to reuse the Api code without hijacking...

Have you tried installing the extension, then restarting your webui completely? I suspect this may be caused by the monkey patch not taking place. This is what I see on...

Wait, why is everything listed under `/` instead of `/sdapi/v1` on your end? For me every route the ui defines before extensions is nested into `/sdapi/v1`.

I just tried these steps: 1. clone a fresh webui repo into a new directory 2. go to extensions tab > available > click on "Load from:" 3. click on...

> They changed completly the json structure, and the base64 image format is also not the same as the default base64 format used on original txt2img and img2img vanilla API....

> Really? Do I have an older version of webui? I literally cloned down the latest via: `git clone https://github.com/AUTOMATIC1111/stable-diffusion-webui.git` > > I'm on Windows, using Chrome. I used chrome...

Alright I just realized. *All* of your `/sdapi/v1` routes are gone. It's not the prefix that's missing, but every route defined under it. I think the hijack is doing something...

Thanks for the info. Are `/sdapi/v1` routes available if you disable the extension? what if you uninstall it and restart the webui completely? If the extension is causing the routes...