Support

Account

Register Login

Forum Replies Created

  • Thank you, that was exactly what I was looking for!

  • I’m not sure I’m following you. I never sync the database development > live, only the other way around. Would that be a problem with this approach?

    How do I make sure the field groups are not loaded from the database but only from json on my production site? Should I delete the field groups on live and sync again?

  • Ok – good to know that this is expected behaviour, thanks!

    The fact that is doesn’t work like this makes me wonder though, am I wrong in thinking that this would be a good workflow? Is there a recommended workflow for keeping my development environment in sync with the changes I do on local?

    Manually deleting the field groups in all environment’s doesn’t seem like a good way to keep everything “in sync”.

  • Hi, sorry maybe I’m unclear or not using the right terminology here.

    What I am deleting is a “field group” (i guess, I have a my native language set). This field group contains one field, in my testcase, a simple textfield.

    I add the group with the one text field and a new json file is created. I push to live and then I can sync and it shows up as it should.

    However, if I on my local environent delete the group containing this text field, and push and pull, I get no changes to sync and the field is still there.

  • Well, this was strange. I did the following for testing purpose:

    1. Create a new simple text field on development. A new json file was created. Push to live where I do a pull. In live, I can now sync and the field shows up.
    2. Delete the field on my local machine. The json file for the field is deleted. I push this change to live and pull from there. The json file disappears but I don’t even get the option to sync and the field is still there.

  • Sure, i *can* do the same change on production, and delete it there – but that kind of defeats the purpose of this feature I think. The point is to have one source of truth, that changes I make in my development environment will be reflected in production. Modifying my fields in more places than one seems to be a recipe for disaster.

  • Hi,

    I did a check and the json files in the acf-json directory is the same on development and production (after syncing) – however the fields that where deleted still show up in my production environment. How can that be, do they come from the database then?

    In this case, it’s a field group of two repeater fields (and nested text and image fields) and a plain text field.

  • I have the same issue, this is a pretty big bug imo and should be prioritized.
    The bug is introduced in v 5.7.0, going back to 5.6.9 solves it for the moment.

  • Argh. I must have accidentally renamed the field group (I have quite a lot). The associated json_file still had the old title, but in my back end view it had another.

    I found out when I tried importing the json and it complained that I already had that field group.

    Sorry for taking your time with this, and thanks for your help.

  • I’m using 5.2.8. They do not appear in the ‘My fields’ page (wp-admin/edit.php?post_type=acf-field-group).

    When editing a post they show up as they should, and they contain the content they should. But I can’t edit the fields anywhere. It’s just one field group it seems, all other field groups appear as they should.

  • Hey,

    Thanks for your feedback. I do already regenerate my thumbnails. My problem was my live server environment was lacking PHP-ImageMagick, so no thumbnails where created. Once I installed that, everything works just fine.

    Seems I can’t set original post to answer, so I’m setting this as answer instead.

Viewing 11 posts - 1 through 11 (of 11 total)