[{"data":1,"prerenderedAt":116},["ShallowReactive",2],{"blog-\u002Fblog\u002F2023\u002F01\u002Fflowforge-1.2.1-released":3},{"id":4,"title":5,"body":6,"description":12,"extension":105,"meta":106,"navigation":111,"path":112,"seo":113,"stem":114,"__hash__":115},"blog\u002Fblog\u002F2023\u002F01\u002Fflowforge-1.2.1-released.md","FlowFuse 1.2.1 released",{"type":7,"value":8,"toc":98},"minimark",[9,13,24,37,42,51,58,62,70,79,91],[10,11,12],"p",{},"We've published a maintenance release containing a fix for new users.",[10,14,15,16,23],{},"This release fixes an ",[17,18,22],"a",{"href":19,"rel":20},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1537",[21],"nofollow","issue"," introduced in FlowFuse 1.2 where users were not being sent their welcome email when they first sign up to the platform. As the sign-up page asks them to click on the link in that email, it left them waiting for an email that wasn't going to arrive.",[10,25,26,27,31,32,36],{},"The same fix also addresses an ",[17,28,22],{"href":29,"rel":30},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1514",[21]," where users could not sign up using an email with a ",[33,34,35],"code",{},"+"," in it. This is a restriction we apply to users signing up with Single Sign-On enabled email domains - but the check was being applied to everyone.",[38,39,41],"h3",{"id":40},"upgrading-flowfuse","Upgrading FlowFuse",[10,43,44,45,50],{},"This release has already been rolled out to ",[17,46,49],{"href":47,"rel":48},"https:\u002F\u002Fapp.flowfuse.com",[21],"FlowFuse Cloud",".",[10,52,53,54],{},"If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a\nguide for ",[17,55,57],{"href":56},"\u002Fdocs\u002Fupgrade\u002F","upgrading your FlowFuse instance",[38,59,61],{"id":60},"getting-help","Getting help",[10,63,64,65,69],{},"Please check FlowFuse's ",[17,66,68],{"href":67},"\u002Fdocs\u002F","documentation"," as the answers to many questions are covered there.",[10,71,72,73,78],{},"If you hit any problems with the platform, please raise an ",[17,74,77],{"href":75,"rel":76},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues",[21],"issue on GitHub",".\nThat also includes if you have any feedback or feature requests.",[10,80,81,82,85,86,50],{},"Chat with us on the ",[33,83,84],{},"#flowfuse"," channel on the ",[17,87,90],{"href":88,"rel":89},"https:\u002F\u002Fnodered.org\u002Fslack",[21],"Node-RED Slack workspace",[10,92,93,94],{},"You can also raise a support ticket by emailing ",[17,95,97],{"href":96},"mailto:support@flowfuse.com","support@flowfuse.com",{"title":99,"searchDepth":100,"depth":100,"links":101},"",2,[102,104],{"id":40,"depth":103,"text":41},3,{"id":60,"depth":103,"text":61},"md",{"navTitle":5,"excerpt":107},{"type":7,"value":108},[109],[10,110,12],{},true,"\u002Fblog\u002F2023\u002F01\u002Fflowforge-1.2.1-released",{"title":5,"description":12},"blog\u002F2023\u002F01\u002Fflowforge-1.2.1-released","S6XqBizUJGu6bUys0eQv69MLjiAypf2JSVSsONyr7rI",1780132425158]