A custom field is a visible form element where users can add information. It’s presentation. Meta data are data stored in one of the meta tables for posts, users, terms and so on. The content of a custom field can be stored as meta data, in a separate table, a text file, on a remote … Read more
Use the following code to add new column and show data properly. function add_user_columns_hospital( $column ) { $column[‘hospital’] = ‘Hospital’; return $column; } add_filter( ‘manage_users_columns’, ‘add_user_columns_hospital’ ); function modify_user_table_row_hospital( $val, $column_name, $user_id ) { switch ($column_name) { case ‘hospital’ : return get_the_author_meta( ‘user_registration_hospital’, $user_id ); default: } return $val; } add_filter( ‘manage_users_custom_column’, ‘new_modify_user_table_row’, 10, 3 … Read more
When you get the date with function get_the_date() you need to pass a $post object or ID as a second parameter: $date = get_the_date( $date_format, $post ); The first parameter here is the PHP date format. The second – Post ID or WP_Post object Here is an example that should work: add_action( ‘acf/save_post’, ‘my_acf_save_post’ ); … Read more
When you do this: ‘_related_posts’: [post.id], you’re actually overriding the entire array or the meta value, so to instead append an item to the existing array, you can use the spread (…) syntax like so: ‘_related_posts’: [ …meta._related_posts, post.id ]. But you may not want to update the meta if the selected post ID is … Read more
There’s a few ways to achieve this but here’s one which supports an unknown depth of children, for example where you have nested groups within groups. Given the field key “field_{some_hash}” of the field, this function will retrieve the field, and its parent most field, and so on until we reach the top of the … Read more
Josh, take a look at: http://farinspace.com/wpalchemy-metabox-data-storage-modes/ … I am thinking I will be changing how WPAlchemy stores values by default … making EXTRACT mode default …
You can use the “orderby” parameter of query_posts. You must specify your custom field and you must give it a numeric value. Short example: query_posts($query_string . “&cat=$que&orderby=meta_value_num&meta_key=your_custom_field”)
You can use meta_query to get only posts with display_submenuexpositions = true and order them by order_submenuexpositions. $args = array( ‘orderby’ => ‘meta_value’, ‘meta_key’ => ‘order_submenuexpositions’, ‘meta_query’ => array( array( ‘key’ => ‘display_submenuexpositions’, ‘value’ => ‘true’, ‘compare’ => ‘LIKE’ ) ) ); $query_posts( $args );
It seems that it still exists, you just have to enable showing it, with screen options http://theandystratton.com/2011/wordpress-3-1-admin-bar-and-i-cant-see-custom-fields
Why not? Same custom field parameters in query should apply and you can use post_type argument to limit query to pages alone.