I’m building an user form with a revision feature, when the user updates his profile, the admin needs to approve or reject these updates before publish them.
The user form uses the acf_form() to render on front-end. I tried two ideas:
1) Save the form array $_POST['acf'] into a meta data serialized named revisions, but after that, it’s a little complicated to work with the data;
2) Save each field with a prefix _revision_..., using the filters acf/update_value to create this other field and acf/load_value to load the revision field value on the form when the user is still waiting approval. I’m having conflicts here.
I came here to ask if someone has been done this before, has another idea to help me.
What you basically need is two views. For the user you need a view that only shows the fields that the user is allowed to alter. On the second view you need the admin to see both the old and the new updated data.
I would create 2 fields for each field. One that holds the approved content and one that holds a duplicate of the approved content for editing by the user.