This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
/** | |
* A dropdown taxonomy terms `<select>` customizer control class. | |
* | |
* @package Hybrid | |
* @subpackage Classes | |
* @author Justin Tadlock <[email protected]> | |
* @copyright Copyright (c) 2008 - 2015, Justin Tadlock | |
* @link http://themehybrid.com/hybrid-core | |
* @license http://www.gnu.org/licenses/old-licenses/gpl-2.0.html |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
add_action( 'customize_register', 'my_customize_register' ); | |
function my_customize_register( $wp_customize ) { | |
$wp_customize->add_setting( | |
'color_xyz', | |
array( | |
'default' => '', |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
class Hybrid_Customize_Control_Select extends WP_Customize_Control { | |
public $type = 'select-custom'; | |
public function to_json() { | |
parent::to_json(); | |
$this->json['choices'] = $this->choices; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
/** | |
* The template for displaying home page. | |
* | |
* This is the template that displays all pages by default. | |
* Please note that this is the WordPress construct of pages | |
* and that other 'pages' on your WordPress site will use a | |
* different template. | |
* | |
* @package SKT Bakery |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
add_action( 'wp_enqueue_scripts', 'jt_enqueue_scripts' ); | |
function jt_enqueue_scripts() { | |
wp_enqueue_script( 'wp-api' ); | |
wp_enqueue_script( 'wp-util' ); | |
} | |
add_action( 'wp_footer', 'jt_print_post_template', 25 ); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
/** | |
* @package ThemeName | |
* @version 0.1.0 | |
* @author Your Name <[email protected]> | |
* @copyright Copyright (c) 2013, Your Name | |
* @link http://yoursite.com/themes/theme-slug | |
* @license http://www.gnu.org/licenses/old-licenses/gpl-2.0.html | |
*/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
/** | |
* Functions for handling font enqueueing, registration, etc. This works with the | |
* Google Fonts API. | |
* | |
* Extending an idea from Jose Castaneda. This is a small script for loading Google fonts | |
* with an easy method for adding/removing/editing the fonts loaded via child theme. | |
* | |
* @link http://blog.josemcastaneda.com/2016/02/29/adding-removing-fonts-from-a-theme/ | |
*/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
/** | |
* Helper Functions | |
* | |
* @package EDDMembers\Functions | |
* @since 1.0.0 | |
*/ | |
// Exit if accessed directly | |
if( !defined( 'ABSPATH' ) ) { |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
/** | |
* The purpose of this file is to show how a theme can have multiple textdomains | |
* and still work with a single translation file. Translation tools like the | |
* one used on WordPress.org and Poedit are going to simply scan the project for | |
* text strings, regardless of the textdomain (and for good reasons that are | |
* not relevant here). | |
* | |
* The code below works with that system. It assumes that we have a single MO | |
* file based on the theme's textdomain. So, how can two textdomains work? It |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
// Font Awesome v. 4.6. | |
function jt_get_font_icons() { | |
return array( | |
'fa-glass' => 'f000', | |
'fa-music' => 'f001', | |
'fa-search' => 'f002', | |
'fa-envelope-o' => 'f003', |