[5.x] Update updated_at and updated_by when duplicating an entry
#12777
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
aerni
changed the title
updated_at and updated_by when duplicating an entryupdated_at and updated_by when duplicating an entry
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 PR makes sure
updated_atandupdated_byget refreshed when you duplicate an entry in the CP.Context
On one of my projects, entry slugs include a timestamp from when they were created, for example:
ceiling-in-the-floor-1759364440. That timestamp comes fromupdated_atat the time the entry is created.The issue was that when duplicating an entry, the duplicate kept the original entry’s
updated_atandupdated_by, which meant both entries ended up with the same timestamp in the slug.This PR fixes that by giving duplicated entries a new
updated_atandupdated_by, so their slugs stay unique.