Description

Ensures renaming a template-part moves it to 'publish' status if it is not already, this fixes a bug where if we rename a theme supplied template part before customizing content, it remains stuck in the auto-draft status indefinitely and is not found in our query requests for template parts.

More on the bug/background:

When a template part auto-draft is customized, it is upgraded from 'auto-draft' to 'publish' status to signify it is customized and to allow another theme default auto-draft to be created in the background.

Currently, the rename toolbar does not handle any publish status. Because of this, if you rename before customizing content, the template part will stay in auto-draft status under a slug which is not supplied by the theme and is not found in our search for template parts.

To reproduce the bug:

• Load a fresh theme supplied template part.
• Rename and save.
• Open the template part selection dropdown from the down chevron next to the name input in the toolbar.
• Notice the template part under the new name is not present in the list.

How has this been tested?

• Load a fresh theme supplied template part.
• Rename and save.
• Open the template part selection dropdown from the down chevron next to the name input in the toolbar.
• Verify the template part under the new name is present in the list.

Screenshots

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.