In the current Bricks Beta, a lot of adjustments have been made to the form logic. One significant change necessitates technical modifications for Pro Forms.
My aim has always been to stay as native as possible. That’s why Pro Forms have been leveraging the actions used natively by Bricks in forms up to this point. With the new Bricks update, this is no longer possible for the Nestable Pro Forms approach. Currently, I am in the process of replacing all native Bricks actions with custom ones.
However, this also comes with advantages! For example, many users missed the ability to assign a specific role or meta-data to the new user in the “Register User” action. Since we are now writing those actions ourselves, we are much more flexible in extending its functionality.
What does this mean for Nestable Pro Forms? In the current Bricks Beta, form submission will not work when using Nestable Pro Forms. The original Pro Forms variant should be used instead. However, since Nestable Pro Forms are experimental and have not been used on live pages, this should not be a problem.
I am making good progress in replacing the native actions, and the implementation is nearly complete.
The plan is to release a new version 2.0 as a Beta once the adjustments are finished. The Beta will already include a stable version of Nestable Pro Forms as well as the current changes. Since some code needs to be rewritten, a Beta release makes sense in this case.
In this post, I wanted to keep you updated on this matter
How should I proceed if I am building a website that will go live roughly in two months? I would like to use Nestable ProForms but wonder if it will be later compatible with the Nestable ProForms released in the stable version. I don’t mind if small adjustments will be required.
Hi all! I’m having the same issue as I need to get the values from the form to pass it along via API to my CRM. Is it working now? Any workaround to access the $form get fields?
Thank you. But I have no idea how to implement that method to assign roles. I am VERY new to Bricks and BricksBuilder and have put in endless hours over the past few weeks. I am finding very thin documentation and outdated tutorials. I thought it was supposed to be relatively straightforward but it is proving to be arduous.
Is there a proper tutorial on how to use the node editor for Pro Form?
I want to hide the pro form after the form submission is successful.
I tried to ask question in the group and also the forum, but no one was responding. I can’t find the relevant video. The doc isn’t very clear about it (maybe I don’t quite understand).
There isn’t (and realistically will never be) a tutorial for exactly your specific use case.
What does exist are tutorials that explain the concepts behind the Node Editor and how it works in general. The Node Editor is a tool that requires some time and hands-on exploration. The idea isn’t to find a video for every single scenario, but to understand the logic behind nodes, conditions, triggers, and outputs.
The best approach is to invest a few hours experimenting:
Rebuild simple examples
Break things and fix them again
Once you understand the underlying concepts, you’ll naturally see how to implement your own individual case.
This is exactly how the Node Editor is designed to be used: not by following step-by-step recipes for every situation, but by learning the system so you can apply it to any situation.
I’ll send you a few links to general Node Editor tutorials next. Those will help you get comfortable with the workflow and mindset needed to work efficiently with it:
Multi button submits would be cool too. Like 1 button updates a meta and reloads the page, and another updates a meta and redirects elsewhere. Like 2 submits, and each one has its own action panel.
I’m doing it based on a hidden field now, loading up the value based on the button pressed and configured the reload vs redirect with with a custom action.
Thanks!