Title: Custom fields backward compatibility
Last modified: August 20, 2016

---

# Custom fields backward compatibility

 *  [–](https://wordpress.org/support/users/disonancias/)
 * (@disonancias)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/custom-fields-backward-compatibility/)
 * Elliot,
 * Would it be possible to keep backward compatibility for custom field types?
 * Many of my sites rely on them and, even though I could update them all according
   to the changes in ACF 4, it would take a while, and I’d like to keep the plugin
   updated, especially because of the bug and vulnerability fixes. And I’m guessing
   I’m not the only one in this situation.
 * Thanks in advance for any help or information you may provide, I’d really like
   to know how to proceed.
 * Cheers,
 * Ricardo
 * [http://wordpress.org/extend/plugins/advanced-custom-fields/](http://wordpress.org/extend/plugins/advanced-custom-fields/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [schwarzgrau](https://wordpress.org/support/users/schwarzgrau/)
 * (@schwarzgrau)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/custom-fields-backward-compatibility/#post-3633301)
 * The basic fields like Text, textarea, radio, select etc. are all backwards compatibile.
   
   At least after my upgrade from 3.x.x to 4.0.2 all fields keep their values and
   stay the same. Just plugin-fields like taxonomy are need to set up again.
 *  Thread Starter [–](https://wordpress.org/support/users/disonancias/)
 * (@disonancias)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/custom-fields-backward-compatibility/#post-3633347)
 * schwarzgrau, that’s exactly what I meant, add-on custom types. Just was wondering
   if it’s possible to keep the old API along with the new one.
 *  [schwarzgrau](https://wordpress.org/support/users/schwarzgrau/)
 * (@schwarzgrau)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/custom-fields-backward-compatibility/#post-3633348)
 * ok taxonomies would be the same, since they get saved outside of the custom-fields
   or meta values. But you’re right, some other field types would be destroyed, 
   even if there values still in the meta.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Custom fields backward compatibility’ is closed to new replies.

 * ![](https://ps.w.org/advanced-custom-fields/assets/icon.svg?rev=3207824)
 * [Advanced Custom Fields (ACF®)](https://wordpress.org/plugins/advanced-custom-fields/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/advanced-custom-fields/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/advanced-custom-fields/)
 * [Active Topics](https://wordpress.org/support/plugin/advanced-custom-fields/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/advanced-custom-fields/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/advanced-custom-fields/reviews/)

## Tags

 * [ACF](https://wordpress.org/support/topic-tag/acf/)
 * [backward compatibility](https://wordpress.org/support/topic-tag/backward-compatibility/)
 * [custom fields](https://wordpress.org/support/topic-tag/custom-fields/)

 * 3 replies
 * 2 participants
 * Last reply from: [schwarzgrau](https://wordpress.org/support/users/schwarzgrau/)
 * Last activity: [13 years, 2 months ago](https://wordpress.org/support/topic/custom-fields-backward-compatibility/#post-3633348)
 * Status: not resolved