For the love of GOD there has to be a better way! I have had to make numerous changes to field names and now i am trying to import tons of data and need to map to fields.. BUT I’m seeing every single custom field ever created AND fields now with “field_bunch of numbers” that I cant even identify! Unbelievable.
Sorry, but ‘time’ is the one thing we can’t get back! Unfortunately I have had to drop this plugin, gladly before i purchased the addons, especially the needed Options and Repeater.
But just having too many problems with the template I am using for client. And secondly because of the issue above, the fact that there are a multitude of test custom fields that cant be cleanly deleted seeing as they were created by ACF? Sorry, but just cant pass that on to a client. Especially when they ask about all of the fields just sitting there from prior dev and myself.. then to respond, well I cant delete them (sure, I know I can.. with “time” that i don’t have to hopefully search enough correct methods and then hopefully do not screw up db).. yea, I know, backup db first.. But why even go through all that when the plugin that created the fields should be able to delete them aswell. EVEN IF,there is a big warning that comes up.. “Do you really wanna do this, your data in those fields will be loss”.. my answer is a big fat yes, because I need them gone.
As far as the fields with names that are “field_bunch of numbers”. Maybe in a future release if you can have the “key” values for fields start with and underscore (_), or maybe have a setting that allows us to set that the key values should be hidden from WP by starting with an underscore, that might help.
A way to delete unused fields would be nice though.
Wow, it’s almost 2 years later, and we are still not able to remove old unused DB records created by ACF?
I would think keeping a clean tidy DB would be reason enough for this to be implemented!
Since this doesn’t seem to be important, can someone give us an official way to SAFELY remove this useless fields manually?
The other massive issue with this, is that the old ACF data is seen by WP search functions.
We had an ACF text area for staff listings on an old theme. We approached that content differently on the newest theme, but the search results now show old data in the results. Which has conflicts in between the old unaccessible ACF content and the new data.
The topic ‘Flush Unused Custom Fields’ is closed to new replies.
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!
© 2022 Advanced Custom Fields.