id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
20858	Themes should have to support the new customizer or be able to disable it	martythornley		"The new customizer tools lok and work great for themes that want to suppor it.

But many themes will have their own options already and may not want to. There are also endless numbers of existing themes that will not support it because they were built before 3.4

While including the ""Customize"" link and allowing the customizer to open does not break anything, there are a few reasons why themes need to be able to disable it altogether. It can be confusing for users to click a ""Customize"" link and have a page pop up with no actual customization options.

The options to choose what the front page displays are still there, as are the site title and description. These are settings for the site as a whole and not the theme and could create a few more points of confusion.

While the typical theme is made to be flexible and allow the front page to use the ""latest posts"" or a ""static page"" there are also themes, especially on custom sites that do not use that setting. 

Many themes will not make use of the site title or description at all and use a logo of some kind. While that option still needs to be there somewhere, it should not be as prominent as it is here (for themes that do not want to support it).

I can think of two solutions, either make themes declare support for the customizer, OR allow a simple ""WP_DISALLOW_CUSTOMIZER"" constant.

Then we could do something like:

if( current_theme_supports('customizer') )
	wp_enqueue_script( 'customize-loader' );

OR

if( ! defined ( 'WP_DISALLOW_CUSTOMIZER' ) )
	wp_enqueue_script( 'customize-loader' );

There may be more to it than this but I think theme authors need to be able to either opt-in or opt-out of a feature like this."	feature request	closed	normal		Themes	3.4	normal	wontfix