search

comfyanonymous / ComfyUI

The most powerful and modular diffusion model GUI, api and backend with a graph/nodes interface.
https://www.comfy.org/
GNU General Public License v3.0
56.21k stars 5.96k forks source link

Convert To Group Node only available in current session #2660

Open LuisBurdallo opened 9 months ago

LuisBurdallo commented 9 months ago

It seems that when I (Convert To Group Node) works fine up until you reload the workflow after restarting the server where it says the group node is missing so it only exists in the current session. Is this a bug? because it doesn't make sense at all. Also, those groups can be saved as template but they won't save at all. Nothing happens if you save a group node as a template and try to reload it.

ltdrdata commented 9 months ago

Group nodes are belong to the workflow. And when deploying the workflow, the corresponding group nodes are included. If there is already a group node with the same name locally, it will result in a collision issue.

To address this in ComfyUI-Manager, I added a feature called "save as component." After assigning a unique name to the component from the context menu of the group node, it can be saved locally as a component, and then used with that name.

LuisBurdallo commented 9 months ago

I just saved a new group node as a component and it is now accessible at any time from the group nodes menu. Thank you so much!

LuisBurdallo commented 9 months ago

Group nodes are belong to the workflow. And when deploying the workflow, the corresponding group nodes are included. If there is already a group node with the same name locally, it will result in a collision issue.

To address this in ComfyUI-Manager, I added a feature called "save as component." After assigning a unique name to the component from the context menu of the group node, it can be saved locally as a component, and then used with that name.

Is it possible to manage those components in order to change the name or any of the details entered when creating them?

LuisBurdallo commented 9 months ago

Group nodes are belong to the workflow. And when deploying the workflow, the corresponding group nodes are included. If there is already a group node with the same name locally, it will result in a collision issue.

To address this in ComfyUI-Manager, I added a feature called "save as component." After assigning a unique name to the component from the context menu of the group node, it can be saved locally as a component, and then used with that name.

Hey man I am still wondering if those components can be managed in any way. I wish I could hide and show stuff in those nodes to simplify them. It seems it's always saving as .pack

ltdrdata commented 9 months ago

Group nodes are belong to the workflow. And when deploying the workflow, the corresponding group nodes are included. If there is already a group node with the same name locally, it will result in a collision issue. To address this in ComfyUI-Manager, I added a feature called "save as component." After assigning a unique name to the component from the context menu of the group node, it can be saved locally as a component, and then used with that name.

Hey man I am still wondering if those components can be managed in any way. I wish I could hide and show stuff in those nodes to simplify them. It seems it's always saving as .pack

The current Component only offers basic storage and sharing functionalities. Separate implementation is planned for management features.

LuisBurdallo commented 9 months ago

Group nodes are belong to the workflow. And when deploying the workflow, the corresponding group nodes are included. If there is already a group node with the same name locally, it will result in a collision issue. To address this in ComfyUI-Manager, I added a feature called "save as component." After assigning a unique name to the component from the context menu of the group node, it can be saved locally as a component, and then used with that name.

Hey man I am still wondering if those components can be managed in any way. I wish I could hide and show stuff in those nodes to simplify them. It seems it's always saving as .pack

The current Component only offers basic storage and sharing functionalities. Separate implementation is planned for management features.

That's great to hear. Thanks!

shivshankar11 commented 9 months ago

i am saving group nodes and group nade created via components and saving using them as templates but they are missing nodes when using in different workflows.

ameets21 commented 1 month ago

After updating Comfy Ui all group node stop working plus i can't now ungroup or convert back to node there is convert to node option but it wont work

Talae06 commented 1 month ago

Same problem here. Have to delete them and re-add them through "Add Node" then "group nodes > workflow" and reconnect the links.

Edit : OK, and saving the workflow again afterwards make the group nodes disappear entirely, can't "manage" them or add them anymore.