ACF Dynamic Content not working when fields are defined by JSON

Nicholas Worth

• March 06, 2021 08:04

I tend to store my ACF fields within a JSON export that a version control within the customer's `/mu-plugins` folder, unfortunately even though this works perfectly fine within WordPress it doesn't work within my Brizy templates. It did use to work in a previous version of Brizy (May 2020 was the last time I touched this site), ever since I updated the editor doesn't recognize the any custom fields and it now displays previous working content with {{brizy placholders}}. I assume this is a bug since the behavior is regressive.

0

• 

  Sandra Prunici

  • March 09, 2021 09:34

  Hi,

  Could you please give us more details about this? How did you set-up the ACF fields using a JSON export from the "mu-plugin"? Why you do not use the standard interface for creating and displaying ACF fields?

  Thanks!

  Best regards,
  Sandra

  0

Please sign in to leave a comment.