[Bug]: New extension manager makes extensions not load properly on startup

[36DB]

Is there an existing issue for this?

• [X] I have searched the existing issues and checked the recent builds/commits

What happened?

If you initially launch webui after installing extensions using the recently added extension tab, the extensions you've installed are not loaded in properly at startup. It doesn't work as it should.

Reloading the UI using either the Apply and restart UI button at the Extensions tab, or Restart Gradio button at the Settings tab seems to fix the issue. After these two actions, extensions are properly loaded in, they work well as they should.

Steps to reproduce the problem

1. Start WebUI after installing extensions from the Extensions tab.
2. After initial startup, installed extensions do not work or load in properly.

What should have happened?

The extensions should have loaded in properly and work without errors.

Commit where the problem happens

5c9b3625fa03f18649e1843b5e9f2df2d4de94f9

What platforms do you use to access UI ?

Windows

What browsers do you use to access the UI ?

Google Chrome

Command Line Arguments

No response

Additional information, context and logs

No response

[Rogal80]

also Inspiration extension work not properly :(

[advtech92]

I am having the error where it prevents it from loading due to the fact that I have the command arguments --listen. Why should this prevent us from doing with extensions? I understand it may be to prevent tampering by other users, but I am doing this on a networked machine and I'd rather not have to walk to it every time I want to use the UI

[kabachuha]

Also seems to cause https://github.com/deforum-art/deforum-for-automatic1111-webui/issues/53 in Deforum

[Dennis74]

Workaround:

Remove --listen and --share

On a CMD prompt on that Windows machine type: netsh interface portproxy add v4tov4 listenport=7860 connectport=7861 connectaddress=127.0.0.1

Start the WebUI, it will listen on 127.0.0.1:7861 and YourmachinesIP:7860

I am having the error where it prevents it from loading due to the fact that I have the command arguments --listen. Why should this prevent us from doing with extensions? I understand it may be to prevent tampering by other users, but I am doing this on a networked machine and I'd rather not have to walk to it every time I want to use the UI

[advtech92]

Workaround:

Remove --listen and --share

On a CMD prompt on that Windows machine type: netsh interface portproxy add v4tov4 listenport=7860 connectport=7861 connectaddress=127.0.0.1

Start the WebUI, it will listen on 127.0.0.1:7861 and YourmachinesIP:7860

I am having the error where it prevents it from loading due to the fact that I have the command arguments --listen. Why should this prevent us from doing with extensions? I understand it may be to prevent tampering by other users, but I am doing this on a networked machine and I'd rather not have to walk to it every time I want to use the UI

I'll keep this in mind, I've found a fix in the meantime to reload the UI which fixes it.

[MrNeon]

Unfortunately reloading the UI will cause other issues like the attention short cut increasing the value by 0.2 instead of 0.1. Probably running twice.