-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Templates: Only allow renaming user-created and non-default templates #40881
Conversation
Size Change: +23 B (0%) Total Size: 1.23 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This solved the issue in my manual test, thank you.
Thanks for testing, @carolinan. Do you think this needs to be backported into the next RC? |
LGTM! 👍
I think it would be good to backport it, yes |
I cherry-picked this PR for WordPress 6.0 RC2 release with c844c75. |
What?
Resolves #40876.
PR disabled the title editing field for WP default templates and custom templates defined by the theme.
Why?
Renaming these templates will break pages/views assigned to them.
How?
Updates check to use both
is_custom
andhas_theme_file
properties.is_custom
property is true when the template isn't in the list of default WP templates.has_theme_file
is set for templates that have corresponding theme files.Testing Instructions
Instructions for the issue.
Additional testing:
Screenshots or screencast