Skip to content

Commit

Permalink
add link to the correct spot
Browse files Browse the repository at this point in the history
  • Loading branch information
colinswinney committed Oct 1, 2024
1 parent 00f51c9 commit b3b9943
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 1 deletion.
3 changes: 3 additions & 0 deletions reference/04-Patterns/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -278,6 +278,9 @@ This is achieved by adding `"__experimentalRole": "content"` to the attribute de

:::caution
There is one item that you need to be aware about in regards to Block Patterns. Once they are inserted they have no link to the original block pattern that they were created by. On insertion they become regular blocks. Therefore it is not possible to adjust all occurrences of a block pattern after it has been used.

WordPress does provide a way of handling this however by using the power of Synced Patterns. [For more info on Synced Patterns, please see the next lesson](../Patterns/synced-patterns).

:::

If you find an issue with the markup of a pattern that you want to fix it is only going to impact new instances of the pattern that are created after you updated it. And you will have to manually go into every instance that was created using the pattern and make the update manually, or create an update script to update it in the database directly.
Expand Down
1 change: 0 additions & 1 deletion training/04-patterns.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,5 +136,4 @@ Try to replace the image url with a dynamically generated url of the image file
## Further reading

- [Block Patterns Overview - 10up Gutenberg Best Practice](../reference/Patterns/overview)
- [Block Patterns Synced Patterns - 10up Gutenberg Best Practice](../reference/Patterns/synced-patterns)
- [Patterns - Block Editor Handbook](https://developer.wordpress.org/block-editor/reference-guides/block-api/block-patterns/)

0 comments on commit b3b9943

Please sign in to comment.