[{"data":1,"prerenderedAt":127},["ShallowReactive",2],{"blog-\u002Fblog\u002F2023\u002F01\u002Fflowforge-1.2.1-released":3,"blog-all-for-related":126},{"id":4,"title":5,"authors":6,"body":8,"cta":107,"date":108,"description":109,"extension":110,"image":107,"lastUpdated":107,"meta":111,"navigation":116,"path":117,"seo":118,"sitemap":119,"stem":120,"subtitle":109,"tags":121,"tldr":107,"video":107,"__hash__":125},"blog\u002Fblog\u002F2023\u002F01\u002Fflowforge-1.2.1-released.md","FlowFuse 1.2.1 released",[7],"ben-hardill",{"type":9,"value":10,"toc":100},"minimark",[11,15,26,39,44,52,59,63,71,80,93],[12,13,14],"p",{},"We've published a maintenance release containing a fix for new users.",[12,16,17,18,25],{},"This release fixes an ",[19,20,24],"a",{"href":21,"rel":22},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1537",[23],"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.",[12,27,28,29,33,34,38],{},"The same fix also addresses an ",[19,30,24],{"href":31,"rel":32},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1514",[23]," where users could not sign up using an email with a ",[35,36,37],"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.",[40,41,43],"h3",{"id":42},"upgrading-flowfuse","Upgrading FlowFuse",[12,45,46,47,51],{},"This release has already been rolled out to [FlowFuse Cloud](",[48,49],"binding",{"value":50},"site.appURL",").",[12,53,54,55],{},"If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a\nguide for ",[19,56,58],{"href":57},"\u002Fdocs\u002Fupgrade\u002F","upgrading your FlowFuse instance",[40,60,62],{"id":61},"getting-help","Getting help",[12,64,65,66,70],{},"Please check FlowFuse's ",[19,67,69],{"href":68},"\u002Fdocs\u002F","documentation"," as the answers to many questions are covered there.",[12,72,73,74,79],{},"If you hit any problems with the platform, please raise an ",[19,75,78],{"href":76,"rel":77},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues",[23],"issue on GitHub",".\nThat also includes if you have any feedback or feature requests.",[12,81,82,83,86,87,92],{},"Chat with us on the ",[35,84,85],{},"#flowfuse"," channel on the ",[19,88,91],{"href":89,"rel":90},"https:\u002F\u002Fnodered.org\u002Fslack",[23],"Node-RED Slack workspace",".",[12,94,95,96],{},"You can also raise a support ticket by emailing ",[19,97,99],{"href":98},"mailto:support@flowfuse.com","support@flowfuse.com",{"title":101,"searchDepth":102,"depth":102,"links":103},"",4,[104,106],{"id":42,"depth":105,"text":43},3,{"id":61,"depth":105,"text":62},null,"2023-01-12","Release includes fix for emailing new user","md",{"excerpt":112},{"type":9,"value":113},[114],[12,115,14],{},true,"\u002Fblog\u002F2023\u002F01\u002Fflowforge-1.2.1-released",{"title":5,"description":109},{"loc":117},"blog\u002F2023\u002F01\u002Fflowforge-1.2.1-released",[122,123,124],"posts","flowfuse","releases","Oc7sBa6JqP9ekGt1Cw9c1fNlEflux-Qmjy8Zw0RFfsM",[],1785528684089]