mirror of
https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git
synced 2026-11-05 00:17:25 +00:00
[GH-ISSUE #231] Stopped working entirely #164
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
low priority
low priority
pull-request
question
waiting for feedback
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DominikDoom/a1111-sd-webui-tagcomplete#164
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @IZA09 on GitHub (Sep 9, 2023).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/231
after reinstalling automatic1111 after a decently long break, i reinstalled the extension through the interface itself. unfortunately nothing seems to be active, nothing pops up as i type, and ive tried removing all other extensions, installing the extension through the other methods, and even just copied over the extension from my old 1111 folder because i knew it worked there, unfortunately nothing semes to be working. the settings pop up and by all accounts the interface recognizes the extension, but literally nothing is happening. something tells me it has to do with the updated interface but im not entirely sure.
edit: i reverted back down to 1.5.2 from the latest version i was initially using 1.6.0 and it works like it should. so evidently something in the newest version is messing with the extension.
@DominikDoom commented on GitHub (Sep 9, 2023):
I am using it fine on 1.6.0, so that shouldn't be the issue. Fresh install through the UI also works without problems for me.
Some things to try out:
<webui root>/config.jsonfile. This will reset all settings to the default, to ensure that the issue isn't some kind of misconfigurationThe most important one is checking for errors in the browser console, I need that info to help you further.
@IZA09 commented on GitHub (Sep 9, 2023):
unfortunately i don't see a thing. I've gone through your steps and still nothing. the extension is the only one active as well. nowhere on the web console or my cmd console do i see an error. ive tried on a different browser just in case but no luck. its a bit frustrating at this point.
@DominikDoom commented on GitHub (Sep 9, 2023):
Can you show me your settings page for tag autocomplete? There shouldn't be breaking changes regarding the webui version there, but that's the only thing I can think of for now where something could be wrong, if no errors show anywhere else.
@IZA09 commented on GitHub (Sep 9, 2023):
everything is default and untouched
@DominikDoom commented on GitHub (Sep 9, 2023):
If you just enter
allTagsin your browser console, does anything show up? To make sure the file gets loaded.@IZA09 commented on GitHub (Sep 9, 2023):
this pops up. i apologize im not very tech savvy its possible i could be missing some kind of super specific prerequisite. but then again, it worked just earlier with the older ui.
@DominikDoom commented on GitHub (Sep 9, 2023):
Well, if that isn't found on the webui page, it means the javascript part of the extension isn't loaded at all (assuming you entered it on the webui page, in another tab it wouldn't work of course).
Why that is the case is a different question.
You can try closing & restarting the webui entirely and then force-refresh the page with CTRL+F5 after it is loaded up again. Might be a cache issue which would be cleared in that case.
Also, do a file search for "__globals.js" in your extensions folder. It might be a problem if some other extension uses the same name.
@IZA09 commented on GitHub (Sep 9, 2023):
i should probably mention that im using opera.
running alltags in chrome brings different results, though neither are affected by CTRL+F5.
and lastly as this is the only extension in the extension folder, there is only one "__globals.js". its own.
i have a sneaking suspicion this is some form of user error and a apologies for bothering with this if the solution ends up being something trivial.
@DominikDoom commented on GitHub (Sep 9, 2023):
But the completion itself doesn't work in chrome too, right? Both are chromium, so they should be similar enough.
With all these other things we already tried I am running out of ideas too. I never had a case this far where it doesn't work without any error messages being shown and with default options. And also no clue why this only affects v1.6.0 for you, pretty sure nothing about extension loading changed there.
Another thing to try would be right clicking the prompt textbox and choosing Inspect.
If the extension is loaded correctly it would show
autocompleteParentnext to it:The only other thing I can think of would be to make sure no browser extension like an adblocker interferes, and if all else fails trying a fresh install of the webui itself / deleting and regenerating the venv. But that seems unlikely.
@IZA09 commented on GitHub (Sep 9, 2023):
its there.
yes in chrome nothing pops up all the same. i recently switched to opera so i assumed it was some weird incompatibility but apperantly its not. i dont mind just rolling back to the older ui, but id still like to understand what it is that's wrong here.
@DominikDoom commented on GitHub (Sep 9, 2023):
Huh, it is there? Now I really wonder what's going on here.
As a test, keep open this view and have an eye on it while you type something. It should change the
display: none;at the bottom todisplay: flex;.If it doesn't, try selecting it in the list and uncheck this:
(should be either to the right or below the list of elements)
@IZA09 commented on GitHub (Sep 9, 2023):
well here's a deviation. mine looks nothing like that.
this is... correct?
@DominikDoom commented on GitHub (Sep 9, 2023):
No no, I meant select the autocompleteParent one below that.
If you type anything before that would normally show the popup, doing that would force it visible to see if the list is filled correctly.
@IZA09 commented on GitHub (Sep 9, 2023):
oh whoops. well yes it does in fact change from "none" to "flex" along with a change in the px, so it looks like its working, but something is preventing the actual asset from showing up
@DominikDoom commented on GitHub (Sep 9, 2023):
Do you have a user.css or some modified theme?
@IZA09 commented on GitHub (Sep 9, 2023):
on a1111? no. its set to default, on the browser itself its all default.
@DominikDoom commented on GitHub (Sep 9, 2023):
Yeah, I just wanted to make sure there isn't some gradio theme or local style edit for the webui that hides the popup. user.css specifically would be a file in the webui root where you can add custom style rules.
For example, I limited the maximum width of the page in mine since I like to have the content centered on the monitor instead of up to the edges.
Since it seems to work there, it really must have to do either with a displaying issue or the tags themselves not loading for some reason.
Also in the browser developer tools, open the "Network" tab, enter "tag" in the Filter textbox at the top, and reload the page using CTRL+F5 with it open. It should show a list similar to this after the reload is finished:
Check if any of these fail, which would show them in red.
@IZA09 commented on GitHub (Sep 9, 2023):
all good here...
@DominikDoom commented on GitHub (Sep 9, 2023):
wtf, now I really have no clue what else could be wrong.
Just for good measure, can you try typing in img2img and the new style editor prompts:
To test if all text boxes are affected or only txt2img.
@IZA09 commented on GitHub (Sep 9, 2023):
yep its affected all throughout. this seems like a personal problem so ill just roll back to an older a1111. while id love to know whats going on here exactly, it looks to be a more obscure problem.
@DominikDoom commented on GitHub (Sep 9, 2023):
Well, as the developer I of course want to find out too, so no worries.
I'd still recommend you try out a clean webui install some time instead of rolling back for a long period. Something with the update does seem to have broken it for you after all. The only change needed for autocomplete to work with the new version was addressed in issue #213, but that fix was added pre-release on the webui side and should definitely be there for you too.
@DominikDoom commented on GitHub (Sep 9, 2023):
Something else I just noticed on your screenshots:
There are some oddities that seem style related, so maybe there actually is some issue with your webui installation.
The textbox and sort order from the extra networks tabs should usually be hidden / removed if the generation tab is selected.
And the icon buttons below the image should normally be centered. The thick line below them is also usually not there.
Tried it out in Opera to make sure.
You could try downloading https://raw.githubusercontent.com/AUTOMATIC1111/stable-diffusion-webui/master/style.css and replacing your local file in the webui root with it, in case the style file somehow got corrupted.
@IZA09 commented on GitHub (Sep 9, 2023):
im in the process of reinstalling the ui, if after that the problem persists, ill try out the css
i did notice the slight changes in the ui too, i just assumed it was part of the update.
@DominikDoom commented on GitHub (Sep 9, 2023):
A fresh reinstall will also have the correct css, so it shouldn't be needed in that case.
Wishing you luck that it works 👍
@IZA09 commented on GitHub (Sep 9, 2023):
sweet jesus it works now after reinstalling 1.6.0.. i decided to run it through conda instead of the usual web-user.bat and somewhere along the line everything fell into place. though ill technically never know if it was conda or the fresh restart, everything's fully functional now. i want to apologies for the time and trouble and thank you very much for the assistance in this.
@DominikDoom commented on GitHub (Sep 9, 2023):
No worries, glad you got it working and thanks for keeping me updated.