Wrong value of ACF empty fields

  • Resolved Łukasz

    (@edker)


    1 year, 5 months ago

    While exporting custom fields created with ACF, if field has an empty value than plugin, instead of just leaving the field empty, inserts ACF field name instead.

    For example:
    In the CSV file, plugin creates a column named description for custom field named description. If for a given post this field is empty (but stored in the database) it, instead of empty value, saves string “field_description”, which is a field name used in ACF configuration. It apparently gets this value from a hidden meta field _description that ACF creates.

Viewing 1 replies (of 1 total)
  • smacksupport

    (@smacksupport)

    1 year, 5 months ago

    @edker Thank you for letting us know. This behaviour arises because the plugin obtains the meta value straight from the database, including ACF’s hidden meta fields (e.g., _description), which include configuration information. Is there any way you could provide the issue screenshot or even your ACF configuration?
    Our team will look into this more and provide an update to correct this behavior, so the generated CSV will leave these fields blank if they have no value.

Viewing 1 replies (of 1 total)

The topic ‘Wrong value of ACF empty fields’ is closed to new replies.