[GH-ISSUE #285] After updating Manager, Unable to upgrade Allor #150

Open
opened 2026-10-27 21:13:54 +00:00 by bsakaguchi · 3 comments
Owner

Originally created by @assassindesign on GitHub (Jan 4, 2024).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/285

293908938-59b390c7-9767-4abc-bb8b-f42a4521345b
After updating Manager, Unable to upgrade Allor

Originally created by @assassindesign on GitHub (Jan 4, 2024). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/285 ![293908938-59b390c7-9767-4abc-bb8b-f42a4521345b](https://github.com/ltdrdata/ComfyUI-Manager/assets/3187551/5cadc2c6-dca0-4338-89d2-2ee92ae45441) After updating Manager, Unable to upgrade Allor
Author
Owner

@ltdrdata commented on GitHub (Jan 4, 2024):

If I base the explanation on ComfyUI-Manager version 1.21, if the "skip update check" option is unchecked, there won't be any updates to perform.
If the "skip update check" is checked, there will be a "try update" button available.

And the "import failed" status visible in the screenshot is not an unupdateable state but a state where Allor is not functioning due to an error. This needs to be addressed with the respective custom node repository.

<!-- gh-comment-id:1876396265 --> @ltdrdata commented on GitHub (Jan 4, 2024): If I base the explanation on ComfyUI-Manager version 1.21, if the "skip update check" option is unchecked, there won't be any updates to perform. If the "skip update check" is checked, there will be a "try update" button available. And the "import failed" status visible in the screenshot is not an unupdateable state but a state where Allor is not functioning due to an error. This needs to be addressed with the respective custom node repository.
Author
Owner

@assassindesign commented on GitHub (Jan 4, 2024):

Thank you. It seems that there is a conflict with the plug-in after comfyui is updated.

<!-- gh-comment-id:1876534306 --> @assassindesign commented on GitHub (Jan 4, 2024): Thank you. It seems that there is a conflict with the plug-in after comfyui is updated.
Author
Owner

@ltdrdata commented on GitHub (Jan 4, 2024):

Thank you. It seems that there is a conflict with the plug-in after comfyui is updated.

The term "conflict" is just a general information message. Be cautious when installed with certain other custom nodes, as it is uncertain which node of a custom node will be loaded. This is unrelated to "import fail" at all.

It explicitly exposes an issue that was previously hidden.

<!-- gh-comment-id:1876544290 --> @ltdrdata commented on GitHub (Jan 4, 2024): > Thank you. It seems that there is a conflict with the plug-in after comfyui is updated. The term "conflict" is just a general information message. Be cautious when installed with certain other custom nodes, as it is uncertain which node of a custom node will be loaded. This is unrelated to "import fail" at all. It explicitly exposes an issue that was previously hidden.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Comfy-Org/ComfyUI-Manager#150
No description provided.