Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
AddressItem has no main property name, and the first property is the langcode which is empty in many cases (cause there's no language override for the field). ConfigurableFieldManager::hasData() takes the first property and runs a query against it, which in this case ends up being address.langcode, returning a wrong result.
We need to fix this in Address, by making sure the country_code property comes first and the langcode property last.
Once that makes it into a release, we need to update Commerce to require that version.
Comment | File | Size | Author |
---|---|---|---|
#2 | 3072156-2-configurable-field-manager.patch | 2.52 KB | bojanz |
|
Comments
Comment #2
bojanz CreditAttribution: bojanz at Centarro commentedRearranging address properties is not feasible for BC, it would also affect the Views integration.
So let's handle this in ConfigurableFieldManager.
Comment #3
bojanz CreditAttribution: bojanz at Centarro commentedCommitted.
Comment #5
bojanz CreditAttribution: bojanz at Centarro commented