New `address_primary` tokens don't work

https://github.com/civicrm/civicrm-core/pull/25032 introduced a new standard, such that a postal code token should be: {contact.address_primary.postal_code}.

There is also what the tests call the "briefly popular" interim format: {contact.primary_address.postal_code}.

However, the address_primary variant only works if either the corresponding primary_address OR legacy token is also present. The tests pass because the legacy tokens and new tokens are tested together.

E.g. this won't render:

pa postal: {contact.address_primary.postal_code}

But these two will:

old postal: {contact.postal_code}

pa postal: {contact.address_primary.postal_code}

interim postal: {contact.primary_address.postal_code}

pa postal: {contact.address_primary.postal_code}

added regression label

I didn't mark this as a regression at first, because it only affects the new token format. However, when I re-read the client report, I realized that the token browser is now broken, since it generates these non-functional tokens.

https://github.com/civicrm/civicrm-core/pull/25548

added has-pull-request label

mentioned in commit 9f8abff4

mentioned in commit 490bdff6

mentioned in commit 5a1ecf0d

mentioned in commit be654e8f

changed milestone to %5.58.1

closed

mentioned in issue #4147 (closed)