Pro Forms: {all_fields} not behaving like native Bricks

Feature Requests
1

Hi! I am making a form and was wondering why {{all_fields}} doesn’t display like native Bricks. Native Bricks forms display the name and field value, but BricksForge display the field ID instead of field name.

For example Bricks puts out this
Name: TEST NAME
Email: email@example.com
Subject: TEST SUBJECT
Message: TEST MESSAGE TEST MESSAGE

But Bricksforge puts out this:
jusyeo: TEST NAME
axqxgy: email@example.com
klamnc: TEST SUBJECT
bsxpvf: TEST MESSAGE TEST MESSAGE

I’m just using Bricksforge for the dynamic/conditional email settings so I configured all of my fields in the native section rather than using the additional Bricksforge elements.

Also, {{all_fields}} isn’t filled by default if you leave the email content empty like Bricks does. It would be nice to update that cause it threw me for a loop as to why my emails weren’t working at the beginning.

2

Hmm…normally, the name should be the value of your label. Is it possible that the “Label” control of your fields is empty?

3

No, they are all filled! Double checked today

4

Hmm… please create a ticket sending us access. We’ll take a look :slight_smile:

5

Just a small note for all others: The form here is using the legacy approach of creating forms. When using the Nestable Forms approach, everything works as expected.