Use ‘relation’ => ‘OR’ as in the Codex example below: $args = array( ‘post_type’ => ‘product’, ‘meta_query’ => array( ‘relation’ => ‘OR’, /* <– here */ array( ‘key’ => ‘color’, ‘value’ => ‘blue’, ‘compare’ => ‘NOT LIKE’ ), array( ‘key’ => ‘price’, ‘value’ => array( 20, 100 ), ‘type’ => ‘numeric’, ‘compare’ => ‘BETWEEN’ ) … Read more
The easiest way I’ve seen is to echo it where you need it: function inline_css() { echo “<style>html{background-color:#001337}</style>”; } add_action( ‘wp_head’, ‘inline_css’, 0 ); Since 2019 you can also add styles inline inside the body, shown here without using echo: function example_body_open () { ?> <style> html { background-color: #B4D455; } </style> <?php } add_action( … Read more
Due to a backwards-incompatible change in version 5.2, you can no longer retrieve the form’s meta data using get_posted_data(). Instead, you can use the id value in the array returned by get_current(): $contact_form = WPCF7_ContactForm::get_current(); $contact_form_id = $contact_form -> id;
The get_field_object() function requires the field KEY not the field NAME. See docs: http://www.advancedcustomfields.com/resources/functions/get_field_object/ So it should looks something like this… $field = get_field_object(‘field_53d27f5599979’); $value = get_field(‘field_myfield’); $label = $field[‘choices’][ $value ]; You can find the field key by clicking on “Screen Options” > “Show Field Key” and it should appear next to the field … Read more
Looking at the filter: $post_content = apply_filters( ‘wpseo_pre_analysis_post_content’, $post->post_content, $post ); it would be a matter of adding your fields content to string being analyzed. You have to do the get_field() part right, this is untested: add_filter( ‘wpseo_pre_analysis_post_content’, ‘filter_yoasts_wpse_119879’, 10, 2 ); function filter_yoasts_wpse_119879( $content, $post ) { $fields = get_field( ‘name’, $post->ID ); return … Read more
This might be a good read for you. I’m not sure exactly what you’re looking to do so I’ll lay this out in a simple format. This query will pull all Posts under the Post Type recipes where the custom field side-dishes exists. You can then loop through and display them how you would like. … Read more
Note that I don’t have ACF PRO 5.8 which comes with the Block features, but I hope this answer helps. If you look at the example here, you can retrieve the additional/custom CSS classes using props.attributes.className; i.e. the classes are saved as an attribute named className. So with that in mind and based on acf_register_block() … Read more
Using the Advanced Custom Fields plugin you can assign options pages to you custom posttype like this: if( function_exists(‘acf_add_options_page’) ) { acf_add_options_page(array( ‘page_title’ => ‘YOUR_PAGE_TILE Options’, ‘menu_title’ => ‘YOUR_MENU_TITLE Options’, ‘menu_slug’ => ‘options_YOUR_SLUG’, ‘capability’ => ‘edit_posts’, ‘parent_slug’ => ‘edit.php?post_type=YOUR_CUSTOM_POSTTYPE_SLUG’, ‘position’ => false, ‘icon_url’ => ‘dashicons-images-alt2’, ‘redirect’ => false, )); } That way you get an … 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 problem is that the function update_field from ACF works a little bit different from update_post_meta. Can you see it? update_post_meta( $post_id, $meta_key, $meta_value, $prev_value ); update_field( $field_key, $value, $post_id ); If you use update_post_meta you should in my opinion use get_post_meta to get the meta. If you use update_field you should use the_field or … Read more