Looking at wp-includes/template-loader.php … there seems to be a way: if ( $template = apply_filters( ‘template_include’, $template ) ) include( $template ); You could hook into that filter, handle the including in a callback function and return FALSE. Sample code, not tested: add_filter( ‘template_include’, function( $template ) { get_header(); include $template; get_footer(); return FALSE; });
you can change lots of things about the tinyMCE editor at the tiny_mce_before_init filter. http://codex.wordpress.org/TinyMCE_Custom_Buttons the following will restrict your blockformats to p,h3,h4 and blockquote function wpa_45815($arr){ $arr[‘theme_advanced_blockformats’] = ‘p,h3,h4,blockquote’; return $arr; } add_filter(‘tiny_mce_before_init’, ‘wpa_45815’); EDIT for WordPress 3.9 see link function wpa_45815($arr){ $arr[‘block_formats’] = ‘Paragraph=p;Heading 3=h3;Heading 4=h4’; return $arr; } add_filter(‘tiny_mce_before_init’, ‘wpa_45815’);
See the source. It has some additional logic for IIS servers, as well as some hooks. It is also pluggable function, so it might be redefined. Overall it’s just more flexible and gives other developers more options to work with your code, unavailable if you just hardcode things.
found solution: before wp_head() command, insert: remove_action(‘wp_head’, ‘rel_canonical’); p.s. if generator meta tag is being added from elsewhere (i.e. from theme or plugin, rather than wp-core) and was priority other than 10, then you might need to put the exact priority, as is was given from that theme/plugin: i.e. remove_action(‘wp_head’, ‘rel_canonical’, 47);
You should enqueue the script in child theme’s functions.php. for example if name of the js file is custom.js and if you place it under js folder in your child theme, then in functions.php you should add function my_custom_scripts() { wp_enqueue_script( ‘custom-js’, get_stylesheet_directory_uri() . ‘/js/custom.js’, array( ‘jquery’ ),”,true ); } add_action( ‘wp_enqueue_scripts’, ‘my_custom_scripts’ ); Here … Read more
Milo is correct. For instance, go to your theme’s functions.php file, and add the following: add_filter( ‘allowed_http_origins’, ‘add_allowed_origins’ ); function add_allowed_origins( $origins ) { $origins[] = ‘https://site1.example.com’; $origins[] = ‘https://site2.example.com’; return $origins; } Now an ajax call from https://site1.example.com to your site’s ajax url will have the appropriate Access-Control-Allow-Origin header in the response. eg. $.ajax({ … Read more
The output is generated by the rest_output_link_header(). This function is used in two actions, wp_head and template_redirect in default-filters.php:@line234. You can remove the function from those hooks to remove the output you wanted to remove. Put the following codes in your theme’s functions.php to achieve the desired result. remove_action( ‘wp_head’, ‘rest_output_link_wp_head’, 10); remove_action( ‘template_redirect’, ‘rest_output_link_header’, … Read more
in your css you could try something like: body.logged-in{margin-top:20px;} or if this doesnt work some other code using the .logged-in class
Ok so I think I figured it out… Both of these work for the most part as you’d expect by sending http / php headers to the browser. wp_headers is actually a filter inside the send_headers() functions.You can use this to modify the headers before they’re sent to the browser with some exception. wp_headers won’t … Read more
You can either add custom rewrites to your pages. Or on the top of the template files that wrap your other pages just output header(‘HTTP/1.1 200 OK’);.