Beta task checklist

[dreamwhisper]

• Add error message if post type added to pattern no longer exists. eg. A post type added to your pattern no longer exists. / You have a post type in your pattern that doesn't exist in WordPress.
• Renaming a pattern creates a new copy. Fix renaming bug where there were 2 patterns #61
• consider doing a couple of things when a theme is changed:
  - Delete all pm_pattern posts (these are not needed as we pull from files) After switching themes, delete all pm_pattern posts #62
  - Send a notice through the heartbeat API to any patterns still open that says The theme was changed. This pattern does not exist in this theme. Please close this tab. In the editor, show a notice that the theme changed #65
• Make sure child themes work If the theme is a child theme, save patterns to the child theme #69
• Make sure content isn't stale when using back button.
• Ensure assets save appropriately. (related to tree-shaking, which is removed now) Bring back tree shaking #91
• Deleting title on the edit screen, then saving results in a php error Don't allow saving if there's no pattern title, or if it's a duplicate #67
• Ensure error messages are read by screen readers. wp.a11y.speak
• Make sure the previews resize with a browser resize. Fix issue with preview width when window is resized #109
• Wide alignment not working in pattern editor in 6.2 beta.
• Default width from theme.json not working.

Feel free to edit as needed. We could also create a project if we feel it is needed.

[kienstra]

Working on:

Renaming a pattern creates a new copy.

[kienstra]

Also working on:

Delete all pm_pattern posts (these are not needed as we pull from files)

[kienstra]

Could you expand on this?

Make sure content isn't stale when using back button.

[kienstra]

Also working on:

Send a notice through the heartbeat API to any patterns still open that says The theme was changed. This pattern does not exist in this theme. Please close this tab.

[kienstra]

Hi @dreamwhisper,
Could you expand on this, please?

Make sure content isn't stale when using back button.

(If that was your idea)

[dreamwhisper]

@kienstra Might need @johnstonphilip to expand on that one. I think it's that the previews aren't up to date with what should be showing.

[kienstra]

Ah, that makes sense! Thanks!

[kienstra]

If it would help, I could demo this in Sprint Review:

• Send a notice through the heartbeat API to any patterns still open that says The theme was changed. This pattern does not exist in this theme. Please close this tab. In the editor, show a notice that the theme changed #65
• Deleting title on the edit screen, then saving results in a php error Don't allow saving if there's no pattern title, or if it's a duplicate #67
• Make sure child themes work If the theme is a child theme, save patterns to the child theme #69

[johnstonphilip]

Alignments should be fixed with WordPress/gutenberg#48380

[kienstra]

Hi @dreamwhisper,
Is this working now?

Ensure assets save appropriately.

Hope you had a great weekend.