There sure is, I talk about some of those options in this Q&A here: Is there a flowchart for wordpress loading sequence? Here is a very brief summary of what was said, Want to see what actions get fired during a request? Take a look at this plugin by Toscho Want to see what’s hooked … Read more
The short answer is ‘yes’. Taken from this article the suffix of those ‘screen specific hooks’ is given by: For custom admin pages added via add_menu_page() – including settings pages – (and related functions) it is the screen ID (the value returned by add_menu_page()) For the admin page listing posts of any post type, it … Read more
The second parameter in add_filter is a function with accepted arguments, not returned values. This is an example how I pass my custom array $args to change an existing array $filter_args: add_filter( ‘woocommerce_dropdown_variation_attribute_options_args’, function( $filter_args ) use ( $args ) { return eswc_var_dropdown_args( $filter_args, $args ); } ); function eswc_var_dropdown_args( $filter_args, $args ) { $filter_args[‘show_option_none’] … Read more
On a parallel thread over on the WordPress hacks forum, someone suggested using in_the_loop() and that works some of the time, with some plugins that use either the_content and/or the_excerpt, but not all of the time with all the plugins I’ve been testing against. Likewise, I’ve now done further testing using is_main_query() and that works … Read more
PHP has a function, get_included_files(), that returns all the files that have been included during a request. However, if you use that function you obtain all the files required: WordPress core files, plugin files… You need a way to: Filter out files that do not belong to the theme and child theme (if any) Include … Read more
Ok, so it turns out that by default, $depth in the end_lvl() function starts at 0 when it’s a submenu and increments as the depth gets greater. So we need to test if {$depth} is equal to 0 to apply it only to the first set of submenus: function end_lvl( &$output, $depth, $args ) { … Read more
The hook is not the problem – your code runs in the context of the current site, not the one just created! The following code isn’t tested, but it should at least highlight the problem: function wpse_71863_default_pages( $new_site ) { $default_pages = array( ‘Impress’, ‘Contact’, ); switch_to_blog( $new_site->id ); if ( $current_pages = get_pages() ) … Read more
Personally I’d use a different approach, because @Shazzad‘s solution seems too much global dependent, and @s_ha_dum‘s needs 2 hooks instead of one. I’d use get_current_screen function to get a WP_Screen object, then I’d look at its property to run (or not) something after the title: function do_something_after_title() { $scr = get_current_screen(); if ( ( $scr->base … Read more
Surely this approach has some benefits, but has also some issues. It’s not really easy to use If the target of your plugin are WordPress developers, they will be very familiar with plugin API, but end users are not. For a non-developer, something like: $data = give_me_the_data(); It’s easier to understand, remember and type than: … Read more
In a WordPress footer hooks are different for back-end(dashboard) and front-end. In Dashboard use “admin_footer” hook. In Front-end use “wp_footer” hook.