Obsidian Registration Entry Block Address Person Field Issues

[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.

• The State in the Address field defaults to AZ.
• The Address field will raise an error that Address Line 1 and City is required when it is not set to required.
  See screenshot below.

Expected Behavior

The address field State should be empty or defaults to the orgazanition state. The address field should not be required if it is not set as required.

Actual Behavior

Steps to Reproduce

• At first I set the address field to required, then I got tired of entering the address everytime I change something in the form when testing so I unchecked the Required.

Rock Version

15.1

Client Culture Setting

en-US

[joezimjs]

Fixed with this commit: fb106eb

[JDShuman]

@joezimjs The address is still automatically pre-filling to AZ for us. We have consistently been updating to the latest public release, so we are now on v16.0. Am I missing a setting somewhere that sets our default state?

[joezimjs]

@JDShuman Looking into this.

[joezimjs]

@JDShuman Under Admin Tools > General Settings > Global Attributes you'll find a setting for Organization Address

The default country and state are pulled from this address. I'm so sorry that I didn't address (no pun intended) this before marking it as fixed. Let me know if there's anything else I can do to help. If you don't need anything else, please re-close this issue. Thanks!

[JDShuman]

Thanks @joezimjs. I wondered if that is where it was pulling from, but we've had that set for several years now.

Any ideas on why that wouldn't be pulling into our event registrations correctly? For additional context, we are running a web farm setup, but I've verified that the Global Attribute is populated on each server (as expected).

[nairdo]

@JDShuman I'm afraid our fix had two parts to it and only one was in the v15.2 release. I just confirmed the bug is still in the v15.2 release but it is fixed in the upcoming v15.3 release (releasing next week) and v16.1 (via c6b8ce6 for issue #5607):

Sorry about that! We'll re-label this and correct the release note to be on the v15.3 release.

[joezimjs]

@JDShuman Nick and I dug a little deeper and found out why I marked it as fixed but it was still causing issues for you. The change in v15.2 / v16.0 did fix this issue for Registration Attributes, but I didn't realize that the Person Field was actually using a different mechanism for gathering the default value. This is fixed in v15.3 / v16.1. I'm sorry for the confusion.