[{"data":1,"prerenderedAt":191},["ShallowReactive",2],{"blog-\u002Fblog\u002F2022\u002F12\u002Fflowforge-1-1-2-released":3},{"id":4,"title":5,"body":6,"description":12,"extension":180,"meta":181,"navigation":186,"path":187,"seo":188,"stem":189,"__hash__":190},"blog\u002Fblog\u002F2022\u002F12\u002Fflowforge-1-1-2-released.md","FlowFuse 1.1.2 released",{"type":7,"value":8,"toc":170},"minimark",[9,13,24,32,41,44,49,52,83,87,90,101,109,114,122,129,133,141,150,163],[10,11,12],"p",{},"We've published a maintenance fix with an important fix for the Palette Manager in Node-RED.",[10,14,15,16,23],{},"A ",[17,18,22],"a",{"href":19,"rel":20},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1367",[21],"nofollow","bug"," was reported this week\nwhere a user was unable to install additional nodes into their Node-RED project\nusing the editor's palette manager.",[10,25,26,27,31],{},"We tracked it down to an issue that was introduced in the 1.1 release, where the\nproject template lets you list nodes that should be blocked from being installed.\nIt was interpreting an empty list to mean ",[28,29,30],"em",{},"disallow everything","! Not quite the\nintended behaviour.",[10,33,34,35,40],{},"Whilst tracking this down, we also spotted a bug (",[17,36,39],{"href":37,"rel":38},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F1379",[21],"#1379",")\naround editing this same setting that made it tricky to work around without this\nrelease being published.",[10,42,43],{},"These issues have now been fixed and FlowFuse 1.1.2 published.",[45,46,48],"h2",{"id":47},"bug-fixes","Bug Fixes",[10,50,51],{},"In additional to the above issues, this release includes some further fixes around\nthe docker and helm components:",[53,54,55,64],"ul",{},[56,57,58,59],"li",{},"Fix fileStore hostname by @flecoufle in ",[17,60,63],{"href":61,"rel":62},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdocker-compose\u002Fpull\u002F59",[21],"#59",[56,65,66,67,72,73,72,78],{},"Fix healthcheck ",[17,68,71],{"href":69,"rel":70},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdocker-compose\u002Fpull\u002F62",[21],"#62"," ",[17,74,77],{"href":75,"rel":76},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdocker-compose\u002Fpull\u002F63",[21],"#63",[17,79,82],{"href":80,"rel":81},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fhelm\u002Fpull\u002F74",[21],"#74",[45,84,86],{"id":85},"contributors","Contributors",[10,88,89],{},"We'd like to thank the following people for their contributions to this release:",[10,91,92,97,98],{},[17,93,96],{"href":94,"rel":95},"https:\u002F\u002Fgithub.com\u002Fflecoufle",[21],"flecoufle"," for their work on ",[17,99,63],{"href":61,"rel":100},[21],[10,102,103,104,108],{},"As an open-source project, we welcome community involvement in what we're building.\nIf you're interested in contributing, checkout our ",[17,105,107],{"href":106},"\u002Fdocs\u002Fcontribute\u002F","guide in the docs",".",[110,111,113],"h3",{"id":112},"upgrading-flowfuse","Upgrading FlowFuse",[10,115,116,117,108],{},"This release has already been rolled out to ",[17,118,121],{"href":119,"rel":120},"https:\u002F\u002Fapp.flowfuse.com",[21],"FlowFuse Cloud",[10,123,124,125],{},"If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a\nguide for ",[17,126,128],{"href":127},"\u002Fdocs\u002Fupgrade\u002F","upgrading your FlowFuse instance",[110,130,132],{"id":131},"getting-help","Getting help",[10,134,135,136,140],{},"Please check FlowFuse's ",[17,137,139],{"href":138},"\u002Fdocs\u002F","documentation"," as the answers to many questions are covered there.",[10,142,143,144,149],{},"If you hit any problems with the platform, please raise an ",[17,145,148],{"href":146,"rel":147},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues",[21],"issue on GitHub",".\nThat also includes if you have any feedback or feature requests.",[10,151,152,153,157,158,108],{},"Chat with us on the ",[154,155,156],"code",{},"#flowfuse"," channel on the ",[17,159,162],{"href":160,"rel":161},"https:\u002F\u002Fnodered.org\u002Fslack",[21],"Node-RED Slack workspace",[10,164,165,166],{},"You can also raise a support ticket by emailing ",[17,167,169],{"href":168},"mailto:support@flowfuse.com","support@flowfuse.com",{"title":171,"searchDepth":172,"depth":172,"links":173},"",2,[174,175],{"id":47,"depth":172,"text":48},{"id":85,"depth":172,"text":86,"children":176},[177,179],{"id":112,"depth":178,"text":113},3,{"id":131,"depth":178,"text":132},"md",{"navTitle":5,"excerpt":182},{"type":7,"value":183},[184],[10,185,12],{},true,"\u002Fblog\u002F2022\u002F12\u002Fflowforge-1-1-2-released",{"title":5,"description":12},"blog\u002F2022\u002F12\u002Fflowforge-1-1-2-released","sUAvShsEShpOY22673RzdayvxEZS6w08F9TQBj3T1lg",1780132425051]