WP_Query provides no such date parameter. While you could query for/store the date of the earliest post on the site and then calculate every date for a particular day of the week in the timespan since then and query based on that criteria, it would be far more efficient to track the publish day of … Read more
From the documentation: https://developer.wordpress.org/reference/hooks/init/ add_action( ‘init’, ‘process_post’ ); function process_post() { if( isset( $_POST[‘unique_hidden_field’] ) ) { // process $_POST data here } } In your example, perhaps having two different add_action is causing problems and burying your function where it’s not firing during init I’m going to test a similar solution and see what … Read more
The problem is probably that the $post_id parameter passed to via the save_post_$post_type hook is not the same $post_id as the original post – it’s the $post_id of the temporary post that’s created when you edit a post. To confirm this: add_filter( ‘pre_post_update’, ‘wpse_pre_post_update’, 10, 3 ); add_filter( ‘save_post’, ‘wpse_save_post’, 10, 1 ); function wpse_pre_post_update( … 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
Searching around and not being able to implement the action through init hook I’ve found this workaround which for sure isn’t the best but does the job nicely. echo “<script type=”text/javascript”> window.location=document.location.href; </script>”; at the end of $_POST instructions. If somebody has a better solution, welcome to share.
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
add_filter( ‘the_title’, ‘YearOfMake’, 10, 2 ); function YearOfMake( $title, $post_id ) { if ( get_post_type( $post_id ) != ‘product’ && ! is_archive() ) return $title; if ( ! ( is_shop() || is_product_category() || is_product_tag() ) ) return $title; /* global $product; $attribute=”year-made”; $abv = $product->get_attribute($attribute); if(!empty($abv)) { $title .= ‘<br /><p>’ . $abv . ‘</p>’; … Read more
Well let’s compare the hook to one that is working: add_action( ‘admin_init’, array( $this, ‘page_init’ ) ); add_action( ‘publish_pelicula’, ‘post_published_notification’, 10, 2 ); page_init() and post_published_notification() are both methods of the MySettingsPage class, but you’ve set the action callbacks for each of them differently. The second argument for add_action() is a callback. It tells WordPress/PHP … Read more
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