# 🎉 Node-RED 1.2.0-beta.1 released

**URL:** <https://discourse.nodered.org/t/node-red-1-2-0-beta-1-released/33557>\
**Category:** News\
**Created:** [30 September 2020 09:57 UTC](https://discourse.nodered.org/t/node-red-1-2-0-beta-1-released/33557 "2020-09-30T09:57:55Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [8 October 2020 06:46 UTC](https://discourse.nodered.org/t/node-red-1-2-0-beta-1-released/33557/28 "2020-10-08T06:46:05Z")

</div>

I could not see any errors related to the specific recovered nodes in the browser console (I have some errors related to another node configuration but I don't think it is related, they are all related to a nexmobasic api key)

In the first view you can see parts of recovered nodes in the upper left corner. Zooming in or out does not make them more visible. Selecting all (Command A in mac) and then drag them into the workspace makes them visible but they are still piled on top of each other. Moving them apart one-by-one makes them visible. In my case 3 in total of type node-red-contrib-string

Only place I use this node, also 3 in total, is in a disabled flow tab

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/9/69e8752e2cd7c15b0abca296976665ff10227042.png)  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/1/e1dde0a9c0aa5728c7004e55de5c9bae4e39cd1e.png)  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/0/f0b5b7fc3f45d1bd900bbbebe97f88af41578f5f.png)

My errors in the console

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/0/507be4c333554a37906635464aab4aba0e867db3.png)

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [8 October 2020 09:40 UTC](https://discourse.nodered.org/t/node-red-1-2-0-beta-1-released/33557/29 "2020-10-08T09:40:40Z")

</div>

Looked at the browser console and saw this:

 ![Screen Shot 2020-10-08 at 5.30.06 AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/d/cdc45690806e90cd65a40eac0d317027175752ef.png)  
so I removed node-red-contrib-python3-function and restarted NR but it still hung up. Checked the console again and found this:  
 ![Screen Shot 2020-10-08 at 5.31.42 AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/3/13ec7bc2c5f332c069a1ecaa66d758a3fc3fb5c9.png)  
so I removed node-red-contrib-xterm and NR started up.

I'll open an issue inGitHug with the author (@BartButenaers)

[EDIT] @knolleary Well this is odd, I've re-added the node and now NR starts with no issues...sigh...

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [7 December 2020 09:40 UTC](https://discourse.nodered.org/t/node-red-1-2-0-beta-1-released/33557/30 "2020-12-07T09:40:41Z")

</div>

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

[Previous page](https://discourse.nodered.org/t/node-red-1-2-0-beta-1-released/33557.md?page=1)