Metadata not saved automatically

  • After great support I realised my mistake not understanding the full extent of why the plugin settings caused me a few issues. I am now giving this plugin 5 stars, but would like more tutorial videos for novices like me please – which is a bit greedy considering I am using the free version ??

    • This topic was modified 1 month, 1 week ago by tomo55555.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    This review seems to be related to this support thread: https://www.ads-software.com/support/topic/some-form-entries-do-not-get-saved/

    The ACF Extended Form module has been designed to be compatible the most advanced front-end forms setup. This is why ACF Fields must be manually selected in order to be saved to the corresponding “Action” (Post Creation, User Creation, Term Creation etc…). Keep in mind there can be multiple Actions within the same Form, with different Fields saved in different Actions.

    There are various scenarios where this logic is important.

    Example 1:

    You want to create a form where the visitor register a User, and create a new Post (post type: entreprise) on-the-fly, in the same form.

    Your form has 2 Actions:

    • Create User
    • Create Post (Entreprise)

    Your Field Group has the following ACF Fields:

    • Date of Birth (Date Picker)
    • Gender (Select)
    • Entreprise History (Textarea)

    Obviously, you’ll want the “Date of Birth” and the “Gender” to be saved as metadata in the “User”. And the “Entreprise History” to saved in the “Post (Entreprise)”.

    If all ACF Fields were automatically saved in all Actions, it means you would have the “Date of Birth” & and “Gender” saved in both the “User” and the “Post (Entreprise)”. Which is unecessary, as these metadata are irrelevant in the Entreprise. It would also bloat the database with superfluous metadata on the said post.

    Example 2:

    Your Field Group has the following ACF Fields:

    • Date Picker
    • Relationship

    Some developpers want to use ACF Fields interaction, but not actually save them anywhere. For example here, the Date Picker would be simply used to filter the selection available in the ACF Relationship, using the ACF JS API.

    There are other use cases like this, where developpers simply want to let the visitor interact with some ACF Fields, but not save their content. For example: Let visitors filter posts displayed on-page.

    As a conclusion, this setting is here to give developpers full control on which, and how, fields values are saved in most complex use cases.

    I hope this answers your question.

    Regards.

    Thread Starter tomo55555

    (@tomo55555)

    Thanks Konrad, I understand the reasons now. Review updated accordingly.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this review.