Yes, that’s what the WP Cron system does. It will fire an action/hook as close to a requested time as it can, and can do it once or multiple times. You would still have a hook that runs on profile_update but it wouldn’t send data to google spreadsheets, rather it would schedule a cron job … Read more
If you have access to the database, you could potentially create a trigger for that plugin-specific table. This bypasses the need for a hook. Depending on how they handle database schema updates, it might even stick around after a plugin update. I’ve never tried triggers on WP tables though, so take this with a grain … Read more
In order to remove the hooks and filters, we need to be able to get a reference to the callable that was added, but in this case, create_function was used, so that’s extremely difficult. It’s also the reason you’re getting deprecation notices. Sadly the only way to fix those deprecations is to change the parent … Read more
You get 500 error, because you’ve added your filter incorrectly… It takes 4 params, but you register it as it was using only one. add_action(‘delete_product_cat’, ‘sync_cat_delete’, 10, 1); // 10 is priority, 1 is number of params to take function sync_cat_delete($term, $tt_id, $deleted_term, $object_ids){ var_dump($deleted_term); } So if you change that 1 to 4, it … Read more
I don’t think that disabling admin-post.php is a good idea. Such solution may break WP, some plugins and themes. But there is another, much simpler solution. Just add your action for admin_post (without nopriv) and process it properly – so if it’s a login action and user is already logged in, redirect him to proper … Read more
When you add an action via add_action(), the variables that are available in the callback function are determined by the specific hook you’re using. The load-post.php hook does not pass any values through to the callback function. However, when adding meta boxes the correct hook to use is add_meta_boxes, and that hook provides 2 values … Read more
I think the hooks you’re looking for are going to be either woocommerce_review_order_after_shipping or woocommerce_review_order_before_order_total. If you need to get in between where those two put you then you’re looking at modifying a template, which isn’t as future proof but is still a viable option when the hooks aren’t enough.
The appropriate hook for handling redirects would be template_redirect: function wpse_331804_redirects() { /** * 1. Check if the URL has a parameter [redirect] * 2. If NO, proceed to the next step * 3. If YES, then get that parameter value and look into [redirects] table * 4. If you found a row that has … Read more
The ajax action that runs on theme or plugin update is edit-theme-plugin-file so you should be able to hook into it by running code on the wp_ajax_edit-theme-plugin-file hook. add_action(‘wp_ajax_edit-theme-plugin-file’, ‘log_cowboy_coders’); function log_cowboy_coders() { $user = get_current_user_id(); if (!empty($__POST[‘theme’])) { // Log that someone is editing a theme } else if (!empty($__POST[‘plugin’])) { //log that someone … Read more
Actually, I noticed that your closure is not capturing/using the proper $template variable which is passed from the template_include filter hook: // This hook is defined in wp-includes/template-loader.php $template = apply_filters( ‘template_include’, $template ) The closure is also not returning the template.. So your closure should look like: add_filter( ‘template_include’, function( $template ) use ( … Read more