Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It can be confusing for users that template parts are not always listed under "patterns" #68704

Open
carolinan opened this issue Jan 16, 2025 · 1 comment
Labels
[Block] Template Part Affects the Template Parts Block [Type] Enhancement A suggestion for improvement. [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable

Comments

@carolinan
Copy link
Contributor

What problem does this address?

In Appearance > Editor , template parts are created and listed on the Patterns screen.
But in the Site Editor, template parts are not listed when you open the block inserter and select the Patterns tab.
This may be confusing and it makes footer and header template parts more difficult to insert.

Please see this support forum post: https://wordpress.org/support/topic/a-custom-footer-has-been-created-but-does-not-appear-in-the-list-of-compositions/

What is your proposed solution?

List template parts as a category on the Patterns tab in the block inserter, like on the pattern Data view screen.

@carolinan carolinan added [Block] Template Part Affects the Template Parts Block [Type] Enhancement A suggestion for improvement. [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable labels Jan 16, 2025
@carolinan
Copy link
Contributor Author

Also named template parts can not be inserted using /name

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Template Part Affects the Template Parts Block [Type] Enhancement A suggestion for improvement. [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable
Projects
None yet
Development

No branches or pull requests

1 participant