Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dashboard Views Lost After Update to @flowfuse/node-red-dashboard #1539

Closed
Koneisto opened this issue Dec 16, 2024 · 6 comments
Closed

Dashboard Views Lost After Update to @flowfuse/node-red-dashboard #1539

Koneisto opened this issue Dec 16, 2024 · 6 comments
Labels
bug Something isn't working needs-triage Needs looking at to decide what to do

Comments

@Koneisto
Copy link

Koneisto commented Dec 16, 2024

Current Behavior

After updating to the latest version of @flowfuse/node-red-dashboard, all dashboards (pages) were marked as orphaned, and the views were completely lost. This is not the first time such an issue has occurred after an update. It severely disrupts workflows and raises concerns about the stability of this module.

Steps To Reproduce

1.	Update to the latest version of @flowfuse/node-red-dashboard and node-red 4.0.6
2.	Open the Node-RED editor after the update.
3.	Observe that all dashboard views (pages) are marked as orphaned.
4.      No pages, no dashboard.

Environment

  • Dashboard version: 1.20.0
  • Node-RED version: 4.0.6
  • Platform/OS: Latest official docker image minimal
@Koneisto Koneisto added bug Something isn't working needs-triage Needs looking at to decide what to do labels Dec 16, 2024
@bartbutenaers
Copy link
Contributor

@Koneisto

I did not have time to reproduce your problem, but could you please explain what you mean with orphaned? If you have screenshot perhaps from that time that would help. Thanks!

Although I am not familiar with that part of the dashboard, so perhaps I won't be able to assist you with this one. But perhaps it does ring a bell to anybody else, to pinpoint which PR caused this...

raises concerns about the stability of this module.

It is very easy to predict what will happen in fact: there are now 322 open issues in this repo. As long (near) nobody from our community starts solving them, those Github issues will keep causing issues in your dashboard...

@Koneisto
Copy link
Author

Hi! Thank you for reply.

After updating Node-RED and Dashboard2, the following issue occurred:
1. A warning appeared: “You have some unused configuration nodes.”
2. These nodes were related to ui-page nodes.
3. The dashboard was empty, and none of the dashboard nodes were linked to any page.
4. I resolved the issue by deleting the unused ui-page nodes and adding them back. However:
• Each dashboard node had to be manually re-added to the newly created pages.
5. This problem has occurred multiple times while editing flows.

Even now, the ui-page nodes are orphaned/unused after deleting a single dashboard text node. This makes the dashboard configuration unreliable.

Versions:
• Node-RED: 4.0.7 (minimal Docker)
• Dashboard: @flowfuse/node-red-dashboard 1.20.0

Screenshot 2024-12-19 at 10 42 19
Screenshot 2024-12-19 at 10 33 25
Screenshot 2024-12-19 at 10 10 40

@bartbutenaers
Copy link
Contributor

@Koneisto ,
Thanks for the detailed instructions!!!

A warning appeared: “You have some unused configuration nodes.”

Could your problem perhaps be related to this issue, which has been registered in the Github repo of Node-RED itself? Hopefully it is, because Nick is going to look at that one tomorrow...

@GogoVega
Copy link
Contributor

Should be fixed in 4.0.8

@Koneisto
Copy link
Author

Update:
Updating to Node-RED version 4.0.8 seems to have resolved the issue. After the update, all pagenodes were correctly restored, and the dashboards is now functioning as expected.

Screenshot 2024-12-20 at 15 01 28

Thank you, @bartbutenaers, for your comment and pointing out the related issue! It seems the problem has been addressed in the latest version. Much appreciated!

@bartbutenaers
Copy link
Contributor

@Koneisto,
You are welcome! Thanks for informing us that the problem is solved now.
Could you please close this issue?
Seems I am not authorized on this repo to do that myself...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Needs looking at to decide what to do
Projects
Status: Done
Development

No branches or pull requests

3 participants