Skip to content

[6.x] Fix blueprint assignment of entries using custom entry class - #15017

Merged
jasonvarga merged 2 commits into
statamic:6.xfrom
daun:fix/localized-entry-blueprint
Jul 16, 2026
Merged

[6.x] Fix blueprint assignment of entries using custom entry class#15017
jasonvarga merged 2 commits into
statamic:6.xfrom
daun:fix/localized-entry-blueprint

Conversation

@daun

@daundaun commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Fixes#15016

Issue

Localizing an entry can assign the wrong blueprint to the localization if two conditions are met:

  • the collection has multiple blueprints
  • the collection uses a custom entry class

This will lead to the default blueprint of the collection being assigned, instead of the origin entry's blueprint. The blueprint is not resolved because at the point of newing up the custom entry class, no origin is set.

Fix

Assigning the origin before the collection during localization allows resolving the correct blueprint.

@jasonvarga
jasonvarga merged commit 7105939 into statamic:6.xJul 16, 2026
20 checks passed
@daun
daun deleted the fix/localized-entry-blueprint branch July 16, 2026 15:31
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Localized entries with entry class are assigned the wrong blueprint

2 participants

@daun@jasonvarga