Home Forums ACF PRO 5.3.6 Upgrade Issue not displaying some fields


5.3.6 Upgrade Issue not displaying some fields

  • I assked this on GitHub but now that I can get in here I will ask here.
    We upgraded from 5.3.5 to 5.3.6 and these fields are no longer displayed in the front end even though others farther down the page for sidebar, etc. work fine. If we revert back to 5.3.5 it displays fine again.
    Here is the current non-woking
    `<div class=”row marg_bot_30″>

    $post_object = get_field(‘featured_person_object’,’option’);
    if( $post_object ):

    // override $post
    $post = $post_object;
    setup_postdata( $post );


    <div id=”home_bio_box” class=”make_these_equal_ht col-sm-8″>
    <a href=”<?php the_permalink(); ?>” class=”flag block block–profile”>
    <div class=”flag__img”>
    <img src=”<?php the_field(‘featured_picture’); ?>” alt=”FeaturedPicture” class=”img-responsive”>

    <div class=”flag__content”>
    <strong class=”block__category”>Profile</strong>
    $first_name = get_field(‘first_name’);
    $last_name = get_field(‘last_name’); ?>
    <h2><?php echo $first_name . ” ” . $last_name ?></h2>
    <small><?php the_field(‘job_title’); ?></small>
    <?php echo firstSentence(get_field(‘description’)); ?>
    <button id=”featured_profile_read_more” class=”link” type=”button”>Read More</button>


  • What types of fields are not returning the correct values?
    field types, return value settings if any

  • I reverted a site to 5.3.5, added fields and values like the ones you’re having problems with (post object, image, etc) and then updated to 5.3.6. I’m not seeing any issue.

    What other plugins are you running? theme? You’ll need to narrow down where the conflict might be by disabling plugins and possibly trying on one of the default WP 20XX themes.

    This appears to have something to do with fields that save ID values, not that I know what that might be. There is another topic that is similar to this one, you may have something in common.

  • Thanks for the info.
    In my post on GitHub Elliot requested “Can you please re-download the plugin and try again. I have fixed this issue moments after releasing the version”

    I did so and now it is working fine. Probably why it did for you in your tests.

    Thanks for looking into it!

  • What are the chances… you must have updated during a tiny window when the bug existed, which explains why I didn’t see a problem when I updated.

  • Hi guys

    Sorry about this issue.
    I’ll be releasing a minor version today to solve this for all users who downloaded in the window.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.