Normally you would just specify a meta_value, e.g.: $args = array( ‘post_type’ => ‘business’, ‘meta_query’ => array( array( ‘key’ => ‘specials’, ‘value’ => ‘these are not the specials you are looking for – Obi Wan Kenobi’ ) ) ); However because your post meta is actually a data structure, a serialised PHP array/object, that’s not … Read more
In your loop, you can access the id of the parent page with $post->post_parent. You just need to pass this value as second parameter: <img src=”https://wordpress.stackexchange.com/questions/111351/<?php the_field(“header_image’, $post->post_parent ); ?>”>
The first parameter passed to register_meta() is always post for posts, Pages (post type of page) and custom post types. However, the REST API Handbook says that: Prior WordPress 4.9.8, meta fields set to show_in_rest using register_meta are registered for all objects of a given type. If one custom post type shows a meta field, … Read more
I stuck with the same question and actually tested wpautop(). It worked, e.g. echo wpautop(get_post_meta($post->ID, ‘_aboutus’, true)); Still, I came around one issue. When sanitizing the user input, don’t use a sanitization method that removed the line breaks before using wpautop 🙂
A meta box is an element in the graphical user interface, a custom field is an extra key and value stored with a post. Most of the time the interface to change the value of a custom field is put in an extra meta box – or in the default meta box for custom fields, … Read more
Since you are new to WordPress I would suggest using Meta Box Script for WordPress which provides an easy way of adding your custom fields to the post edit panel and its main features are: Support various field types, including: text, textarea, checkbox, checkbox list, radio box, select, wysiwyg, file, image, date, time, color. Developers … Read more
I’ve read through your post in it’s entirety, I certainly don’t see anything particularly wrong with it, but it sounds to me like your more frustrated with how it’s been laid out. I personally have a big objected oriented programming background, it allows me to establish a structure and makes my code much more re-usable. … Read more
To me, the simplest solution would be creating additional field in JSON response and populating it with selected post meta: function create_api_posts_meta_field() { // “tribe_venue” is your post type name, // “protected-fields” is a name for new JSON field register_rest_field( ‘tribe_venue’, ‘protected-fields’, [ ‘get_callback’ => ‘get_post_meta_for_api’, ‘schema’ => null, ] ); } add_action( ‘rest_api_init’, ‘create_api_posts_meta_field’ … Read more
you can use custom taxonomies and make you query_posts much easier! by that i mean create a custom taxonomy for type,duration like so: add_action(‘init’,’register_event_tax’); function register_event_tax(){ register_taxonomy(‘even_type’,array(‘events’), array( ‘hierarchical’ => false, ‘labels’ => ‘type’, ‘show_ui’ => true, ‘query_var’ => true, ‘rewrite’ => array( ‘slug’ => ‘type’ ), )); register_taxonomy(‘even_duration’,array(‘events’), array( ‘hierarchical’ => false, ‘labels’ => … Read more
That’s because the fields weren’t set then. Note: The »Autosave« process/request also doesn’t save them. Use the values from $_POST instead for your “new_to_publish” action. EDIT: Do NOT forget to escape and properly sanitize input data! Else you will open a security hole.