You are talking about “Options”. These are saved in the *_options table and can be stored and retrieved using a number of Core functions (straight from the Codex page above): Add/Delete Option add_option() delete_option() add_site_option() delete_site_option() Get/Update Option get_option() update_option() get_site_option() update_site_option()
Define your own template tag One idea is to use the template tag: <?php the_price();?> or <?php the_price( ‘%.1f’ );?> to change the format to your needs. Then you can add filters to it as you like. In your functions.php file you could add // setup the price filters: add_filter( ‘the_price’ , ‘xyz_add_product_price’, 1, 1 … Read more
I noticed that your are using get_the_content(), but it will return unfiltered content. The shortcodes are generated via the the_content filter with priority 11. So if you want only the shortcodes generated, try: ‘content’ => do_shortcode( get_the_content() ) to filter it through the_content filter, try: ‘content’ => apply_filters( ‘the_content’, get_the_content() ) to simulate the_content() function, … Read more
I am guessing but based on your choice of placeholder names in the code above… $args = array( ‘meta_key’ => ‘myvalue’, ‘orderby’ => ‘meta_value_num’, ‘order’ => ‘DESC’ ); … your meta_key argument is wrong. That is the meta key not the meta value as your naming convention suggests. meta_key (string) – Custom field key. http://codex.wordpress.org/Class_Reference/WP_Query#Custom_Field_Parameters … Read more
get_post_custom() will return an array of arrays. You need: echo $custom_array[‘my_custom_field’][0]; Alternatively, you can use get_post_meta() with the $single flag as true: echo get_post_meta( get_the_ID(), ‘my_custom_field’, true );
<?php // get an array of multiple values $post_meta_array = get_post_meta($post->ID, ‘link’); // do not use ‘true’ as the third argument // echo the link for each value foreach ($post_meta_array as $post_meta) { echo ‘<a href=”‘ . $post_meta . ‘” target=”_blank”>Images Source</a>’; }
Here are few ideas: 1) You could try to compare with LIKE instead: ‘key’ => ‘_my_custom_field_key’, ‘value’ => ‘test1’, ‘compare’ => ‘LIKE’ It should give you a SQL query with: … LIKE ‘%test1%’ … 2) You might want to save the string as ,test1,test2,test3, to make the whole word search easier: ‘key’ => ‘_my_custom_field_key’, ‘value’ … Read more
When adding a metabox, the metabox itself isn’t saved in the database. It’s loaded from the plugin code that is written, then it’s up to you to fill it with appropriate values. You don’t have to create additional fields in the DB. There is a function: update_post_meta($post_id, $meta_key, $meta_value); In your case you might do … Read more
There is a dynamic hook right before any new metadata is added: do_action( “add_{$meta_type}_meta”, $object_id, $meta_key, $_meta_value ); It would be add_post_meta for posts accordingly. Note that you might to tinker some to catch this precisely in the case of new post being created, for example hook into publish_post first, note the ID, and add … Read more
Your meta key should be specified as the meta_key argument, and orderby should be meta_value_num: $args = array( ‘post_type’ => ‘post_sermons’, ‘post_status’ => ‘publish’, ‘posts_per_page’ => ot_get_option(‘wpl_sermon_per_page’), ‘paged’=> $paged, ‘meta_key’ => ‘video_order’, ‘orderby’ => ‘meta_value_num’, ‘order’ => ‘ASC’ ); See WP_Query for explanations of query arguments.