[6.x] Only change date for localizations with an explicit date set#14362
Merged
jasonvarga merged 2 commits into6.xfrom Mar 26, 2026
Merged
[6.x] Only change date for localizations with an explicit date set#14362jasonvarga merged 2 commits into6.xfrom
jasonvarga merged 2 commits into6.xfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request fixes an issue where the
migrate-dates-to-utccommand would result in incorrect dates for localized entries in multisite setups.This was happening because when a localized entry inherits its date from an origin entry, calling
$item->date()returns the origin's date. If the origin was processed first, this date would already be in UTC, but the command would treat it as being in the current timezone and convert it again, causing double-conversion.This PR fixes it by checking
hasExplicitDate()before migrating entry dates. Entries that don't have an explicit date (they inherit from the origin) are now skipped, since the origin will be migrated separately and the inheritance will continue to work correctly.Fixes #14343