We had similar thing in our upgrade. This is what we have done.
Since Forms has changed a lot in the latest version. Create a folder ElementsBlocks and then create Components folder wherever you are rendering your partials. My structure is as shown below.
Views --> Shared --> ElementsBlocks --> Components --> YourFormContainerName --> FormContainerBlock.cshtml.
This cshtml you can have your rendering code (essentially old forms html code). Also please ensure to FormContainerInitScript.cshtml from the modules/forms folder in the ElementsBlocks folder as it is required for form to render. Unfortunately I can put a snapshot but try this out and should work
Thanks DD! I think we're doing it in a way equivalent to what you suggest, and it (knock on wood) seems to work. I'm not really happy with that solution though, but maybe I just have to accept it and hope it will be better in future versions 😊.
We are upgrading from CMS 11 and CMS 12. One of the many problems that we have encountered is related to forms. We have a custom FormContainerBlock (that is heavily used on our sites). It was implemented a long time ago by developers who no longer are on the team and we who are have limited experience with this part of the product. I've tried to find documentation about how to work with custom form containers in CMS 12, but I'm either really bad at googling this or the available documentation is very sparse. Basically, the only useful page I've found so far is How to create custom FormContainerBlock in CMS 12 – Support Help Center (optimizely.com), which really doesn't contain much information.
Any input on this would be greatly appreciated