search

DominikDoom / a1111-sd-webui-tagcomplete

Booru style tag autocompletion for AUTOMATIC1111's Stable Diffusion web UI
MIT License
2.55k stars 306 forks source link

wildcards no longer autocompleting #241

Closed kenwud closed 1 year ago

kenwud commented 1 year ago

ive tried deleting and reinstalling the extension, but "__" no longer autocompletes to the list of wildcards.. bit bash terminal into the extension directory command git reset --hard 5067afeee95b9a742742333c67837cd35d5d732a seems to have resolved the issue

bWm-nubby commented 1 year ago

I had the same experience. My wildcards are in the default location for Tsukreya/Umi-AI-Wildcards I was previously using Tsukreya/Umi-AI-debloat and updated to the updated one when I noticed tagcomplete was unable to find them in the old extension but it did not work with the new extension either.

CCpt5 commented 1 year ago

Same here. I rolled back to an earlier commit since this was bugging me. Thanks for raising the issue. Hopefully there's a fix forthcoming.

I rolled back (git checked out) e23bb6d4 and it's works fine at this point (3 weeks back).

DominikDoom commented 1 year ago

Can't reproduce, everything works like normal for me on the current version. I also tried it on a fresh installation with default settings, which made no difference. I tried the wildcards @bWm-nubby mentioned, that works too.

Can you give me more details on your configuration? OS, Browser, Settings, etc. Also, force-refresh the site using CTRL+F5, the issue might be old files in the wrong format being loaded instead of the new one required after the recent updates. Check your browser console for errors (CTRL+SHIFT+I), if something goes wrong while loading it should be visible there. Also related to that, please enter wildcardExtFiles in the console to print out the variable and tell me if it has the expected content.

DominikDoom commented 1 year ago

Scratch that, I was able to find an issue. The problem was not the third-party wildcards, but the old school <webui root>/scripts/wildcards missing. The extension accidentally tried to load these even if they didn't exist. I had some files left there from testing so it didn't happen to me, but most people would've replaced that with the extension version or never had them in the first place.

If you update to the newest version, it should work for you now.