Uibuilder & Node RED 2.0.2

General
1

Hi out there,
while uibuilder 3.1.3 is running under Node RED 1.2.6 (node.js 12.20.0) like a charm the output usinge recent Versions (uibuilder 4.1.1, Node RED 2.0.5, node.js 12.20.0) is quite "corrupt".
Flow:

[{"id":"88c9944b.653ce8","type":"uibuilder","z":"348a7f3d.de0d5","name":"","topic":"","url":"uibuilder","fwdInMessages":false,"allowScripts":false,"allowStyles":false,"copyIndex":true,"templateFolder":"blank","showfolder":false,"useSecurity":false,"sessionLength":432000,"tokenAutoExtend":false,"x":580,"y":820,"wires":[["1455e200.92058e"],["17a514c2.6821ab"]]},{"id":"634f2dd1.da6784","type":"inject","z":"348a7f3d.de0d5","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":380,"y":820,"wires":[["88c9944b.653ce8"]]},{"id":"1455e200.92058e","type":"debug","z":"348a7f3d.de0d5","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":770,"y":800,"wires":[]},{"id":"17a514c2.6821ab","type":"debug","z":"348a7f3d.de0d5","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":770,"y":840,"wires":[]}]

The - not expected - result is

Unbenannt
Unbenannt1069Ă—255 15.5 KB

Any idea?
Thank you so much

2

I seem to recall reading in many topics now that Node-Red 2.0.x should be using node.js 14+ Perhaps that is contributing to your issue?

3

Well it looks like you've ended up with the new "blank template" which is, as the name says ... blank :grinning:

v4 made some very significant changes to template handling so that we could move uibuilder forward more rapidly.

To have the same template as previous versions, change the template:

image

Just note the warnings that tell you all of your code is going to be overwritten so make a backup if you've changed anything. BTW, you still get another chance to back out even if you press the load button.

V4+ now defaults to the blank template.

As a side note, if you ever think that uibuilder's front-end is doing something weird, add uibuilder.debug(true) immediately after your uibuilder.start and reload the page, Now, open the browser dev tools and have a look at the console. You will be getting lots of output showing you exactly what is going on.

No, v12 is still OK while it is still an LTS version. I had to move uibuilder to v12 as a minimum in v4 because of upstream dependencies. In the world of node.js and JavaScript, I'm afraid things move super fast. Actually, I can't wait until v14 becomes the accepted minimum as that puts in place some nice enhancements for classes.

1 Like
4

I guess it was recalling the references of "12 soon to be 14+" that I was recalling. I run 14

That and I shouldn't have bothered posting as I don't run uibuilder anyhow :stuck_out_tongue:

5

Hi Julian,
thank yu so much for the quick response. Everything is working fine now. :+1:
Have a nice time.

6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.