• Resolved windowmandrill

    (@windowmandrill)


    In case anyone else has wondered why acf-json files might be suddenly stored in different filenames:

    If the the plugin is activated together with the advanced custom fields plugin, it’s interfering with acf’s local json filenames (if the theme is using this feature).

    The file name for acf’s local json files is using underscores e.g. “group_{fieldkey}.json”. With better images activated, the format changes to “group-{fieldkey}.json”.

    This causes some unwanted side effects (the .json file might be created twice, instead of being overwritten) that can prevent changes in field groups being shown in the backend.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor hemenderki

    (@hemenderki)

    Hello @windowmandrill! Thank you for getting i touch with us. We’ll take a look at this and fix it in the next update asap.

    Plugin Contributor hemenderki

    (@hemenderki)

    We have published an update now that should resolve the issue. Please let us know if you are still experiencing any issues.

    Thread Starter windowmandrill

    (@windowmandrill)

    Thank you! The json files are now stored in the expected naming convention: group_{fieldkey}.json

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Advanced Custom Fields > acf-json filenames’ is closed to new replies.