If you are using the Settings API then you don’t have to save the options, that’s done for you. So when using an array to store the options your validation function should get an array of all existing options, update only the changed and return that array. Something like this: function my_settings_option_validate( $input ) { … Read more
I’d suggest not using $query_string to simplify things. If you’re using an array, stick with the array form for the query variables: global $wp; $paged = ((int)get_query_var(‘paged’)) ? (int)get_query_var(‘paged’) : 1; $s_array = array( ‘post_type’ => ‘blog’, ‘caller_get_posts’ => 1, ‘paged’ => $paged, ‘meta_query’ => array( array( ‘key’ => ‘votes_percent’, ‘value’ => ’50’, ‘compare’ => … Read more
Definite solution: Seeing as wp’s core get_post_custom function returns multiple data fields saved as a single key in a random order, I resolved the issue by writing a function to replace it – which has some added flexibility: /*————————————————————— Function: Retrieve post meta field for a post based on ID Usage: [admin/meta_box/downloads.php] = to replace … Read more
once you have set of result in particular order you can achieve it simply as below : – $pageposts=$wpdb->get_results(” SELECT * FROM $wpdb->posts WHERE post_type=”post” AND post_status=”publish” ORDER BY post_date DESC LIMIT 6 “, OBJECT); First time $i=1; foreach($pageposts as $pageposts_first){ //here goes your first post if($i==1) break; } For rest of posts $i=0; foreach($pageposts … Read more
Steve you’re doing it wrong. WordPress provides Settings API that should be used for settings pages. If you aren’t familiar with Settings API see great tutorial by Chip Bennett – Incorporating the Settings API in WordPress Themes.
I think you’re confusing old meta parameters with new meta_query parameters. meta_key should be just key and meta_value should be just value. Refer to WP_Query in Codex for correct syntax. Also, print_r( $country_query ); will show you the actual SQL query being sent to the database and will show you where you’re going wrong.
Quite simple. Instead of saving the post title, save the post ID, so in the front end you can extract all necessary info. Like so: get_post( $the_saved_ID_value ); or get_permalink( $the_saved_ID_value );. In you code, change this line: echo ‘<option value=”‘.get_the_ID().'” ‘.$is_selected.’>’.get_the_title().'</option>’; Notes: Using a WP_Query seems a bit too much, consider get_posts. Lots of … Read more
explode will be your best option. WordPress has a few built in functions to handle arrays of function arguments (wp_parse_args and shortcode_atts for example), but nothing relating to splitting a string and iterating the result. It’s not entierly clear to me what you are trying to achieve, but let’s say you were trying to get … Read more
That data is serialised PHP, if you pass in a PHP structure it will be serialised into a string. When you pull it back out, it’s de-serialised automatically, e.g.: $post_id = current post ID….. $data = get_post_meta( $post_id, ”, true ); To see the structure in a human readable form, use something like this: echo … Read more
There is no need to put them into an array. According to google’s documentation you should just separate out the various pieces of the address in the url like a standard (U.S.) formatted address. // Example taken from google’s docs: $state=”CA”; $street=”Mountain View”; $address=”1600 Amphitheatre Parkway”; function geocode_address($post_id) { $custom_fields = get_post_custom(); // just set … Read more