I just waisted over 10 hours integrating our custom Action with Pro Forms… just to find out it won’t work due to multiple bugs (could work around two of them)
BricksForge Pro Forms “Custom Action”-docs are referring to the Bricks docs… but are not passing the same data, therefore we will have almost no documentation. I already mentioned this here, but got no response at all: ProForms custom action not working acoording to Bricks docs
→ Workaround be debugging the passed Data, which is nasty and unreliable long term.
Condition based on global JS Variable isn’t working. I add var MyVar = "Test"; right before my Form and set condition based to global variable MyVar equals Test for my field → won’t work at all.
→ Workaround done by utilizing browser storage.
Conditional Fields value won’t be passed to the backend at all… My email template with {{all_fields}} doesn’t show the field (visible in the frontend) at all. Also didn’t get passed to my custom action.
After a delay due to the hurdles I had to take, I’m now totally blocked on our client’s project. I would be glad if there’s a quick fix for Issue #3, since this one is the worst.
I also experienced issue number 3 (Conditional fields). I don’t get it. Everyone swears by this product. I purchased it based on raving reviews. Purchased solely for the Forms feature. And I had issues the moment I started working with it. Then I started making animations, and that’s another set of issues.
I am under the impression that the earlier version worked better and that all developers’ focus went into the silly Node editor GUI.
The lack of developers addressing the issue or communicating on their own forum is certainly disheartening. I do sense that the product is overwhelming and has nice potential, though. But man, I keep losing hours of my time blaming myself, I am doing something wrong, only to come here and find people having the same issues.
A one: yes, it’s a bug and we are working on a fix - would do better than silence.
What’s even more interesting is that the developer obviously read the complaint, and now he is considering closing this forum for good.
He made a voting pool on Facebook whether the forum should be closed or not. Very worrying intention. Now, the people who are in the FB group, most of whom do not even know this forum exists, will decide the fate of a forum and its users here.
I am finding this completely sad.
I understand the challenges of maintaining multiple communication channels, but I believe that eliminating this forum would be a poor business decision for several key reasons:
The forum provides a structured knowledge archive that is easily searchable, which Facebook does not allow
Many users don’t have or don’t want a Facebook account. It’s even blocked in some countries.
The forum provides better capabilities for detailed bug reports, with the ability to attach larger files
Professional industry standards include forums as the primary support channel
The forum is the professional face of your product and a place where a lasting knowledge base is built. Facebook is useful for more informal communication, but it cannot replace a forum.
Perhaps a better solution would be to reduce your personal time invested in the forum, while keeping it as an official channel for support and bugs. You could appoint community moderators or check the content occasionally instead of responding daily (or never).
Hey everyone! Just wanted to chime in here as well. As I’ve mentioned several times before, the forum is currently intended more as a user-to-user space. It was never designed to be an official support channel.
If you need private support, the official way to request it is by submitting a ticket here:
That also applies to the issue discussed in this thread: feel free to open a ticket and provide your login details. Martin and I are happy to help you directly!
Regarding the question: “Should the forum continue to exist?”
The poll on Facebook is simply meant to give us a better sense of how much the forum is currently being used, and how the community feels about it. We want to involve users in decisions like this.
Even though most people currently lean towards shutting down the forum, that doesn’t mean we’ve made a final decision. We’re still weighing our options.
In fact, we’re even considering closing down the current support platform entirely and moving all support into a dedicated category in the forum, accessible only to verified customers.
We’re keeping all possibilities open and will make a decision soon.
Just posting here as well for others regarding the initial bug reports. Also answered you via ticket
1. Custom Action Documentation
You’re absolutely right. Initially, the Bricks and Bricksforge docs were closely aligned, but since Bricks has evolved quite a bit, the examples in our documentation don't match perfectly anymore.
We’re planning a docs update to better reflect the current situation. In the meantime, it’s indeed best practice to use error_log() or similar tools during development to inspect the actual data structure being passed. So you know exactly how the data comes in
2. Global JS Variables for Conditions
I see the confusion here. Bricksforge doesn’t rely on regular global JS variables. Instead, all variables for conditions are stored inside window.bricksforgeData.globalVariables and are designed to be created via UI. So instead of setting var MyVar = "Test";, you could do something like:
With the recent decision to push forward with supporting the forums - what is your preferred approach for reporting bugs and/or issues? Should we post here AND submit a support ticket, or moving forward, should we just post here - and then bump posts that are not being attended to? I want to make sure we don’t waste your time or our own when reporting issues and/or asking for help.
Just wanted to chime in here as well. As I’ve mentioned several times before, the forum is currently intended more as a user-to-user space. It was never designed to be an official support channel.