As @cybmeta already pointed out, you are too early with your removal. So you have to defer the actual removal, for instance like so: add_action( ‘after_setup_theme’, ‘wpdev_170663_remove_parent_theme_stuff’, 0 ); function wpdev_170663_remove_parent_theme_stuff() { remove_action( ‘after_setup_theme’, ‘et_pb_setup_theme’ ); }
muplugins_loaded is the earliest hook. Depending on your wordpress setup, you may not have any plugins in the MU_PLUGINS directory. In that case this hook may not fire. The next best hook to trigger is plugins_loaded. RESOURCES WordPress Codex – Action Reference List Q/A: How to get WordPress’ hook run sequence? Q/A: Make sense of … Read more
You can use the remove_action() function, like this: remove_action(‘publish_post’, ‘old_action’); add_action(‘publish_post’, ‘new_action’); It’s important to note that if the old_action was added with a priority parameter, you must add that to the remove_action call, otherwise it will fail to remove it. There are other implications if the old_action was added within a class. See here … Read more
Try to see the function with better names: apply_filters( $filter_name, // used for add_filter( $filter_name, ‘callback’ ); $value_to_change, // the only variable whose value you can change $context_1, // context $context_2 // more context ); So when that function is called as: // wp-login.php line 94 apply_filters( ‘login_body_class’, $classes, $action ); You can use … … Read more
The API you offer in a plugin or a theme depends on the logic of that specific code. There is probably no guide that applies to all situations. I am a contributor for multiple plugins with APIs, and what I have learned so far is: Do not offer an API until you really know how … Read more
Use do_action( ‘unique_name’ ) to create your own actions. You can use that to offer an API for your plugin, so other plugins can register callbacks for your custom action. Example: Do I need to call do_action in my plugin? But you can use custom actions (or filters) in a theme too. Example: Best practice … Read more
It is easier to read: When is what called? If you are debugging a hook you can immediately see if you have to read the function or not: If it is not your hook, you can skip the code. In my themes and plugins I combine all registrations for actions, filters and shortcodes at the … Read more
The wp_insert_post_data filter can do that: add_filter( ‘wp_insert_post_data’ , ‘filter_post_data’ , ’99’, 2 ); function filter_post_data( $data , $postarr ) { // Change post title $data[‘post_title’] .= ‘_suffix’; return $data; }
You can do it like this (put in your functions.php) : function add_admin_scripts( $hook ) { global $post; if ( $hook == ‘post-new.php’ || $hook == ‘post.php’ ) { if ( ‘recipes’ === $post->post_type ) { wp_enqueue_script( ‘myscript’, get_stylesheet_directory_uri().’/js/myscript.js’ ); } } } add_action( ‘admin_enqueue_scripts’, ‘add_admin_scripts’, 10, 1 );
My favorite plugin for that is Core Control which has very nice module for display of what is going in the cron – which events are set up, when are they next firing, etc. On getting your hands dirty level see _get_cron_array(), which returns internal stored data for cron events (top level of keys are … Read more