2004-09-11 12:12:40 -04:00
< ? php
2008-08-16 03:27:34 -04:00
/**
* Themes administration panel .
*
* @ package WordPress
* @ subpackage Administration
*/
/** WordPress Administration Bootstrap */
2013-09-24 20:18:11 -04:00
require_once ( dirname ( __FILE__ ) . '/admin.php' );
2010-12-16 03:43:22 -05:00
2010-12-07 16:06:19 -05:00
if ( ! current_user_can ( 'switch_themes' ) && ! current_user_can ( 'edit_theme_options' ) )
2014-11-16 01:16:22 -05:00
wp_die ( __ ( 'Cheatin’ uh?' ), 403 );
2010-12-13 16:21:50 -05:00
2010-12-03 05:13:17 -05:00
if ( current_user_can ( 'switch_themes' ) && isset ( $_GET [ 'action' ] ) ) {
2009-03-05 13:45:26 -05:00
if ( 'activate' == $_GET [ 'action' ] ) {
2012-06-06 16:34:24 -04:00
check_admin_referer ( 'switch-theme_' . $_GET [ 'stylesheet' ]);
$theme = wp_get_theme ( $_GET [ 'stylesheet' ] );
if ( ! $theme -> exists () || ! $theme -> is_allowed () )
2014-11-16 01:16:22 -05:00
wp_die ( __ ( 'Cheatin’ uh?' ), 403 );
2012-06-26 01:21:04 -04:00
switch_theme ( $theme -> get_stylesheet () );
2010-10-27 06:43:43 -04:00
wp_redirect ( admin_url ( 'themes.php?activated=true' ) );
2005-09-05 19:33:10 -04:00
exit ;
2010-12-03 05:13:17 -05:00
} elseif ( 'delete' == $_GET [ 'action' ] ) {
2012-06-06 16:34:24 -04:00
check_admin_referer ( 'delete-theme_' . $_GET [ 'stylesheet' ]);
$theme = wp_get_theme ( $_GET [ 'stylesheet' ] );
if ( ! current_user_can ( 'delete_themes' ) || ! $theme -> exists () )
2014-11-16 01:16:22 -05:00
wp_die ( __ ( 'Cheatin’ uh?' ), 403 );
2014-12-01 21:21:24 -05:00
$active = wp_get_theme ();
if ( $active -> get ( 'Template' ) == $_GET [ 'stylesheet' ] ) {
wp_redirect ( admin_url ( 'themes.php?delete-active-child=true' ) );
} else {
delete_theme ( $_GET [ 'stylesheet' ] );
wp_redirect ( admin_url ( 'themes.php?deleted=true' ) );
}
2009-03-05 14:15:56 -05:00
exit ;
2004-09-11 12:12:40 -04:00
}
2005-09-05 19:33:10 -04:00
}
2004-09-11 12:12:40 -04:00
2006-11-18 02:31:29 -05:00
$title = __ ( 'Manage Themes' );
$parent_file = 'themes.php' ;
2008-05-20 13:19:33 -04:00
2013-12-01 22:23:10 -05:00
// Help tab: Overview
if ( current_user_can ( 'switch_themes' ) ) {
$help_overview = '<p>' . __ ( 'This screen is used for managing your installed themes. Aside from the default theme(s) included with your WordPress installation, themes are designed and developed by third parties.' ) . '</p>' .
'<p>' . __ ( 'From this screen you can:' ) . '</p>' .
'<ul><li>' . __ ( 'Hover or tap to see Activate and Live Preview buttons' ) . '</li>' .
'<li>' . __ ( 'Click on the theme to see the theme name, version, author, description, tags, and the Delete link' ) . '</li>' .
'<li>' . __ ( 'Click Customize for the current theme or Live Preview for any other theme to see a live preview' ) . '</li></ul>' .
'<p>' . __ ( 'The current theme is displayed highlighted as the first theme.' ) . '</p>' ;
2010-06-02 16:04:07 -04:00
2013-12-01 22:23:10 -05:00
get_current_screen () -> add_help_tab ( array (
'id' => 'overview' ,
'title' => __ ( 'Overview' ),
'content' => $help_overview
) );
} // switch_themes
2011-11-29 12:34:08 -05:00
2013-12-01 22:23:10 -05:00
// Help tab: Adding Themes
2011-11-29 12:34:08 -05:00
if ( current_user_can ( 'install_themes' ) ) {
if ( is_multisite () ) {
2011-11-30 19:36:19 -05:00
$help_install = '<p>' . __ ( 'Installing themes on Multisite can only be done from the Network Admin section.' ) . '</p>' ;
2011-11-29 12:34:08 -05:00
} else {
2014-03-07 23:14:15 -05:00
$help_install = '<p>' . sprintf ( __ ( 'If you would like to see more themes to choose from, click on the “Add New” button and you will be able to browse or search for additional themes from the <a href="%s" target="_blank">WordPress.org Theme Directory</a>. Themes in the WordPress.org Theme Directory are designed and developed by third parties, and are compatible with the license WordPress uses. Oh, and they’re free!' ), 'https://wordpress.org/themes/' ) . '</p>' ;
2011-11-29 12:34:08 -05:00
}
get_current_screen () -> add_help_tab ( array (
2011-11-30 20:24:39 -05:00
'id' => 'adding-themes' ,
'title' => __ ( 'Adding Themes' ),
2012-05-07 13:26:16 -04:00
'content' => $help_install
) );
2013-12-01 22:23:10 -05:00
} // install_themes
2012-06-06 16:34:24 -04:00
2013-12-01 22:23:10 -05:00
// Help tab: Previewing and Customizing
2014-07-14 15:01:16 -04:00
if ( current_user_can ( 'edit_theme_options' ) && current_user_can ( 'customize' ) ) {
2012-05-07 13:26:16 -04:00
$help_customize =
2013-12-01 22:23:10 -05:00
'<p>' . __ ( 'Tap or hover on any theme then click the Live Preview button to see a live preview of that theme and change theme options in a separate, full-screen view. You can also find a Live Preview button at the bottom of the theme details screen. Any installed theme can be previewed and customized in this way.' ) . '</p>' .
'<p>' . __ ( 'The theme being previewed is fully interactive — navigate to different pages to see how the theme handles posts, archives, and other page templates. The settings may differ depending on what theme features the theme being previewed supports. To accept the new settings and activate the theme all in one step, click the Save & Activate button above the menu.' ) . '</p>' .
'<p>' . __ ( 'When previewing on smaller monitors, you can use the collapse icon at the bottom of the left-hand pane. This will hide the pane, giving you more room to preview your site in the new theme. To bring the pane back, click on the collapse icon again.' ) . '</p>' ;
2012-05-08 21:38:54 -04:00
2012-05-07 13:26:16 -04:00
get_current_screen () -> add_help_tab ( array (
'id' => 'customize-preview-themes' ,
2013-12-01 22:23:10 -05:00
'title' => __ ( 'Previewing and Customizing' ),
2012-05-07 13:26:16 -04:00
'content' => $help_customize
2011-11-29 12:34:08 -05:00
) );
2014-07-14 15:01:16 -04:00
} // edit_theme_options && customize
2009-05-11 14:59:09 -04:00
2011-11-02 16:14:10 -04:00
get_current_screen () -> set_help_sidebar (
2013-12-02 13:58:09 -05:00
'<p><strong>' . __ ( 'For more information:' ) . '</strong></p>' .
'<p>' . __ ( '<a href="http://codex.wordpress.org/Using_Themes" target="_blank">Documentation on Using Themes</a>' ) . '</p>' .
2014-03-07 23:14:15 -05:00
'<p>' . __ ( '<a href="https://wordpress.org/support/" target="_blank">Support Forums</a>' ) . '</p>'
2011-11-01 23:12:37 -04:00
);
2013-11-13 15:58:05 -05:00
if ( current_user_can ( 'switch_themes' ) ) {
$themes = wp_prepare_themes_for_js ();
} else {
$themes = wp_prepare_themes_for_js ( array ( wp_get_theme () ) );
}
2013-12-06 22:11:10 -05:00
wp_reset_vars ( array ( 'theme' , 'search' ) );
2013-11-13 15:58:05 -05:00
wp_localize_script ( 'theme' , '_wpThemeSettings' , array (
'themes' => $themes ,
'settings' => array (
2013-11-20 09:09:10 -05:00
'canInstall' => ( ! is_multisite () && current_user_can ( 'install_themes' ) ),
2013-11-29 04:01:09 -05:00
'installURI' => ( ! is_multisite () && current_user_can ( 'install_themes' ) ) ? admin_url ( 'theme-install.php' ) : null ,
2013-11-13 15:58:05 -05:00
'confirmDelete' => __ ( " Are you sure you want to delete this theme? \n \n Click 'Cancel' to go back, 'OK' to confirm the delete. " ),
2014-02-25 14:22:13 -05:00
'adminUrl' => parse_url ( admin_url (), PHP_URL_PATH ),
2013-11-13 15:58:05 -05:00
),
2013-11-20 14:44:12 -05:00
'l10n' => array (
'addNew' => __ ( 'Add New Theme' ),
2013-12-09 02:41:10 -05:00
'search' => __ ( 'Search Installed Themes' ),
2014-03-19 04:18:14 -04:00
'searchPlaceholder' => __ ( 'Search installed themes...' ), // placeholder (no ellipsis)
2013-11-20 14:44:12 -05:00
),
2013-11-13 15:58:05 -05:00
) );
2013-11-19 21:57:10 -05:00
add_thickbox ();
2010-09-24 14:50:31 -04:00
wp_enqueue_script ( 'theme' );
2012-04-16 10:02:28 -04:00
wp_enqueue_script ( 'customize-loader' );
2008-05-20 13:19:33 -04:00
2013-09-24 20:18:11 -04:00
require_once ( ABSPATH . 'wp-admin/admin-header.php' );
2004-09-11 12:12:40 -04:00
?>
2005-09-05 19:33:10 -04:00
2013-11-20 14:44:12 -05:00
< div class = " wrap " >
2013-11-13 15:58:05 -05:00
< h2 >< ? php esc_html_e ( 'Themes' ); ?>
2014-08-25 11:58:15 -04:00
< span class = " title-count theme-count " >< ? php echo count ( $themes ); ?> </span>
2013-11-13 15:58:05 -05:00
< ? php if ( ! is_multisite () && current_user_can ( 'install_themes' ) ) : ?>
2014-10-18 16:11:18 -04:00
< a href = " <?php echo admin_url( 'theme-install.php' ); ?> " class = " hide-if-no-js add-new-h2 " >< ? php echo esc_html_x ( 'Add New' , 'Add new theme' ); ?> </a>
2013-11-13 15:58:05 -05:00
< ? php endif ; ?>
</ h2 >
2012-04-11 17:19:32 -04:00
< ? php
2012-06-12 14:39:16 -04:00
if ( ! validate_current_theme () || isset ( $_GET [ 'broken' ] ) ) : ?>
2015-04-01 18:06:28 -04:00
< div id = " message1 " class = " updated notice is-dismissible " >< p >< ? php _e ( 'The active theme is broken. Reverting to the default theme.' ); ?> </p></div>
2012-06-12 14:39:16 -04:00
< ? php elseif ( isset ( $_GET [ 'activated' ]) ) :
if ( isset ( $_GET [ 'previewed' ] ) ) { ?>
2015-04-01 18:06:28 -04:00
< div id = " message2 " class = " updated notice is-dismissible " >< p >< ? php printf ( __ ( 'Settings saved and theme activated. <a href="%s">Visit site</a>' ), home_url ( '/' ) ); ?> </p></div>
2012-09-24 12:31:41 -04:00
< ? php } else { ?>
2015-04-01 18:06:28 -04:00
< div id = " message2 " class = " updated notice is-dismissible " >< p >< ? php printf ( __ ( 'New theme activated. <a href="%s">Visit site</a>' ), home_url ( '/' ) ); ?> </p></div><?php
2012-06-12 14:39:16 -04:00
}
elseif ( isset ( $_GET [ 'deleted' ]) ) : ?>
2015-04-01 18:06:28 -04:00
< div id = " message3 " class = " updated notice is-dismissible " >< p >< ? php _e ( 'Theme deleted.' ) ?> </p></div>
2014-12-01 21:21:24 -05:00
< ? php elseif ( isset ( $_GET [ 'delete-active-child' ] ) ) : ?>
< div id = " message4 " class = " error " >< p >< ? php _e ( 'You cannot delete a theme while it has an active child theme.' ); ?> </p></div>
2012-06-12 14:39:16 -04:00
< ? php
endif ;
2012-04-11 17:19:32 -04:00
$ct = wp_get_theme ();
2013-10-02 16:50:09 -04:00
if ( $ct -> errors () && ( ! is_multisite () || current_user_can ( 'manage_network_themes' ) ) ) {
2014-03-26 19:37:25 -04:00
echo '<div class="error"><p>' . sprintf ( __ ( 'ERROR: %s' ), $ct -> errors () -> get_error_message () ) . '</p></div>' ;
2013-10-02 16:50:09 -04:00
}
2013-11-13 15:58:05 -05:00
/*
2013-10-02 16:50:09 -04:00
// Certain error codes are less fatal than others. We can still display theme information in most cases.
if ( ! $ct -> errors () || ( 1 == count ( $ct -> errors () -> get_error_codes () )
&& in_array ( $ct -> errors () -> get_error_code (), array ( 'theme_no_parent' , 'theme_parent_invalid' , 'theme_no_index' ) ) ) ) : ?>
2013-12-02 13:58:09 -05:00
*/
2013-10-02 16:50:09 -04:00
2010-09-22 13:23:38 -04:00
// Pretend you didn't see this.
2013-12-02 13:58:09 -05:00
$current_theme_actions = array ();
2010-09-22 13:23:38 -04:00
if ( is_array ( $submenu ) && isset ( $submenu [ 'themes.php' ] ) ) {
foreach ( ( array ) $submenu [ 'themes.php' ] as $item ) {
$class = '' ;
2014-07-29 12:02:16 -04:00
if ( 'themes.php' == $item [ 2 ] || 'theme-editor.php' == $item [ 2 ] || 0 === strpos ( $item [ 2 ], 'customize.php' ) )
2010-09-22 13:23:38 -04:00
continue ;
// 0 = name, 1 = capability, 2 = file
Introduce WP_Theme, wp_get_themes(), and wp_get_theme() to replace get_themes(), get_theme(), get_theme_data(), current_theme_info(), and others.
* Getters and Helpers: Introduces a series of methods to allow for easy generation of headers for display, and other theme metadata, including page templates.
* Screenshots: Handles support for multiple screenshots. (see # Additional screenshots must be PNG and start with screenshot-2.png, and be sequential to be counted. see #19816.
* Error Handling: Broken themes have a WP_Error object attached to them.
* Caching: Introduces a wp_cache_themes_persistently filter (also in [20020]) to enable persistent caching of all filesystem and sanitization operations normally handled by WP_Theme (and formerly get_file_data() and get_themes()). Themes are cached individually and across five different cache keys for different data pieces.
* Compatibility: A WP_Theme object is backwards compatible with a theme's array formerly returned by get_themes() and get_theme(), and an stdClass object formerly returned by current_theme_info().
* i18n/L10n: Theme headers are now localizable with proper Text Domain and Domain Path headers, like plugins. (Language packs may remove the requirement for headers.) For page templates, see #6007 (not fixed yet, but will be easy now). For headers, fixes #15858.
* PHP and CSS files: New methods that fetch a list of theme files (for the theme editor) only on demand, rather than only loading them into memory. fixes #11214.
Functions deprecated:
* get_themes(), get_allowed_themes() and get_broken_themes() -- use wp_get_themes()
* get_theme() and current_theme_info() -- use wp_get_theme()
* get_site_allowed_themes() -- use WP_Theme::get_allowed_on_network()
* wpmu_get_blog_allowedthemes() -- use WP_theme::get_allowed_on_site()
see also [20016], [20018], [20019], [20020], [20021], [20022], [20025], [20026], [20027]. also fixes #19244.
see #20103.
git-svn-id: http://svn.automattic.com/wordpress/trunk@20029 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2012-02-28 16:24:44 -05:00
if ( ( strcmp ( $self , $item [ 2 ]) == 0 && empty ( $parent_file )) || ( $parent_file && ( $item [ 2 ] == $parent_file )) )
2014-12-08 17:23:23 -05:00
$class = ' current' ;
2010-09-22 13:23:38 -04:00
if ( ! empty ( $submenu [ $item [ 2 ]]) ) {
2011-12-14 12:36:38 -05:00
$submenu [ $item [ 2 ]] = array_values ( $submenu [ $item [ 2 ]]); // Re-index.
2010-09-22 13:23:38 -04:00
$menu_hook = get_plugin_page_hook ( $submenu [ $item [ 2 ]][ 0 ][ 2 ], $item [ 2 ]);
2011-09-25 15:24:15 -04:00
if ( file_exists ( WP_PLUGIN_DIR . " / { $submenu [ $item [ 2 ]][ 0 ][ 2 ] } " ) || ! empty ( $menu_hook ))
2014-12-08 17:23:23 -05:00
$current_theme_actions [] = " <a class='button button-secondary $class ' href='admin.php?page= { $submenu [ $item [ 2 ]][ 0 ][ 2 ] } '> { $item [ 0 ] } </a> " ;
2010-09-22 13:23:38 -04:00
else
2014-12-08 17:23:23 -05:00
$current_theme_actions [] = " <a class='button button-secondary $class ' href=' { $submenu [ $item [ 2 ]][ 0 ][ 2 ] } '> { $item [ 0 ] } </a> " ;
} elseif ( ! empty ( $item [ 2 ] ) && current_user_can ( $item [ 1 ] ) ) {
2012-09-24 09:20:51 -04:00
$menu_file = $item [ 2 ];
2014-12-08 17:23:23 -05:00
if ( current_user_can ( 'customize' ) ) {
if ( 'custom-header' === $menu_file ) {
$current_theme_actions [] = " <a class='button button-secondary hide-if-no-customize $class ' href='customize.php?autofocus[control]=header_image'> { $item [ 0 ] } </a> " ;
} elseif ( 'custom-background' === $menu_file ) {
$current_theme_actions [] = " <a class='button button-secondary hide-if-no-customize $class ' href='customize.php?autofocus[control]=background_image'> { $item [ 0 ] } </a> " ;
}
}
if ( false !== ( $pos = strpos ( $menu_file , '?' ) ) ) {
2012-09-24 09:20:51 -04:00
$menu_file = substr ( $menu_file , 0 , $pos );
2014-12-08 17:23:23 -05:00
}
2012-09-24 09:20:51 -04:00
if ( file_exists ( ABSPATH . " wp-admin/ $menu_file " ) ) {
2014-12-08 17:23:23 -05:00
$current_theme_actions [] = " <a class='button button-secondary $class ' href=' { $item [ 2 ] } '> { $item [ 0 ] } </a> " ;
2010-09-22 13:23:38 -04:00
} else {
2014-12-09 06:27:22 -05:00
$current_theme_actions [] = " <a class='button button-secondary $class ' href='themes.php?page= { $item [ 2 ] } '> { $item [ 0 ] } </a> " ;
2010-09-22 13:23:38 -04:00
}
}
}
}
2013-12-02 13:58:09 -05:00
2010-05-12 15:19:57 -04:00
?>
2010-12-10 13:40:48 -05:00
2015-02-22 05:15:26 -05:00
< div class = " theme-browser " aria - live = " polite " >
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< div class = " themes " >
< ? php
/*
* This PHP is synchronized with the tmpl - theme template below !
*/
2014-01-22 16:00:11 -05:00
foreach ( $themes as $theme ) :
$aria_action = esc_attr ( $theme [ 'id' ] . '-action' );
$aria_name = esc_attr ( $theme [ 'id' ] . '-name' );
?>
< div class = " theme<?php if ( $theme['active'] ) echo ' active'; ?> " tabindex = " 0 " aria - describedby = " <?php echo $aria_action . ' ' . $aria_name ; ?> " >
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< ? php if ( ! empty ( $theme [ 'screenshot' ][ 0 ] ) ) { ?>
< div class = " theme-screenshot " >
< img src = " <?php echo $theme['screenshot'] [0]; ?> " alt = " " />
</ div >
< ? php } else { ?>
< div class = " theme-screenshot blank " ></ div >
< ? php } ?>
2014-01-22 16:00:11 -05:00
< span class = " more-details " id = " <?php echo $aria_action ; ?> " >< ? php _e ( 'Theme Details' ); ?> </span>
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< div class = " theme-author " >< ? php printf ( __ ( 'By %s' ), $theme [ 'author' ] ); ?> </div>
< ? php if ( $theme [ 'active' ] ) { ?>
2015-03-26 16:56:26 -04:00
< h3 class = " theme-name " id = " <?php echo $aria_name ; ?> " >
< ? php
/* translators: %s: theme name */
printf ( __ ( '<span>Active:</span> %s' ), $theme [ 'name' ] );
?>
</ h3 >
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< ? php } else { ?>
2014-01-22 16:00:11 -05:00
< h3 class = " theme-name " id = " <?php echo $aria_name ; ?> " >< ? php echo $theme [ 'name' ]; ?> </h3>
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< ? php } ?>
< div class = " theme-actions " >
< ? php if ( $theme [ 'active' ] ) { ?>
2014-07-14 15:01:16 -04:00
< ? php if ( $theme [ 'actions' ][ 'customize' ] && current_user_can ( 'edit_theme_options' ) && current_user_can ( 'customize' ) ) { ?>
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< a class = " button button-primary customize load-customize hide-if-no-customize " href = " <?php echo $theme['actions'] ['customize']; ?> " >< ? php _e ( 'Customize' ); ?> </a>
< ? php } ?>
< ? php } else { ?>
2014-10-18 14:17:20 -04:00
< a class = " button button-secondary activate " href = " <?php echo $theme['actions'] ['activate']; ?> " >< ? php _e ( 'Activate' ); ?> </a>
2014-07-14 15:01:16 -04:00
< ? php if ( current_user_can ( 'edit_theme_options' ) && current_user_can ( 'customize' ) ) { ?>
2014-10-18 14:17:20 -04:00
< a class = " button button-primary load-customize hide-if-no-customize " href = " <?php echo $theme['actions'] ['customize']; ?> " >< ? php _e ( 'Live Preview' ); ?> </a>
2014-07-14 15:01:16 -04:00
< a class = " button button-secondary hide-if-customize " href = " <?php echo $theme['actions'] ['preview']; ?> " >< ? php _e ( 'Preview' ); ?> </a>
< ? php } ?>
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< ? php } ?>
</ div >
< ? php if ( $theme [ 'hasUpdate' ] ) { ?>
< div class = " theme-update " >< ? php _e ( 'Update Available' ); ?> </div>
< ? php } ?>
</ div >
< ? php endforeach ; ?>
< br class = " clear " />
</ div >
2015-02-22 05:15:26 -05:00
< p class = " no-themes " >< ? php _e ( 'No themes found. Try a different search.' ); ?> </p>
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
</ div >
2013-12-06 22:11:10 -05:00
< div class = " theme-overlay " ></ div >
2013-11-28 21:40:09 -05:00
2004-10-24 19:48:51 -04:00
< ? php
// List broken themes, if any.
2012-03-08 02:32:42 -05:00
if ( ! is_multisite () && current_user_can ( 'edit_themes' ) && $broken_themes = wp_get_themes ( array ( 'errors' => true ) ) ) {
2004-10-24 19:48:51 -04:00
?>
2013-11-20 14:44:12 -05:00
< div class = " broken-themes " >
2011-01-14 21:17:42 -05:00
< h3 >< ? php _e ( 'Broken Themes' ); ?> </h3>
2010-06-03 09:37:51 -04:00
< p >< ? php _e ( 'The following themes are installed but incomplete. Themes must have a stylesheet and a template.' ); ?> </p>
2004-10-24 19:48:51 -04:00
2014-10-16 15:46:18 -04:00
< ? php
$can_delete = current_user_can ( 'delete_themes' );
?>
2013-11-20 14:44:12 -05:00
< table >
2004-10-24 19:48:51 -04:00
< tr >
2011-06-10 18:13:26 -04:00
< th >< ? php _ex ( 'Name' , 'theme name' ); ?> </th>
2004-10-24 19:48:51 -04:00
< th >< ? php _e ( 'Description' ); ?> </th>
2014-10-16 15:46:18 -04:00
< ? php if ( $can_delete ) { ?>
< th ></ th >
< ? php } ?>
</ tr >
2004-10-24 19:48:51 -04:00
</ tr >
2014-10-16 15:46:18 -04:00
< ? php foreach ( $broken_themes as $broken_theme ) : ?>
2013-10-02 16:50:09 -04:00
< tr >
2014-10-16 15:46:18 -04:00
< td >< ? php echo $broken_theme -> get ( 'Name' ) ? $broken_theme -> display ( 'Name' ) : $broken_theme -> get_stylesheet (); ?> </td>
< td >< ? php echo $broken_theme -> errors () -> get_error_message (); ?> </td>
< ? php
if ( $can_delete ) {
$stylesheet = $broken_theme -> get_stylesheet ();
$delete_url = add_query_arg ( array (
'action' => 'delete' ,
'stylesheet' => urlencode ( $stylesheet ),
), admin_url ( 'themes.php' ) );
$delete_url = wp_nonce_url ( $delete_url , 'delete-theme_' . $stylesheet );
?>
< td >< a href = " <?php echo esc_url( $delete_url ); ?> " class = " button button-secondary delete-theme " >< ? php _e ( 'Delete' ); ?> </a></td>
< ? php
}
?>
</ tr >
< ? php endforeach ; ?>
2004-10-24 19:48:51 -04:00
</ table >
2013-11-20 14:44:12 -05:00
</ div >
2004-10-24 19:48:51 -04:00
< ? php
}
?>
2013-11-13 15:58:05 -05:00
</ div ><!-- . wrap -->
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< ? php
/*
* The tmpl - theme template is synchronized with PHP above !
*/
?>
2013-11-13 15:58:05 -05:00
< script id = " tmpl-theme " type = " text/template " >
2013-11-28 23:04:11 -05:00
< # if ( data.screenshot[0] ) { #>
2013-12-01 13:00:09 -05:00
< div class = " theme-screenshot " >
< img src = " { { data.screenshot[0] }} " alt = " " />
</ div >
2013-11-28 23:04:11 -05:00
< # } else { #>
2013-11-29 12:17:11 -05:00
< div class = " theme-screenshot blank " ></ div >
2013-11-28 23:04:11 -05:00
< # } #>
2014-01-22 16:00:11 -05:00
< span class = " more-details " id = " { { data.id }}-action " >< ? php _e ( 'Theme Details' ); ?> </span>
2013-11-21 21:34:10 -05:00
< div class = " theme-author " >< ? php printf ( __ ( 'By %s' ), '{{{ data.author }}}' ); ?> </div>
2013-12-11 14:49:11 -05:00
2013-12-05 13:42:16 -05:00
< # if ( data.active ) { #>
2015-03-26 16:56:26 -04:00
< h3 class = " theme-name " id = " { { data.id }}-name " >
< ? php
/* translators: %s: theme name */
printf ( __ ( '<span>Active:</span> %s' ), '{{ data.name }}' );
?>
2015-03-27 19:20:27 -04:00
</ h3 >
2013-12-05 13:42:16 -05:00
< # } else { #>
2014-01-22 16:00:11 -05:00
< h3 class = " theme-name " id = " { { data.id }}-name " > {{{ data . name }}} </ h3 >
2013-12-05 13:42:16 -05:00
< # } #>
2013-11-29 04:01:09 -05:00
2013-11-13 15:58:05 -05:00
< div class = " theme-actions " >
< # if ( data.active ) { #>
2013-12-02 02:34:10 -05:00
< # if ( data.actions.customize ) { #>
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< a class = " button button-primary customize load-customize hide-if-no-customize " href = " { { data.actions.customize }} " >< ? php _e ( 'Customize' ); ?> </a>
2013-11-13 15:58:05 -05:00
< # } #>
< # } else { #>
2014-10-18 14:17:20 -04:00
< a class = " button button-secondary activate " href = " { { { data.actions.activate }}} " >< ? php _e ( 'Activate' ); ?> </a>
< a class = " button button-primary load-customize hide-if-no-customize " href = " { { { data.actions.customize }}} " >< ? php _e ( 'Live Preview' ); ?> </a>
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< a class = " button button-secondary hide-if-customize " href = " { { { data.actions.preview }}} " >< ? php _e ( 'Preview' ); ?> </a>
2013-11-13 15:58:05 -05:00
< # } #>
</ div >
< # if ( data.hasUpdate ) { #>
2013-12-02 03:38:10 -05:00
< div class = " theme-update " >< ? php _e ( 'Update Available' ); ?> </div>
2013-11-13 15:58:05 -05:00
< # } #>
</ script >
< script id = " tmpl-theme-single " type = " text/template " >
< div class = " theme-backdrop " ></ div >
< div class = " theme-wrap " >
2013-12-02 02:12:09 -05:00
< div class = " theme-header " >
2014-02-07 12:33:12 -05:00
< button class = " left dashicons dashicons-no " >< span class = " screen-reader-text " >< ? php _e ( 'Show previous theme' ); ?> </span></button>
< button class = " right dashicons dashicons-no " >< span class = " screen-reader-text " >< ? php _e ( 'Show next theme' ); ?> </span></button>
< button class = " close dashicons dashicons-no " >< span class = " screen-reader-text " >< ? php _e ( 'Close overlay' ); ?> </span></button>
2013-11-13 15:58:05 -05:00
</ div >
2013-12-02 02:14:10 -05:00
< div class = " theme-about " >
< div class = " theme-screenshots " >
< # if ( data.screenshot[0] ) { #>
2013-12-06 12:11:10 -05:00
< div class = " screenshot " >< img src = " { { data.screenshot[0] }} " alt = " " /></ div >
2013-12-02 02:14:10 -05:00
< # } else { #>
2013-12-06 12:11:10 -05:00
< div class = " screenshot blank " ></ div >
2013-11-13 15:58:05 -05:00
< # } #>
</ div >
2013-12-02 02:14:10 -05:00
< div class = " theme-info " >
< # if ( data.active ) { #>
< span class = " current-label " >< ? php _e ( 'Current Theme' ); ?> </span>
< # } #>
< h3 class = " theme-name " > {{{ data . name }}} < span class = " theme-version " >< ? php printf ( __ ( 'Version: %s' ), '{{{ data.version }}}' ); ?> </span></h3>
2013-12-05 14:08:10 -05:00
< h4 class = " theme-author " >< ? php printf ( __ ( 'By %s' ), '{{{ data.authorAndUri }}}' ); ?> </h4>
2013-12-02 13:58:09 -05:00
2013-12-02 02:14:10 -05:00
< # if ( data.hasUpdate ) { #>
< div class = " theme-update-message " >
2013-12-02 03:38:10 -05:00
< h4 class = " theme-update " >< ? php _e ( 'Update Available' ); ?> </h4>
{{{ data . update }}}
2013-12-02 02:14:10 -05:00
</ div >
< # } #>
< p class = " theme-description " > {{{ data . description }}} </ p >
2013-12-02 13:58:09 -05:00
2013-12-02 02:14:10 -05:00
< # if ( data.parent ) { #>
2013-12-02 02:20:09 -05:00
< p class = " parent-theme " >< ? php printf ( __ ( 'This is a child theme of %s.' ), '<strong>{{{ data.parent }}}</strong>' ); ?> </p>
2013-12-02 02:14:10 -05:00
< # } #>
2013-12-02 13:58:09 -05:00
2013-12-02 02:14:10 -05:00
< # if ( data.tags ) { #>
2013-12-06 09:37:10 -05:00
< p class = " theme-tags " >< span >< ? php _e ( 'Tags:' ); ?> </span> {{{ data.tags }}}</p>
2013-12-02 02:14:10 -05:00
< # } #>
</ div >
2013-11-13 15:58:05 -05:00
</ div >
2013-12-02 02:14:10 -05:00
< div class = " theme-actions " >
< div class = " active-theme " >
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< a href = " { { { data.actions.customize }}} " class = " button button-primary customize load-customize hide-if-no-customize " >< ? php _e ( 'Customize' ); ?> </a>
2013-12-02 13:58:09 -05:00
< ? php echo implode ( ' ' , $current_theme_actions ); ?>
2013-12-02 02:14:10 -05:00
</ div >
< div class = " inactive-theme " >
< # if ( data.actions.activate ) { #>
2014-10-18 14:17:20 -04:00
< a href = " { { { data.actions.activate }}} " class = " button button-secondary activate " >< ? php _e ( 'Activate' ); ?> </a>
2013-12-02 02:14:10 -05:00
< # } #>
2014-10-18 14:17:20 -04:00
< a href = " { { { data.actions.customize }}} " class = " button button-primary load-customize hide-if-no-customize " >< ? php _e ( 'Live Preview' ); ?> </a>
No-JavaScript and no-Customizer support for the new Themes screen.
JavaScript is rarely disabled, but graceful degradation is still important. For example, syntax errors can occur, usually with major WP updates that overhaul entire experiences and update external libraries combined with themes or plugins doing weird or old things. If this error is due to their current theme, a user needs to be able to access the themes screen to switch away from the theme. A more subtle issue could make things painful to diagnose.
This commit renders the grid in PHP (the template is duplicated, but it lightweight, fairly mundane, and easy to sync). On Backbone render, the grid is then re-rendered from JavaScript so searches can occur. Customize and Live Preview is disabled if JS fails to kick in. If JS is disabled, old-school "Preview" links are displayed.
No-Customizer support: The customizer is only supported when the browser supports postMessage (IE8+), and if the frontend is a different domain, CORS (IE10+). We use the .hide-if-no-customize class for this. Pre-customize "Preview" links should use .hide-if-customize.
The .load-customize class should be used to declare a link that opens the customizer. This enables customize-loader.js to intercept this link and load the customizer on top of the current window, making for a smoother experience.
fixes #25964.
Built from https://develop.svn.wordpress.org/trunk@26726
git-svn-id: http://core.svn.wordpress.org/trunk@26615 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2013-12-06 11:11:10 -05:00
< a href = " { { { data.actions.preview }}} " class = " button button-secondary hide-if-customize " >< ? php _e ( 'Preview' ); ?> </a>
2013-12-02 02:14:10 -05:00
</ div >
2013-12-02 13:58:09 -05:00
2013-12-11 17:49:09 -05:00
< # if ( ! data.active && data.actions['delete'] ) { #>
< a href = " { { { data.actions['delete'] }}} " class = " button button-secondary delete-theme " >< ? php _e ( 'Delete' ); ?> </a>
2013-11-29 04:01:09 -05:00
< # } #>
2013-11-13 15:58:05 -05:00
</ div >
2013-12-02 02:12:09 -05:00
</ div >
2013-11-13 15:58:05 -05:00
</ script >
2004-09-11 12:12:40 -04:00
2014-05-19 01:04:16 -04:00
< ? php require ( ABSPATH . 'wp-admin/admin-footer.php' );
