I do not understand what happens in the Tabs & Links menu.
I have several times the same entries, a priori 2x?
This seems to be the result of several manipulations on my part:
an update of Nodered to 2.2.0 with the standard script.
An update from Raspbian 10 to 11 (bulleyes)
An update of all NR packages used.
An import of a flow from the Import menu
If I try to change something and want to do a deployment, I get these wonderful errors.
Do you have any idea what happens?
I have a backup but it annoys me to have to start all over again, the update is long. It will be if there is no simple solution to restore the situation.
Thanks for any advises
Edit:
I cleared the browser's cache
The CTRL+Right click doesn't work either into the editor
I used the new function: node-red admin init
Started the editor, started to create 2 tabs with one group each, result ok.
Then I used the palette to install several packages.
And bingo, the right part of the tabs split.
If I empty the browser cache, I restart it and it's back to normal.
I added a package, added a tabs + group, moved and closed the browser.
Then I restarted the editor and the defect appears again
You are not alone, I have the same issue in one of my flows. I thought it was me, by doing imports/exports a lot. If I go to another tab, like debug and back to dashboard tab, it is "repairing itself", it then looks normal, no duplicates no more (the complete flow works anyway fully perfect)
Thanks for the help Walter.
I did as you suggested, so it does indeed fix the Tabs part except that at the bottom it informs me that something is wrong with the widgets. I click on it, it's ok.
I do a deployment and there the big information message tells me that the 5 groups are not assigned, while I deleted groups 1-4 yesterday ! and that there I took another PC to be sure that it does not come from Linux, the I'm under Windows. Same.
These groups do not exist anymore in the Tabs part.
I can deploy though.
I don't know what else to do.
Hello Jean-Luc,
In my case it looks like below. It must be a bug somewhere, I think I have only seen this in the later 2.x versions but I'm not sure. Maybe it is me causing the bug
I've made some test now with a VM under ubuntu,
I don't have a free raspberry at the moment. So I'm not in the same condition, sorry.
There is also the description just above where I have problems with the deploy
In Node-RED 2.2, sidebar tab before refreshing become to be retained after browser refresh. This revealed the problem of the dashboard that originally existed.
I think that possible fix on Node-RED side is to change sidebar to the info tab after refresh as previous Node-RED.
I was able to update 3 of my "prod" raspberry with v3.1.6
and the problems disappeared.
It seems that everything is normal.
Congratulations for the reactivity and the help you gave me.