Latest update &*^%$$ messed things up!

• 

  • PandS

  • January 23, 2015 at 5:24 am

  Luckily I am only working on a dev server, but, updating from 5.1.6 rendered the whole ACF set up useless.

  I have:
  ACFPro 5.1.6
  WPML (latest but not sure this affected it)
  Latest WP.

  I’m using a lot of flexible fields and repeaters and after updating to 5.1.7 I found a lot of sub fields had bundled themselves into another field and lots of items / paths were broken.

  For example:
  5.1.6
  – Field One
  — sub field 1
  — sub field 2
  — sub field 3

  – Field two
  — sub field 4
  — sub field 5
  — repeater 1
  etc

  5.1.7
  – Field One
  — sub field 1
  — sub field 2
  — sub field 3
  — sub field 4
  — sub field 5
  — repeater 1

  – Field two
  EMPTY!
  etc

  I’ve reverted back to 5.1.6 and everything is happy bunny time again.

  Advice: BACK EVERYTHING UP BEFORE UPDATING ANYTHING!
• 

  

  • Elliot

  • January 23, 2015 at 9:43 am

  Hi @PandS

  This looks like a serious issue!

  I’m not sure how the sub fields have changed their parent relationship as absolutely no DB data has been modified…

  Any chance You can throw me some screenshots to help understand exactly where the issue is?
• 

  • PandS

  • January 23, 2015 at 9:49 am

  Hi Elliot.

  My post here wasn’t really to scare anyone, just a heads up to see if anyone else has had the same thing.
  Other updates, from day one have either run perfectly or had very minor issues which just needed a reinstall/ off/ on again to fix.
  I’ll try and recreate it again and grab some shots, but we’re running late on the project so I’ll see what I can do.
• 

  

  • Elliot

  • January 23, 2015 at 10:18 am

  Hi @PandS

  All good mate. Were the field’s registered via PHP, JSON or DB?
  Is there any chance another action was performed before or afetr upgrading? Perhaps a JSON sync?

  I’m hoping the issue is due to something else – most likely JSON related