wp_loaded is called long, long before the post content is fetched. Put that code into a plugin. Also, you shouldn’t echo anything that early. The HTTP headers aren’t sent yet on wp_loaded, so you will get the Headers already sent error, and your user authentication will not work: you cannot log in anymore.
Technically, you can’t. That filter doesn’t pass in any data that will specifically allow you to distinguish between those two cases. 2086 /** 2087 * Fires immediately after an existing user is updated. 2088 * 2089 * @since 2.0.0 2090 * 2091 * @param int $user_id User ID. 2092 * @param object $old_user_data Object containing … Read more
Hooks/actions are better thought of as events. When you run this code: add_action( ‘post_footer’, ‘toms_footer_stuff’ ); You’re saying that when the post_footer event happens, run the toms_footer_stuff function. These functions take the form of: add_action( name_of_action, php_callable ); A PHP callable is something that can be called represented as an object. It can be any … Read more
I think there are two decent options here. Let WordPress keep its mail function, but hook in once or twice wp_mail() has several hooks that will be helpful for you to replace the built in behavior, which is basically to use php’s simple little mailer. Here are a couple of those helpful hooks that I … Read more
There’s a filter called login_redirect. add_filter( ‘login_redirect’, ‘wpse377295_login_redirect’, 10, 3 ); function wpse377295_login_redirect( $url, $request, $user ) { if ( is_wp_error( $user ) ) { // It’s possible that the $user param is a WP_Error. If so, bail out. return $url; } if ( ! user_can( $user, ‘update_core’ ) { // Only admin users can … Read more
You’ve misunderstood how hooks, and PHP, work. Hooks are not persistent. Each time you visit a page in WordPress the PHP scripts that comprise WordPress all get run. Every time. This includes plugins and the theme’s the functions.php file. So when you run add_action() that queues up a callback function to run whenever the corresponding … Read more
Enqueue mechanics and suggested ways to use them serve flexibility and interoperability. Simply put consider what would be the easiest way for third party code to modify mechanics of yours? Hardcoding things in template often makes editing that template the only viable option. Manipulating hooks is typically more convenient and less problematic than that. On … Read more
Don’t remove wp_head() or wp_footer() as they are required for triggering other hooks. Instead, conditionally remove scripts / stylesheets based on page type, page ID, page template, post category, etc. I reckon you mostly need to worry about this on the site’s front page, since all your site CSS and main JavaScript will be loaded … Read more
create_term as you can see in inline docs in code Fires immediately after a new term is created, before the term cache is cleaned So you can’t prevent an event after that event already happen. To prevent a term is inserted you can use ‘pre_insert_term’ filter hook and return a WP_Error a 0 or an … Read more
Im not entirely sure there is such action hook for custom forms (someone else might know) but there are definately other ways if form is submitted normally, without ajax. Let me know if you have any questions. //This applies if you want it to happen only if form is submited and page refreshed //It doesn’t … Read more