Obsidian Registration Entry Does not Show Conditional Field When Not Logged-In Unless Toggled

[frogydiak]

Please go through all the tasks below

• Check this box only after you have successfully completed both the above tasks

Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.

I don't know what is Rock's dev terminology for the toggled field when enabling/disabling a conditional fields so I'm calling it "Toggle".

Anyhow, when a user is logged in, the set conditional fields works properly as intended but when a user is not, then the default field that is set to show up will not appear unless the field is toggled.

Expected Behavior

Obviously, conditional fields that are supposed to appear should appear as set regardless of the user is logged in or not. Unless, there is a reason for this and I'm understanding it wrong, please educate me.

Actual Behavior

Please see screenshots below.

Steps to Reproduce

• Create a Boolean Registration Field, and make No as the default value:
  

• Create the field that will show up when the boolean field is set to No and Yes:
  

• Since the default boolean answer is No, then set the default field when the boolean field is set to No:
  

• Set the field that will appear when the under to the boolean field is Yes:
  

• Make sure that your registration page is using Obsidian Registration Entry Block:
  

• Using the rock demo site, I am logged in by default when going to the External Site:
  

• Click Next and you'll see the field that is supposed to show up by default (boolean is No):
  

• This time, try to log out and check if the field that is supposed to show when boolean field is set to No still appears:
  

The field will appear if you click on Yes, then No. But that is not the logic intended for and would confuse the end user.

Rock Version

15.1

Client Culture Setting

en-US

[ethan-sparkdevnetwork]

Fixed in 9b8b259. There is a typo for the issue number in the commit message.

[frogydiak]

FYI, in v15.3, the issue also exists with field Source is Group Member Attribute. The boolean field is in group member attribute. But when I switch the field source to Registrant Attribute, it works just fine. Logged in or not.

[chead4]

@frogydiak Hi there. I am reopening this issue to address the Group Member Attribute issue mentioned in the comment.