-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Template activation: inserting template through /templates should always result in active template #72770
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
Conversation
|
Size Change: 0 B Total Size: 2.37 MB ℹ️ View Unchanged
|
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
…ays result in active template
5e48416 to
029c1da
Compare
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.
PR fixes the template activation upon creating template via endpoint! 👍
PR made dozens of WooCommerce E2E tests to pass thanks to it
|
Thank you! |
…ays result in active template (#72770) Co-authored-by: ellatrix <[email protected]> Co-authored-by: kmanijak <[email protected]>
|
I just cherry-picked this PR to the wp/6.9 branch to get it included in the next release: c7a8088 |
What?
To condition to distinguish between routes in
rest_pre_insert_wp_templateis wrong.Why?
We need to maintain backwards compatibility: all templates created through
/templatesshould automatically activate.How?
We should check the route instead.
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast