SOLVED: Post Content and Form Fields Disappear After First Radio Button/Checkbox for logged in Users

Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL: Link to a page that illustrates this issue
Video: Short screen recording that illustrates this issue (free tool: jam.dev)

I’ve set up a frontend form to update a custom post. However, when I include radio buttons or checkboxes as input fields, the post content stops displaying for logged-in users and is also missing from the DOM. Instead, only the form itself appears—but only up to the point where the first radio button or checkbox is rendered. All fields that come before the first radio button or checkbox display correctly, but everything after that point, including the rest of the form, does not appear at all.

Sorry, I have solved this. It was an issue with the fields not being hooked up correctly to the data, I think.

I’m not able to reproduce the bug anymore.

Sorry, I have now reproduced the bug. It happens if there is data selected in the meta-field that is connected to the form field.

Hi @Jonas0815,

We were unable to replicate the issue locally. Could you please share temporary admin access to your staging environment? You may send the login details to help@bricksbuilder.io with a link to this forum thread URL so we can track it.

Just to share an update here: we were able to replicate the issue when more than one option is selected and have added this to our internal bug tracker.

We fixed this issue in Bricks 2.1, now available as a one-click update in your WordPress Dashboard.

Please take your time to read the changelog entry before updating: Bricks 2.1 Changelog – Bricks + Bricks 2.1-beta Changelog – Bricks, and let us know if you continue to experience issues.

Hello Dear Bricks Team,

First of all, thank you for your great work and support. Unfortunately, I have to inform you that this issue is not resolved for me with Bricks 2.1.1. Having a checkbox field with multiple values selected still crashes the post. In fact, there is a new wrinkle to the problem, where the custom post also crashes in the backend. I hope the video helps.

https://1drv.ms/v/c/c01e2a84860fc2e7/EQhxP7E8KXVCipf4JRRhjcEBRW5Gs_UMY84KsjijTGw1qg?e=VfmhfO

Hi @Jonas0815,

I’m unfortunately unable to replicate the issue locally following the 2.1-stable release, so could you please share temporary admin access to a staging clone over our email thread so we can debug further?