91950cfea0
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 for the user - 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" - in general, 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 all old with new fixture posts (e.g. you just installed 1.25 and straight migrate to 2.0 - the old fixture posts should get replaced) - added more protections to ensure we never delete custom posts using the same fixture post slugs |
||
|---|---|---|
| .. | ||
| client@36bdca6dfe | ||
| server | ||
| test | ||
| index.js | ||