• Resolved zwief

    (@zwief)


    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/mysite.com/wp-content/plugins/advanced-custom-fields/acf.php on line 1108

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/mysite.com/wp-content/plugins/advanced-custom-fields/acf.php on line 1112

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/mysite.com/wp-content/plugins/advanced-custom-fields/acf.php on line 1116

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/mysite.com/wp-content/plugins/advanced-custom-fields/acf.php on line 1120

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/mysite.com/wp-content/plugins/advanced-custom-fields/acf.php on line 1124

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/mysite.com/wp-content/plugins/advanced-custom-fields/acf.php on line 1128

    http://wordpress.org/extend/plugins/advanced-custom-fields/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Yup, it seems like updating from 2.x to 3.x is a death sentence for your Web site. You will lose all data. Oops?

    I know I would not trust this plugin. I’d use ExpressionEngine or something similar instead.

    Plugin Contributor Elliot Condon

    (@elliotcondon)

    Thanks @houdini2758

    Yes, updating from v2 to v3 can sometimes result in data loss. This is due to different encoding on databases.

    Can you try reverting to your v2.x backup and update to the very last v2. Then update to the very first v3

    That should make the transition smoother as less updates are run at once.

    Good luck!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: Advanced Custom Fields] Upgrading from 2.0.5 to 3.1.6 Totally Breaks my Site’ is closed to new replies.