Whenever you use the function get_post_meta(), the above query will be performed to get all post meta and store in the cache. The more posts you query, the more queries are made. To reduce the number of queries, we should pre-cache all meta values of all posts in the query before calling get_post_meta. This is … Read more
On the initial issues, are you positive the plugin is registering the fields to be made available to the api? the register_meta needs show_in_rest => true assigned. Also, the CPT needs custom-fields in its supports array, ‘supports’ => array(‘title’,’editor’,’thumbnail’,’custom-fields’) for that to made available when accessing the CPTs api endpoint. I cover that (with links, … Read more
I am just incredible stupid here as this can be easily done by a simple WP_Query: new WP_Query( array( ‘post_type’ => ‘shop_order’, ‘meta_key’ => $meta_key, ‘meta_value’ => $meta_value ) ) However, I decided to compare the actual generated SQL of the get_posts() with a ‘post_where’ filter solution which is: SELECT wp_posts.ID FROM wp_posts WHERE 1=1 … Read more
Add the following code in the functions.php for acf function get_all_meta($type){ global $wpdb; $result = $wpdb->get_results($wpdb->prepare( “SELECT post_id,meta_key,meta_value FROM wp_posts,wp_postmeta WHERE post_type = %s AND wp_posts.ID = wp_postmeta.post_id”, $type ), ARRAY_A); return $result; } function acf(){ $options = array(); $acf = get_all_meta(‘acf’); foreach($acf as $key => $value){ $options[‘post_type’][$value[‘post_id’]][‘post_id’] = $value[‘post_id’]; $test = substr($value[‘meta_key’], 0, 6); … Read more
It seems that the action save_post gets fired when sending a post to the trash… Therefore, my custom metadata save function was being activated with no $_POST data to send thru it. To circumvent this, I wound up adding a nonce to the save function. function wpg_testimonial_author() { global $post; $custom = get_post_custom($post->ID); $testimonial_author_name = … Read more
The sticky posts are saved as an array of post IDs in the wp_options table. Hence, $stickies = get_option( ‘sticky_posts’ ); $stickies[] = $post_id; update_option( ‘sticky_posts’, $stickies ); will make the post in question sticky. EDIT: Even better, the core provides functions to stick and unstick posts (had to have ’em). stick_post( $post_id ); unstick_post( … Read more
You JOIN two elements both with the same table. When you need to join one table more than once, you need to make each join unique by giving the table alias. When WP makes the whole query, it takes that into account, but you have added your own code that doesn’t do that. So, first … Read more
The way your code is setup is just wrong, you are making two database calls for each custom field and if you have between 2-30 fields like this then that means you make over 60 calls to the database which can be done with a single call using get_post_custom() for ex: $custom_fields = get_post_custom($post->ID); for … Read more
A standard WordPress schema “sync” via dbDelta() will only add indexes, not drop them. Same goes for fields. We never touch the storage schema either, so it’d be the default for MySQL (which in latest versions is now InnoDB). On the face, a comment_id_meta_key index makes perfect sense. But when you look at how WordPress … Read more
The problem is that the function update_field from ACF works a little bit different from update_post_meta. Can you see it? update_post_meta( $post_id, $meta_key, $meta_value, $prev_value ); update_field( $field_key, $value, $post_id ); If you use update_post_meta you should in my opinion use get_post_meta to get the meta. If you use update_field you should use the_field or … Read more