WordPress.org

1. Gilligan
   Member
   Posted 9 months ago #

   I had to roll back my database because... see title.

2. Gilligan
   Member
   Posted 9 months ago #

   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.

3. logikal16
   Member
   Posted 9 months ago #

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

4. Gilligan
   Member
   Posted 9 months ago #

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

5. logikal16
   Member
   Posted 9 months ago #

   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.

6. Gilligan
   Member
   Posted 9 months ago #

   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'); ?>

7. GlamCat
   Member
   Posted 9 months ago #

   Yeah, the same problem.

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

8. Gilligan
   Member
   Posted 8 months ago #

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

Reply

You must log in to post.