Patterns: fix issue in 16.1 with wrong sync status set in Site Editor#52229
Patterns: fix issue in 16.1 with wrong sync status set in Site Editor#52229glendaviesnz merged 4 commits intorelease/16.1from
Conversation
|
Size Change: +9 B (0%) Total Size: 1.44 MB
ℹ️ View Unchanged
|
aaronrobertshaw
left a comment
There was a problem hiding this comment.
Thanks for putting this one together @glendaviesnz 👍
I couldn't replicate the issue with new patterns created on the release/16.1 branch not showing in the correct sections in the site editor. I did encounter an old synced pattern from previous testing appearing in an incorrect location though.
After applying this PR:
✅ New and existing patterns are displayed in the correct sections in the site editor
✅ The issue preventing updating the patterns sync status in the post editor has been fixed
✅ After editing a pattern's sync status the pattern's location in the site editor is correctly updated
✅ All patterns were showing in the correct locations in the block editor
✅ Synced patterns appear in the quick inserter and under the correct tab in main inserter
✅ Unsynced patterns appear in custom patterns category in main inserter
* Fix phpunit failures * Add comment * Update comment with actual reason this fix works
What?
There was a bug with synced patterns added in the Site Editor having a deprecated sync status added, which causes them not to display in the post editor inserter.
Why?
The bug was fixed here, but this fix did not make it into the 16.1 release.
How?
Cherry picked the relevant commit and also added a check for the incorrect sync status to the reusable block selector.
This also includes the following php unit test fixes from trunk:
Testing Instructions
Screenshots or screencast
Before:
synced-before.mov
After:
synced-after.mov