Description

Only try to move and/or remove Core's Customizer link when a block theme is active.

Note that this is a real-world issue on WordPress.com, where the AMP plugin uses the Customizer to autofocus an AMP section in the Customizer. You will not see the bug on a standard install as our load order is a bit different so the AMP callback to admin_menu calls prior to gutenberg_remove_legacy_pages, despite both being on the default 10 priority. Any plugin that leverages the Customizer will see its link restored rather than the Customizer itself.

Testing Instructions

Add a customizer-based appearance menu at an early priority. Eg:

add_action( 'customize_register', '__return_false' );
add_action( 'admin_menu', function() {
	add_theme_page(
		'Third Party',
		'Third Party',
		'edit_theme_options',
		'customize.php?autofocus'
	);
}, 9 );

Without this patch, you should see that the Third Party item is restored rather than the Core Customizer link. With this patch, both are maintained, but the Customizer is demoted according to the intent the original code by @Mamaduka in #37175

Screenshots

Before:

After:

Types of changes

Bug fix

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• 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 (please manually search all *.native.js files for terms that need renaming or removal).
• I've updated related schemas if appropriate.