DominikDoom/a1111-sd-webui-tagcomplete

Fork 0

mirror of https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git synced 2026-11-05 00:17:25 +00:00

[GH-ISSUE #157] Does not show up anymore #113

New issue

Closed

opened 2026-10-30 21:19:33 +00:00 by bsakaguchi · 9 comments

bsakaguchi commented

2026-10-30 21:19:33 +00:00

Owner

Originally created by @hexahigh on GitHub (Apr 9, 2023).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/157

I recently updated python version and updated the webui. I dont know what could have caused this but after doing this the autocomplete popup no longer shows up. I get alot of error in the javascript console on my browser when typing something in but this could be completely unrelated. I tried reinstalling the extension but it still doesnt work.

Originally created by @hexahigh on GitHub (Apr 9, 2023). Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/157 I recently updated python version and updated the webui. I dont know what could have caused this but after doing this the autocomplete popup no longer shows up. I get alot of error in the javascript console on my browser when typing something in but this could be completely unrelated. I tried reinstalling the extension but it still doesnt work.

bsakaguchi closed this issue

2026-10-30 21:19:33 +00:00

bsakaguchi commented

2026-10-30 21:19:34 +00:00

Author

Owner

@DominikDoom commented on GitHub (Apr 9, 2023):

Well, what are the errors? Even if they are unrelated, they might still be a good starting point.
But it's likely they are, since you said they appear while typing. The script listens to textbox changes and executes a function on every key press, so it would fit your description.

@DominikDoom commented on GitHub (Apr 9, 2023): Well, what are the errors? Even if they are unrelated, they might still be a good starting point. But it's likely they are, since you said they appear while typing. The script listens to textbox changes and executes a function on every key press, so it would fit your description.

bsakaguchi commented

2026-10-30 21:19:34 +00:00

Author

Owner

@hexahigh commented on GitHub (Apr 9, 2023):

Weirdly enough the errors stopped appearing after making this issue. It still doesnt work but im only getting one error.

console-export-2023-4-9_18-56-14.txt

@hexahigh commented on GitHub (Apr 9, 2023): Weirdly enough the errors stopped appearing after making this issue. It still doesnt work but im only getting one error. [console-export-2023-4-9_18-56-14.txt](https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/files/11185923/console-export-2023-4-9_18-56-14.txt)

bsakaguchi commented

2026-10-30 21:19:34 +00:00

Author

Owner

@hexahigh commented on GitHub (Apr 9, 2023):

The error comes from the extension

@hexahigh commented on GitHub (Apr 9, 2023): The error comes from the extension

bsakaguchi commented

2026-10-30 21:19:34 +00:00

Author

Owner

@hexahigh commented on GitHub (Apr 9, 2023):

Here is my launch command if that could be what causes the issue:

py -3.10 launch.py --share --disable-safe-unpickle --no-half-vae --xformers --reinstall-xformers --reinstall-torch --enable-insecure-extension- --gradio-queue --remotemoe
pause

@hexahigh commented on GitHub (Apr 9, 2023): Here is my launch command if that could be what causes the issue: <pre> py -3.10 launch.py --share --disable-safe-unpickle --no-half-vae --xformers --reinstall-xformers --reinstall-torch --enable-insecure-extension- --gradio-queue --remotemoe pause <pre<

bsakaguchi commented

2026-10-30 21:19:35 +00:00

Author

Owner

@DominikDoom commented on GitHub (Apr 9, 2023):

Is the extension up to date? It says in the error that modelDropdown is null, which was an issue after the webui updated to a newer Gradio version and some UI elements changed the way they function. But that should already be fixed in recent versions of tag-autocomplete, so the issue might be if you updated one but not the other.

@DominikDoom commented on GitHub (Apr 9, 2023): Is the extension up to date? It says in the error that modelDropdown is null, which was an issue after the webui updated to a newer Gradio version and some UI elements changed the way they function. But that should already be fixed in recent versions of tag-autocomplete, so the issue might be if you updated one but not the other.

bsakaguchi commented

2026-10-30 21:19:35 +00:00

Author

Owner

@hexahigh commented on GitHub (Apr 9, 2023):

In the webui it says its up to date but i will try manually deleting the extension and reinstalling

@hexahigh commented on GitHub (Apr 9, 2023): In the webui it says its up to date but i will try manually deleting the extension and reinstalling

bsakaguchi commented

2026-10-30 21:19:35 +00:00

Author

Owner

@hexahigh commented on GitHub (Apr 9, 2023):

That was the issue. The webui said it was up-to-date but it was over 300 changes behind.

@hexahigh commented on GitHub (Apr 9, 2023): That was the issue. The webui said it was up-to-date but it was over 300 changes behind.

bsakaguchi commented

2026-10-30 21:19:35 +00:00

Author

Owner

@hexahigh commented on GitHub (Apr 9, 2023):

Thanks alot for the help

@hexahigh commented on GitHub (Apr 9, 2023): Thanks alot for the help

bsakaguchi commented

2026-10-30 21:19:35 +00:00

Author

Owner

@DominikDoom commented on GitHub (Apr 9, 2023):

Glad I could help you!
Although the up-to-date display in the webui should be correct. It directly compares the git head states to see if you're behind, so unless you switched to an older branch manually at some point it should be accurate. It could also just be another issue with loading or the cache that resolved itself after a clean reinstall though.

@DominikDoom commented on GitHub (Apr 9, 2023): Glad I could help you! Although the up-to-date display in the webui should be correct. It directly compares the git head states to see if you're behind, so unless you switched to an older branch manually at some point it should be accurate. It could also just be another issue with loading or the cache that resolved itself after a clean reinstall though.