Home › Forums › General Issues › Moving old custom fields to ACF › Reply To: Moving old custom fields to ACF
ACF removes it because it seriously impacts the performance of the editor.
You can enable it by adding the following to functions.php
add_filter('remove_wp_meta_box', '__return_false', 20);
There is no tutorials or information regarding moving other types of custom fields to ACF. There have been plenty of discussions here in the past.
Basically, if the custom field holds a single, simple text value then all you really need to do is create an ACF field with the same field name (meta_key). If the field can contain multiple values or is more complex than a simple text value then the fields need to be converted to what ACF needs. The details of every type of field are too complex to go into every possibility. It requires understanding how the existing field is stored in the DB and converting the value to what ACF needs stored in the DB for each type of field.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
🚨 The 2023 ACF Annual Survey closes tomorrow! This is your last chance to complete the survey and help guide the evolution of ACF. https://t.co/0cgr9ZFOJ5— Advanced Custom Fields (@wp_acf) May 18, 2023
© 2023 Advanced Custom Fields.