Skip to content
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

No longer autocompleting since v1.2.2 #9

Closed
Evil-Dragon opened this issue Oct 14, 2022 · 4 comments
Closed

No longer autocompleting since v1.2.2 #9

Evil-Dragon opened this issue Oct 14, 2022 · 4 comments

Comments

@Evil-Dragon
Copy link

I can only get autocomplete to work up to v1.2.2 but any version after that never brings anything up. Running the latest version of A111 via git pull on launch.

Not sure if related:
acConfig.activeIn is undefined TypeError: acConfig.activeIn is undefined <anonymous> http://127.0.0.1:7860/:1824 <anonymous> http://127.0.0.1:7860/:1814 runCallback http://127.0.0.1:7860/:82 executeCallbacks http://127.0.0.1:7860/:88 mutationObserver http://127.0.0.1:7860/:93 MutationCallback* http://127.0.0.1:7860/:92 EventListener.handleEvent* http://127.0.0.1:7860/:91

@DominikDoom
Copy link
Owner

Are you using the current version of the config?
Newer versions added some new settings, and the error reads like it just can't find that setting key.
Would also match the version since 1.3.0 introduced those activeIn keys to support autocompletion in img2img and negative textboxes.

@Evil-Dragon
Copy link
Author

Evil-Dragon commented Oct 15, 2022

If you mean the config file in your script then yes, i've overwritten it from the 1.4.2 release.

Still doesn't work however.

@DominikDoom
Copy link
Owner

Hm weird, then the error above shouldn't happen.

Another suggestion: It might be that your browser cached the old config. In the Developer Tools, try checking "Disable cache" under the Network tab and reload the page with the Tools still open. That should ensure it reloads the config.

@Evil-Dragon
Copy link
Author

Evil-Dragon commented Oct 15, 2022

Definately a cache issue, disabling cache sorted it out and then I reloaded and it worked. Never even thought about caching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants