Predefined values not working after the update

[AndreeaCristinaRadacina]

Description

A user reported that the default values no longer work after the update. He has radio inputs with options, where the name of the option is used as default value, but the changes are not reflected on live website.

ref: https://secure.helpscout.net/conversation/2526814758/406626?viewId=212385

Step-by-step reproduction instructions

1. Insert a radio button
2. Add an option
3. Use the option's name in the default value area

Screenshots, screen recording, code snippet or Help Scout ticket

URL: https://merchprint.se/produkt/test/

Environment info

No response

Is the issue you are reporting a regression

Yes, this is a regression.

[AndreeaCristinaRadacina]

+1 https://wordpress.org/support/topic/pre-set-values/

[GrigoreMihai]

@AndreeaCristinaRadacina Could you help me a bit confirming if this was working previous the update ? I tried using it with the previous version and it's still broken.

If it's working on previous versions for you can you please share and instance where it is working with an older version, it will help a lot, thank you!

[AndreeaCristinaRadacina]

Sure:

• https://conscioushearing.s1-tastewp.com/wp-admin
• user
• bb)ES1i0KuNOl*Wvjp6BTUVr

[GrigoreMihai]

@AndreeaCristinaRadacina Thank you for the details, I'm still struggling to replicate the issue, even on your instance after updating the plugin the default value is still selected: https://vertis.d.pr/v/mhwlUu .

Are there any additional steps that you took when replicating ?

[AndreeaCristinaRadacina]

Hey @GrigoreMihai,

Thank you for your patience, and I apologize for the delay.

The problem occurs when using the radio input as a conditional field. I set this up in PPOM; you can test it on the Test product.
There is a radio field displayed under conditions, that ignores the default value and a simple radio input that displays it without problem.

What I also noticed is that the same problem occurs to me even before the update in 32.0.9, so I am not exactly sure which was the trigger that made them report it now.

One of the customers also mentioned that rolling back didn't have any effect on the pre-defined values, as if they didn't exist: