Thanks for reporting @utaani
The i18n library we use is one of the ones that has had a major upgrade in this release. I'll investigate why this particular feature has broken.
1 Like
Ok I've managed to run an Image with code pulled from the dev branch and happy to report that the issue with @ in Basic Auth Username is fixed.
Thank you @hardillb !
Is the dnp3 node ready to use in this beta version?
Hi @Steven
which node are you referring to? I can't find anything mentioning dnp3 in the flow library and it isn't something in the core.
I've just tried posting the code for a flow between back ticks on the forum.
It just posts the whole of the json rather than the neat compacted line.
I'm using the Monaco editor.
I tried posting a flow from a previous node-RED v1.3.5 and that works fine.
In the export dialog, switch to the JSON tab and make sure the 'compact' option is selected.
1 Like
Thanks Nick - that sorted it.
Hello Developers .. excellent job with the new features
I notice a small issue with the new beta version relating to the Context panel and the icons to copy, refresh, delete.
Basically the first time we refresh in order to show the data in Context, when we hover over the root of the data it shows all the icons. If we expand the object and then hover over the root again the icons dont show anymore (except the copy value). Nothing critical but anyway
Also would it be possible to have in Context the same font type and size as with the Debug panel ?
now it looks a bit .. whats the british word .. chunky
...ahh, you mean more readable 
yea 
.. especially if we have a bigger object (than the screenshot above) ..
i find the Debug panel font family and size more convenient to read when expanded
Hi Nick, you can please check the link below.
HI @Steven
Check it for what exactly?
I thought you ask me which node I refer to? 
That's why I share the DNP node link here. I reply according to your message 15 days ago, sorry that I am late
Oh sorry, I missed it was in reply to a previous post.
As for that node, you'd have to ask it's author. It isn't a core node so we don't have anything to do with it.
Alright, noted with thanks 
But it is probably worth noting that node hasn't been updated in the last 3 years and the github repo it points to has been deleted.
Also given the large warning at the top of the readme about not being fit for production I would not choose to use it for anything serious.
Been using the beta software on two systems now with no issues but........
I gave little thought as to what moving forward would look like. Is it as simple as re- running the "real" 2.0 install script when it comes of age?
yes - the @next tag will become @latest which will be the default. (same as not adding @anything). But beta-2 will come before then.... (which will be tagged @next when released to replace beta-1)
2 Likes
Hi Nick,
Is there any changes with MQTT nodes?
We are working with it, on 1.3.5v we facing suddenly crashes.
Thank you.
Nothing significant has changed with the mqtt nodes. But if you are hitting issues with 1.3.5 then that isn't relate to the beta and I suggest you post separately about them so we can see what's going on.
