s the front-end Live Editor ( Customize.php ) now part of the WP Core ?
Yes. It was added in WordPress 3.5(?).
it’s just an empty framework without options.
I think there’s a problem within your themes. At the very least, the customizer should provide options to change the site title & tagname and an option to set a static front page.
Thread Starter
Shmoo
(@macpresss)
Yeah I know this feature has been part of WP for some time but in the past i’ve always deleted it from the functions.php file because I don’t need it in my themes.
This code-snippet was always at the very end of the functions.php ( 2011 )
/**
* Binds JS handlers to make Theme Customizer preview reload changes asynchronously.
*
* @since Twenty Twelve 1.0
*/
function twentytwelve_customize_preview_js() {
wp_enqueue_script( 'twentytwelve-customizer', get_template_directory_uri() . '/js/theme-customizer.js', array( 'customize-preview' ), '20130301', true );
}
add_action( 'customize_preview_init', 'twentytwelve_customize_preview_js' );
If I deleted this code-snippet and also deleted the Google Webfonts, custom-headers and other stuff this ‘Customize’ menu-item was gone from the back-end.
Now at WP 3.6 Beta 2 I’ve done the same thing deleted all those scripts and code-snippets I don’t need from the functions.php ( 2013 ) but still the empty framework of the Live Editor is active in the menu.
That shouldn’t happen I believe.
That script you’ve been removing was purely a bit of javascript to make the customizer more dynamic (ie no refresh needed). The customizer itself has always been very much part of core since it was first introduced.
Why are you trying to remove it? Maybe there’s a better way to approach this?
Thread Starter
Shmoo
(@macpresss)
Because I don’t need it, those features shouldn’t be part of my CMS.
If I want to change Webfonts or change the size and color of my site title I’ll go inside the stylesheet to modify those changes where they belong.
I can understand WordPress wants to be that Uber friendly CMS that can do it all without knowing a single line of code but at least make it enjoyable for developers and beginners.
See this screenshot, I’ve never had this option around thats why I mention it right away.
http://i.imgur.com/IgVzdF1.png (first is 3.6 other are 3.5.1)
Because I don’t need it, those features shouldn’t be part of my CMS.
You could hide that menu option completely using CSS loaded via your themes. But, bottom line, this really isn’t a 3.6 beta issue since the customizer has been in core for a while now. If you’re looking for a coded solution, you could try posting in the Hacks forum.
Thread Starter
Shmoo
(@macpresss)
But how can you explain this feature has never showed up before in earlier versions because I simply don’t have any customizable features activated , and while testing my themes without changing anything in 3.6 Beta it does shows up out of the blue.
And the worst part is it shows up empty, just a framework with nothing inside it.
Thanks for your help btw I really appreciate it.
For now I have hide-/removed it by a code snippet.
// Hide (sub) menuitems from the admin menu
function remove_submenus() {
global $submenu;
//Appearance Menu
unset($submenu['themes.php'][6]); // Customize
}
add_action('admin_menu', 'remove_submenus');
Credits.
http://wpsnipp.com/index.php/functions-php/remove-all-admin-submenu-items/
how can you explain this feature has never showed up before in earlier version
I’m sorry – I have no idea but then I don’t know your theme. I only know that the Customizer has always displayed in all of my themes (and in any other theme I’ve checked) since WordPress 3.4.
@shmoo: if you’re talking about Customize admin menu link under Appearance, it was added in WP 3.6.
Not the Customize menu link under Appearance. Customize Feature have been around ages:)
Ah! But the OP asked about Customize.php – which has been around since 3.4 🙂
