The stylesheet is registered and enqueued by a function called twentyfourteen_scripts() in the theme’s functions.php. Callbacks hooked into the style loader/dependency system will be echoed on the wp_head action in the wp_head() function. Which, by the way, is how you should be loading your own stylesheets. There is a similar system for scripts.
Upon successful login wp_signon() sets a cookie in the http response header. Hence it has to be called before any HTML output is sent to the browser. Otherwise the “headers already sent” error will occur. After a successfull login you should redirect your user. Otherwise the login information will not present when the page HTML … Read more
The error message you are seeing is normal for that operation. By the time the transition_post_status hook fires, the HTTP page headers is already sent. By simply echoing an error message inside a hook like transition_post_status which was never intended to echo any output to the browser, as you did, you are actually trying to … Read more
Look at the documentation for the_custom_logo(): Displays a custom logo, linked to home. So it’s doing what it’s supposed to. If you want to do anything other than that, you can get the ID of the logo image using get_theme_mod( ‘custom_logo’ ). Then you can do whatever you want to it, such as just outputting … Read more
Yes, you can hook determine_current_user. This is how WordPress calls the existing code that processes authentication cookies: add_filter( ‘determine_current_user’, ‘wp_validate_auth_cookie’ ); add_filter( ‘determine_current_user’, ‘wp_validate_logged_in_cookie’, 20 ); e.g. see the implementations of those in wp-includes/pluggable.php. Your filter should return the user ID of the user you want to authenticate as once you’ve processed the headers. That … Read more
Okay, here’s the answer: function CustomHead() { include(‘headcontent.php’); } add_action(‘wp_head’,’CustomHead’,1,1); The key is that first “1”, which sets the priority of it to run at the highest (this is an optional element, defaulting to 10, putting it at the end of the head by default). More info here: http://codex.wordpress.org/Function_Reference/add_action
While you can practically control order of hooked things by priority, it’s not always the right tool for the job. In case of styles you should be using appropriate wp_enqueue_style() function which allows you to easily set up elaborate dependencies which will be automagically processed by WP to produce desired order of styles output. Unfortunately … Read more
Headers are sent long before you try to alter them. Headers are sent by actions associated with get_header(), so by the time your code executes, it is too late to alter the headers. You can demonstrate this with a simple experiment. Try each of the following: get_header(); status_header( 404 ); and status_header( 404 ); get_header(); … Read more
Before I answer this question, I would believe that you have already created a child theme. Reason: You should never make any changes to a theme/plugin that you are not the author of. This includes core files With that sorted, the behavior of the navigation menu in purely controlled by js, 77 /* 78 * … Read more
There is no way do perform a redirect, if you already printed anything to the browser. (To make a redirect you have to send proper header to the browser. And headers have to be sent before any output.) So if you want to perform any redirects, you can’t (and shouldn’t) put such code directly in … Read more