mirror of
https://github.com/Comfy-Org/ComfyUI-Manager.git
synced 2026-11-05 07:47:25 +00:00
[GH-ISSUE #992] [bug] Manager causes the new ComfyUI front end search to break #434
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/ComfyUI-Manager#434
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 @gonzalu on GitHub (Aug 22, 2024).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/992
Hello,
I have this problem with the new front end that double-click to search for nodes is not working when the ComfyUI manager is installed.
When I disable ALL custom nodes, the feature works fine.
When I disable ALL custom nodes EXCEPT the manager, the problem is there
Thank you.
@ltdrdata commented on GitHub (Aug 23, 2024):
Show me the browser console log. (press F12 if chrome)
@gonzalu commented on GitHub (Aug 23, 2024):
Further troubleshooting shows that ANY custom node causes it. Only way I get it to work is if ALL custom nodes are not enabled :(
@gonzalu commented on GitHub (Aug 23, 2024):
Now it started working all of a sudden!!
WHAT?? This is so weird :( I have updated nothing...
@ltdrdata commented on GitHub (Aug 24, 2024):
You have to remove
NestedNodeBuilder.It should be removed long time ago since GroupNode feature is added.
@gonzalu commented on GitHub (Aug 24, 2024):
Thank you... maybe when I cleaned up some nodes it got dumped. I did re-install the manager, but it did not fix itself immediately. I am just glad it is working :D
Thank you!
@gonzalu commented on GitHub (Aug 25, 2024):
Looks like NestedNodeBuilder was dirty and did not get picked up by the manager and I missed it MANUALLY... so after going in by hand, I deleted it for good.
Thanks as always!!
@ltdrdata commented on GitHub (Aug 25, 2024):
That node is moved to legacy channel. So you cannot see in the default channel list.