-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Site Editor: 'page-home' template is categorized as a 'General' template #30454
Comments
I named my templates template-page-sidebar-left.html and so on and they show up under general. |
Sorry, I should have clarified page templates beginning with 'page-' It seems weird how templates that start 'page-' are grouped under page templates, yet 'page-home' is grouped under general. How is it decided which page templates are 'Page templates', and which page templates are 'General templates'? |
It looks like it is expecting the home template to be home, not page-home. The pr says that "page-home is an exception, it's set to shown up in General" #28291 So I think it is working as intended? |
I think the sections should work as follows:
So I think the issue here is may be the name of the template in tt1-blocks? It needs testing, but as it stands I think any template with a |
The UI has changed a lot here and these sections don't exist anymore. |
Description
The TT1 Blocks theme has one additional custom page template - 'page-home.html'
In the Site Editor > page templates side navigation panel, the 'page-home' template is grouped under the 'General templates' sub-panel.
Step-by-step reproduction instructions
Expected behaviour
Custom page templates should be grouped in 'Page templates'
Actual behaviour
A custom page template with the file name 'page-home.html' is grouped in 'General templates'
I tested with variations of the file name and creating additional page templates, and the only time a custom page template is not grouped in 'Page templates' is when it is specifically named 'page-home.html'
Screenshots or screen recording (optional)
Code snippet (optional)
WordPress information
Device information
The text was updated successfully, but these errors were encountered: