mirror of
https://github.com/Comfy-Org/ComfyUI-Manager.git
synced 2026-11-05 07:47:25 +00:00
[GH-ISSUE #1392] failed to load components #572
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#572
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 @Neytiri7 on GitHub (Jan 3, 2025).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1392
That's how it appears when you start the browser without any messages.
@ltdrdata commented on GitHub (Jan 3, 2025):
This is fixed, already.
Update to latest version.
@Neytiri7 commented on GitHub (Jan 3, 2025):
Even in the latest version, it's the same even if you erase and reinstall it, and update it.
@ltdrdata commented on GitHub (Jan 3, 2025):
What is your Manager version number?
@Neytiri7 commented on GitHub (Jan 3, 2025):
@ltdrdata commented on GitHub (Jan 3, 2025):
For the nightly version, it may not display the version information correctly there.
Check the version on the about page.
@Neytiri7 commented on GitHub (Jan 3, 2025):
When installed as git, it is automatically installed as nightly version.
I updated it afterwards, and it was done without errors, and I get an error when I restart it.
So, I reinstalled the ComplyUI, and I also installed the manager with version 3.3.6.
I updated it afterwards, and an error occurs as below.
And, it was updated to 3.3.7 normally upon restart.
There are no components errors.
Even when I update it later, I'm worried that there's an error like that.
And, I think it should always be installed with the latest version, not the nightly version at the first installation.
@ltdrdata commented on GitHub (Jan 4, 2025):
This is patched. Update to 3.3.9 and try again.
@Neytiri7 commented on GitHub (Jan 4, 2025):
The same error occurs in 3.3.9.
Of course, there is nothing wrong with driving the ComplyUI.
I get this error only for updates.
There seem to be nodes that cannot be updated.
@ltdrdata commented on GitHub (Jan 4, 2025):
It seems that your ComfyUI installation/status is invalid.
Goto
W:\SynologyDrive\Comfy\ComfyUIin cmd.And execute
What is displayed?
@Neytiri7 commented on GitHub (Jan 6, 2025):
@ltdrdata commented on GitHub (Jan 6, 2025):
This is patched. Update and try again.
@Neytiri7 commented on GitHub (Jan 6, 2025):
No errors are displayed when updating
However, if you click Update, some custom node functions will not work.
https://github.com/pythongosssss/ComfyUI-Custom-Scripts/issues/413
https://github.com/cubiq/ComfyUI_IPAdapter_plus/issues/776
After the update, the CompyUI is reinstalled, and it only works fine if it is not updated, and when it is updated, some features do not work the same.
Upon update
The cache log is being displayed.
Access denied, update fails.
@Neytiri7 commented on GitHub (Jan 6, 2025):
@ltdrdata commented on GitHub (Jan 6, 2025):
Can you check the files of the following directory?
"W:\SynologyDrive\Comfy\ComfyUI\custom_nodes\cg-image-picker"
Is the directory exists?
Are the files exist in the directory?
@ltdrdata commented on GitHub (Jan 6, 2025):
Can you check the files of the following directory?
"W:\SynologyDrive\Comfy\ComfyUI\custom_nodes\cg-image-picker"
Is the directory there?
Are there files in the directory?
@Neytiri7 commented on GitHub (Jan 7, 2025):
As explained earlier, there is an error like that, but if you click the update again, it will not be updated or updated.
The custom node is also installed normally.
It also works normally.
https://github.com/pythongosssss/ComfyUI-Custom-Scripts/issues/413
https://github.com/cubiq/ComfyUI_IPAdapter_plus/issues/776
Once these two issues occur, they are not resolved.
@drmbt commented on GitHub (Mar 18, 2025):
what is currently the state of components? I still have issues with them not loading internal widget values in new projects; would be such a power tool if they were reliable. Also doesn't seem to be a lot of documentation surrounding their current capabilities / best practices
@ltdrdata commented on GitHub (Mar 19, 2025):
The front-end implementation is currently being migrated. The component functionality will also be reimplemented on the front end.
The current components will behave like group nodes when added to a workflow, so they should not cause compatibility issues with existing workflows.