If your tests are correct the problem is with the data in $csv_data. Before saving something to the database WP runs a lot of filters. Some are standard, others may be added by plugins. So, most likely some piece of code thinks the content of $csv_data is not fit to be stored in the database. … Read more
Help with right recipe ierarchy post type and taxonomy
If your posts store the date in a consistent format like YYYY-MM-DD HH:MM:SS, etc, you could compare with strings using regular expressions, like: $current_date = new DateTime(); $datemonth = $current_date->format(“m-d”); // MM-DD $args = array( // … ‘meta_query’ => array( array( ‘key’ => ‘birthday’, ‘compare’ => ‘REGEXP’, // Regular expression explanation: // ^ – Start … Read more
The filter wp_title won’t pass $id to your function. Drop the parameter and instead retrieve it with get_queried_object_id(): function dw_listing_title( $title ) { if ( is_singular() && $id = get_queried_object_id() ) { // Modify $title as required } return $title; }
Yes it is, and to also sort by the post title, you would just need to add , {$wpdb->posts}.post_title <ASC or DESC> after the FIELD(), like so which results in a clause that looks like ORDER BY FIELD(wp_posts.post_type, <types>), wp_posts.post_title ASC: // Replace this: return $orderby = “FIELD( {$wpdb->posts}.post_type,” . $post_type__in_string . ‘ )’; // … Read more
The issue with your code appears to be related to the hook wp_after_insert_post being nested within the publish_service action. This setup can lead to the wp_after_insert_post action being added multiple times, which may cause the repeated creation of products. Here are a few steps to resolve this issue: Separate the Actions: Instead of nesting wp_after_insert_post … Read more
After thorough investigation, I identified the root cause of the issue. TL;DR: A bug in my JavaScript code was causing the post form to be submitted without the necessary publish parameter. Consequently, WordPress interpreted the request as an attempt to save a draft. I resolved the issue by updating the code to include the publish … Read more
You don’t need to use add_submenu_page() for custom post types and taxonomies, WordPress adds them to the menu automatically when you use the show_in_menu parameter.
So the problem was in the custom rest route which had the call to flush_rewrite_rules() which (as far as I can see) resetted the permalinks to default somehow and messed up the permalink structure. Once we removed all the calls to the custom route no 404 happened.
To pass the current post type to your AJAX request, you need to modify your JS to include the post type information in the AJAX request. You can achieve this by adding the post type as a parameter when calling the filterPosts() function JS import Alpine from ‘alpinejs’; Alpine.data(“filterPosts”, (adminURL, postType) => ({ posts: “”, … Read more