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.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bojanz created an issue. See original summary.

bojanz’s picture

Status: Active » Needs review
FileSize
2.52 KB

Rearranging address properties is not feasible for BC, it would also affect the Views integration.
So let's handle this in ConfigurableFieldManager.

bojanz’s picture

Status: Needs review » Fixed

Committed.

  • bojanz committed 3a98a2f on 8.x-2.x
    Issue #3072156 by bojanz: ConfigurableFieldManager::hasData() doesn't...
bojanz’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.