Meta queries are essentially wrapper for ease of setup, but end results is part of SQL query to run on MySQL database. These operators are those of MySQL, see in documentation: LIKE operator (performs pattern matching) IN() function (checks if value is in set)
function add_meta_boxes() { add_meta_box( ‘repeatable-fields’, ‘Audio Playlist’, ‘repeatable_meta_box_display’, ‘post’, ‘normal’, ‘high’); add_meta_box( ‘wpa-45985’, ‘Wordpress Answers Metabox’, ‘wpa_meta_box_display’, ‘post’, ‘normal’, ‘high’); } add_action(‘admin_menu’, ‘add_meta_boxes’); just define a 2nd metabox, then define its display function and save function. it is exactly the same. EXCEPT, that if you want to save it as a different meta entry then … Read more
The function below will store a distinct list of all custom fields for the list of posts/pages/custom posts that is passed to it in the keys of the array $customfields. The array values are the number of posts with the corresponding field. In the example, custom fields added by plugins are excluded ($value[0] != ‘_’;) … Read more
Custom post meta data are generally updated in the database via a callback function hooked into save_post. (Others: draft_post, publish_post, future_post.) The custom post meta data are part of the $_POST data sent on-submit for the edit post screen, so simply look for them there, sanitize them, and then update them in the database. I’m … Read more
Here is how I’ve done it. No changes to the save function are needed. I’ve been trying to save data from both fields at once, thats why it didn’t worked. <input class=”upload_file” type=”text” size=”45″ id=”picture_%1$s” name=”picture_%1$s” value=”%6$s” /> <input class=”upload_button button” type=”button” value=”Upload File” /> <input class=”upload_file_id” type=”hidden” id=”picture_%1$s_id” name=”items[%1$s][picture]” value=”%7$s” /> The value stored … Read more
You are going to have to JOIN twice on the postmeta table. Something like: SELECT $wpdb->posts.ID, $wpdb->posts.post_title, $wpdb->terms.name, wpcflat.meta_value AS latitude, wpcflong.meta_value AS longitude FROM $wpdb->posts /* First Join */ LEFT JOIN $wpdb->postmeta as wpcflong ON $wpdb->posts.ID = wpcflong.post_id /* Second Join */ LEFT JOIN $wpdb->postmeta as wpcflat ON $wpdb->posts.ID = wpcflat.post_id LEFT JOIN $wpdb->term_relationships … Read more
Retrieving and Listing posts based on current posts metadata Assuming that the custom field is saved as postmeta: global $post; // current post displayed /* grab the value of the custom field for the current post */ $custom_field_value = get_post_meta( $post->ID, ‘custom-field-name’, true ); /* fetch all posts with the same value for the custom … Read more
The way you have built that query it is possible for you to have a bunch of empty values. For example, if grad is not present then you end up searching ex_lokacija keys for empty strings. Since your main relation is AND all of the terms have to ‘hit’ so it seems likely to me … Read more
You can use one save function. wp_nonce_field function creates hidden field with action. You can use wp_nonce_field for two metaboxes if you want different actions for two metaboxes. Please go throgh below link for more information http://codex.wordpress.org/Function_Reference/wp_nonce_field
Resolved by following comment on Tutsplus Tutorial (link included): In function save_meta(), replace this line: if (!wp_verify_nonce($_POST[‘custom_meta_box_nonce’], basename(__FILE__))) with this line: if (!isset($_POST[‘custom_meta_box_nonce’]) || !wp_verify_nonce($_POST[‘custom_meta_box_nonce’], basename(__FILE__))) See full comment here.