Radio buttons work in Dev but not Live

[qwatkins]

So I have no idea why this is happening. I have radio buttons that show/hide groups/options and they work properly in dev mode but not in live. I did a side by side screen recording to demonstrate. The tab on the left is the dev tab and the tab on the right is the live tab. Strangely, this just cropped up today, its been working without this issue prior to this and I have never seen this issue in my past 2 years with Bubble. Watch the video and please tell me I’m not crazy, any insights welcome.

Also, just prior to this I added a new entry on one of the data types but can’t remember if it happened immediately following that or not.

Things I’ve tried but to no avail:

1. Replace the Radio button element with another Radio button (rationale, screwed up widget)
2. Duplicated Radio button element with workflows (rationale, same as previous)

Here is the video

Here is the radio button set in the editor. I dynamically populate it with data from the Provision Templates entity. I am using the Programmable Template plugin to take user input data and blend it with the templates for the final output to PDF.

[rjayaddimalik]

Hy @qwatkins
Can you share your editor setup for the radio button so we can get a better idea about the issue and tell you the solution?

Tip: Push the changes again.

[qwatkins]

I’ve added some screen shots to the original post

[qwatkins]

@qwatkins

d Radio but

Ok after more working on this I’ve isolated the issue to be associated with the autobind. When I turn off autobinding then it works except, obviously, it doesn’t store the selection in the db because of no autobinding. Any thoughts on this anyone??

[J805]

I don’t know if the plugin allows for this but normally you can right click on an input like the radio button and create a workflow. Then you don’t need autobinding. I never use autobinding.

[code-escapee]

@qwatkins

Any thoughts on this anyone??

Since you asked for my thoughts, I’d honestly stop fighting the radio button here.

Bubble’s radio buttons are one of those elements that look simple but get weird fast, especially once autobinding and dynamic data are involved (not to mention the uncentered layout).

A more predictable pattern is:

• Ditch the radio button entirely
• Use a Repeating Group (or a simple group list) to display the options
• On click of a row, explicitly set the value you want

If you replace the radio button with a Repeating Group, you also solve the selection problem cleanly.

How to track the selected option

On click → set “8. child custody” (using the screenshot as an example) to be the current cell’s that group’s Provision Template option set.

How to show which row is selected

On the RG cell, add a conditional:

When Current cell's Provision Template option set= 8. Child custody
→ background color = highlighted
→ border = visible / thicker

That gives you a true “selected row” effect and makes the whole row clickable, not just a tiny radio dot.

If you like the radio button look, you can still fake it visually:

• Add an icon inside the cell (circle / check / dot)
• Default state = empty circle
• Conditional:

When Current cell's Provision Template option set= 8. Child custody
→ show filled circle / check icon

Functionally it behaves like a radio button group, but it’s explicit, stylable, and far more predictable.

[m.andremuniz]

Have you checked if the privacy rules are the same in both environments?

[qwatkins]

@code-escapee

group’s Provision Template o

Thanks for your response @code-escapee that is a solid approach. @J805 I use autobinding for the convenience and its been good so far.

I kept on poking and prodding and I discovered that it was a data issue. For reason(s) still unknown the live site records were missing a foreign key reference, which gets generated and set on the creation of a new client. I manually added back the key references and it started working as expected. So I put in some breakpoints, created a new client and stepped through that section of the code and it put the keys in correctly. So I’m still at a loss as to why that occurred in the first place because I had not changed that part of the workflow since I first made it.

Have any of you experienced unexpected holes in your live vs dev data before?

[J805]

Glad you figured it out.

I have not had any issues with the database before. Only issues that I made myself.