There is the in_admin_footer hook that’s right before the “Thank you for creating with WordPress.” text in the footer, you can check if you’re on a tag edit screen in that hook. function wpse_277416_admin_footer() { $screen = get_current_screen(); if ( $screen->id === ‘edit-post_tag’ ) { echo ‘Hello world!’; } } add_action( ‘in_admin_footer’, ‘wpse_277416_admin_footer’ ); That’s … Read more
The function will run, but nothing will happen. There is a small overhead, but you shouldn’t worry about it, the possible savings are minimal. Depending on when you have $checked available, you could also do function example() { echo ‘true’; } if ($checked) add_action(‘wp_head’, ‘example’);
You could use the wp_mail function https://developer.wordpress.org/reference/functions/wp_mail/ to send an email to anyone after the file is successfully uploaded in your directory. You do not need any action here Add it your code after the file is uploaded successfully if(empty($errors)==true){ move_uploaded_file($file_tmp,”/$user_dirname/”.$document); echo “The file was uploaded successfully!”; wp_mail(..); }else{ print_r($errors); } }
You can create a custom template and assign that to both your homepage as well as that specific post. Templates are normally for the page post type, but you can add * Template Post Type: post, page to the comment at the top of the template file to make this available for posts as well. … Read more
You’re looking for the save_post action. This allows you to add a function when a post is saved (updated). You can hook into it like this: function your_save_post_function( $post_id ) { } add_action( ‘save_post’, ‘your_save_post_function’ ); Remember to not change WordPress Core files, as these will be overwritten when WordPress is updated. You can put … Read more
As Milo hints at in their comment, custom post types can only be registered on the init hook. Therefore, if you are trying to get all the public but not builtin post types before init, then get_post_types() will return an empty array. (You can use get_post_types() to get the builtin post types before init.) What … Read more
Post type is reflected in body as class. It is .post-type-post for posts, .post-type-product for WooCommerce products and must be .post-type-food in your case. So, you can use css rule like that to detect certain post type: body.post-type-food #titlediv input { background: yellow !important; } Post status is reflected only in TinyMCE editor classes, as … Read more
The init and plugins_loaded hooks are already run before a plugin is activated. That’s why your first code doesn’t work but the second does. Regarding your third code: there’s no need to run add_action(‘myplugin_activate’ … inside init. Not everything needs to be hooked to init. Just use add_action(‘myplugin_activate’, function(){ echo ‘myplugin is not allowed.’; die; … Read more
I belive this will work for you: Create a “page” called “stuff”, then create another page called “foo”, make it child of “stuff”, now stuff/foo will exist and won’t be 404. Finally use the_content filter and make the required data manipulation. The other choice (hard way) you’d have is to use pre_get_post hook, so you … Read more
There is no difference between 1 and 2. Both are same in every single case. So, I’ll consider 1 and 2 as A and 3 as B. Now in A the add_action() callback function is a named function whereas in B the callback function is an anonymous function and this is the main difference. I … Read more