Support » Plugins and Hacks » Advanced Custom Fields » Update caused advanced custom fields to display db field ID instead of content

Viewing 7 replies - 1 through 7 (of 7 total)
  • so, the custom fields displayed, for example, 3257 where it would have inserted code or text.

    And yes, I did run the database upgrade, and also emptied caches.

    Is this happening to all field types (both text AND file/image/post object)?

    I am only using text and wysiwyg. It is affecting both of those field types.

    Two things to check.

    1. Edit one of your posts. Do the correct ACF values populate into the input fields?

    2. In one of your templates (within the loop), add this:
    <?php var_dump(get_post_custom($post->ID)); ?>

    This will determine if the data still exists. If so, then at least it’s narrowed down to an API bug. I’m assuming you’re using get_field() to get the field values, and not some custom query.

    I can re-try this locally with MAMP to see if it happens… don’t want to risk on live site.

    I am using for example, <?php the_field('year'); ?>

    Should I switch to <?php get_field('year'); ?>

    Yeah, the same problem.

    And if I use “get_field” instead of “the_field” then it displays nothing.

    I waited for bugfixes, looks like 2.1.3 version is good. Auto-update from 2.0.5 with no issues. Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Update caused advanced custom fields to display db field ID instead of content’ is closed to new replies.