Skip to content

fix: Reading associations via the parent, if the parent has multiple associations of the same type and to the same entity (backport: 6.6.x)#15206

Merged
Michael Telgmann (mitelg) merged 2 commits into6.6.xfrom
fix/customer-default-addresses-assocations-backport-6.6.x
Feb 26, 2026
Merged

fix: Reading associations via the parent, if the parent has multiple associations of the same type and to the same entity (backport: 6.6.x)#15206
Michael Telgmann (mitelg) merged 2 commits into6.6.xfrom
fix/customer-default-addresses-assocations-backport-6.6.x

Conversation

@shopware-octo-sts-app
Copy link
Copy Markdown
Contributor

Backport: #14215


1. Why is this change necessary?

Reading child associations via the parent entity is broken, if the parent has multiple associations of the same type to the same child entity.
e.g. the relation from the customer to its default shipping and billing address.

2. What does this change do, exactly?

Fix the ApiController so it is not only checking if the reference definition is matching, but also the reference field.

5. Checklist

  • I have written tests and verified that they fail without my change
  • I have updated developer-facing release notes if this change is relevant for external developers:
    • Add a short entry to RELEASE_INFO-6.<major>.md under “Upcoming” for informational changes, including the consequences of the change and how it affects external developers.
    • Add an UPGRADE section in UPGRADE-6.<next-major>.md for breaking changes (what/why/impact/how to adapt).
    • See the Documenting a Release Process for details.
  • I have written or adjusted the documentation according to my changes
  • This change has comments for package types, values, functions, and non-obvious lines of code
  • I have read the contribution requirements and fulfilled them

@github-actions
Copy link
Copy Markdown

Warnings
⚠️ The Pull Request doesn't contain any changelog file

@mitelg Michael Telgmann (mitelg) force-pushed the fix/customer-default-addresses-assocations-backport-6.6.x branch from 4180355 to e1fbe2e Compare February 26, 2026 09:20
@mitelg Michael Telgmann (mitelg) force-pushed the fix/customer-default-addresses-assocations-backport-6.6.x branch from e1fbe2e to d527181 Compare February 26, 2026 10:01
@mitelg Michael Telgmann (mitelg) removed the external-contribution A PR contributed by a community member. label Feb 26, 2026
@mitelg Michael Telgmann (mitelg) added this pull request to the merge queue Feb 26, 2026
Merged via the queue into 6.6.x with commit b6a72a2 Feb 26, 2026
49 checks passed
@mitelg Michael Telgmann (mitelg) deleted the fix/customer-default-addresses-assocations-backport-6.6.x branch February 26, 2026 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component/core domain/framework Responsible for the framework-level code includes core, administration, storefront, and frontends

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants