• Support for local json for better performance. Does this work to convert existing non to local json? Or will it be duplicated and just create local json of the existing meta fields and groups?

    Do you have support for non-theme WordPress like oxygen builder, who does not have a theme and therefore no files to add and store local json. Do you store it in your plugin folder instead?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    I don’t know if I understood correctly, but here is how it works:

    Native ACF behavior:

    If you create a folder called /acf-json in your theme, everytime you update a field group a local file called group_abcdef123.json will be created (if it doesn’t exists) and synchronized.

    With ACF Extended:

    If you create a folder called /acf-json in your theme, you will be able to check the option ‘Json Sync’ for each field groups. If you don’t use this option, the file group_abcdef123.json will not be created/updated. You will have to activate it for each field group, this way you control which field groups are synchronized with Json.

    Regarding the json folder path:

    ACF let you customize the path of the json folder. Here is an article explaining it: https://www.advancedcustomfields.com/resources/local-json/

    For your information ACF Extended also use that path.

    Note: ACF & ACF Extended never store json files in the plugin folder.

    I hope I answered your questions.

    Regards.

    Thread Starter Rookie

    (@alriksson)

    Native ACF behavior:

    If you create a folder called /acf-json in your theme, everytime you update a field group a local file called group_abcdef123.json will be created (if it doesn’t exists) and synchronized

    Correct but what happens with the one stored in the database before acf-json was activated?

    With ACF Extended:

    If you create a folder called /acf-json in your theme, you will be able to check the option ‘Json Sync’ for each field groups. If you don’t use this option, the file group_abcdef123.json will not be created/updated. You will have to activate it for each field group, this way you control which field groups are synchronized with Json.

    Ok but by default acf-json is syncronizing no? Talking without using your plugin.

    Regarding the json folder path:

    ACF let you customize the path of the json folder. Here is an article explaining it: https://www.advancedcustomfields.com/resources/local-json/

    For your information ACF Extended also use that path.

    Note: ACF & ACF Extended never store json files in the plugin folder.

    Many thanks, would look into this and where to store maybe a new custom acf-json folder then. Since I use themeless with a page builder so there is no theme folder to store it. Or it is in the sftp but not loaded. Look into native support for oxygen builder would be nice so it’s loaded correctly with acf-json. Using this which is the solution right now:
    https://github.com/wplit/ACF-Local-JSON
    Which do as you say but with a plugin and easy toggle to create /acf-json folder in plugins to store the local-json. Would this work together with your plugin?

    Any update on this?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘local json’ is closed to new replies.