Each post meta key can have multiple values. So you get the values by default as an array; the first entry (0) is the oldest. get_post_custom() fetches all meta keys with their values. You could simplify your code with: $price = get_post_meta( $post->ID, ‘price’, TRUE ); $comake = get_post_meta( $post->ID, ‘coMake’, TRUE ); When the … Read more
As stated in @ambroseya’s answer, its supposed to work like that. Once you declare a meta query, even if you aren’t looking for a specific value, it will only query posts with that meta key declared. If you want to include all posts sort them by the meta key, use the following code: $args = … Read more
@s_ha_dum suggests that Post meta will be deleted automatically. Therefore because his reputation suggests he knows what he is talking about, this solution only handles Post attachments. I’d suggest checking out the docs for the before_delete_post() hook, as it’s quite handy to be able to check out what Post Type is being deleted, etc. add_action(‘before_delete_post’, … Read more
This should do it. The default relation is AND so that won’t need to be specified. $args = array( ‘post_type’ => ‘wpse_cpt’, ‘meta_query’ => array( array( ‘key’ => ‘post_code’, ‘value’ => ‘432C’, ), array( ‘key’ => ‘location’, ‘value’ => ‘XYZ’, ), ), ); $query = new WP_Query( $args );
Here’s one experimental idea: Assume we got: post A with the custom field location1 as UK – London post B with the custom field location2 as France – Paris post C with the custom field location3 as USA – New York Then we could use, for example: $args = [ ‘meta_query’ => [ ‘relation’ => … Read more
The underscore prefix are private, these meta fields will be hidden and will not be shown as custom fields in the post backend screens. Those meta fields without the underscore prefix are public fields and shows up as custom fields in the post screens
Unfortunately you cannot perform a meta_query using a LIKE comparison on the meta_key value when using WP_Query. I’ve been down this road… Instead you have a couple other options if you want to maintain like status relationships as post meta and not user meta and or meta in a custom table. Option 1 requires no … Read more
$post in the callback function is an array, not an object. So you cannot use $post->id. Change it to $post[‘id’] and it should work: function slug_get_phone_number($post, $field_name, $request) { return get_post_meta($post[‘id’], ‘_phone’, true); } I recommend to change _phone to phone_number or something else without underscore prefix. Because _ is often used with private meta … Read more
This would need a query. So building on your code: <?php $postTitle = $_POST[‘post_title’]; $submit = $_POST[‘submit’]; if(isset($submit)){ global $user_ID, $wpdb; $query = $wpdb->prepare( ‘SELECT ID FROM ‘ . $wpdb->posts . ‘ WHERE post_title = %s AND post_type = \’stuff\”, $postTitle ); $wpdb->query( $query ); if ( $wpdb->num_rows ) { $post_id = $wpdb->get_var( $query ); … Read more
To answer this, I have gone and done some tests on this, and the results was actually mind blowing. Here is my test To this yourself, set yourself up with a test page. Just simply copy page.php, rename it and delete the loop. Now just create a new page in the back end. Before you … Read more