Optimised 6th migration script (fixture posts replacement) #9812
Conversation
This file contains 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
no issue - do only look for published old fixture posts - otherwise we detect draft old fixture post - and then we would replace them with published new fixture posts, which is not a very nice experience - ensure, if we have found all old fixture posts, replace all of them with the correct date - otherwise they are getting replaced and the date is now - this migration script is tricky and it tries to be smart, but there are so many cases we can run into - to remember: the goal was to replace old with new fixture posts (e.g. you just installed 1.25, but 2.0 is out and you migrate straight) - added more protection to ensure we don't delete custom posts
kirrg001
force-pushed
the
optimise-6th-mig
branch
from
79fe0f4
to
426172e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
no issue