Forms and Location Rules

Hello @joecpu,

Have you tried the “Post field groups” setting in the Advanced Tab, like in the screenshot I posted?

This will work exactly as acf_form(array('post_id' => 123)).

Let me know!

Regards.

Hello @bootword,

I was replying to @joecpu, who specified that he was using the native ACF Form to display field groups attached to post_id and display specific field group based on the said post taxonomy.

In his case, the setting “Post field groups” is what he’s looking for, as the form field groups will behave the same as it would using the native ACF Form Front.

Regarding what you’re asking for field group location applying on the front-end, the feature is kinda tricky, because all native field groups locations would not work.

For example, the location “Widget == All” doesn’t make much sense in the Front-end. Your feature request is interesting tho, because as you said you could easily define rules like “Current user == viewing front-end” + “Current user != logged in” which seems pretty cool for form display.

After thinking about it, what I can do is to add a setting in Dynamic Forms: “Apply Field Groups Locations Rules”. This way, all users who already run Dynamic Forms with field groups that use the default field group location “Post Type == Post” won’t have their form displaying an empty page after upgrading to the new version.

I add the feature request in the Trello board. For the first version I will focus on the following location rules, so it shouldn’t take too much time:

• Post Type
• Post Category
• Post Taxonomy
• Current user
• Current user role

Have a nice day 🙂

Regards.

Hello,

@bootword

Regarding “Advanced Settings as Default”:

There is no UI for global settings in the plugin for the moment. It will come in a future version. When it will come out, I’ll think about a “default field group” settings template, so you will be able to customize your experience, for all settings.

Meanwhile, you can add the following code in your functions.php file in order to force “Advanced Settings” in all new field groups creation:

add_filter('acf/validate_field_group', 'my_acf_field_group_advanced');
function my_acf_field_group_advanced($field_group){
    
    // Bail early if field group has been already saved
    if(acf_maybe_get($field_group, 'acfe_form') !== null)
        return $field_group;
    
    // Set field advanced settings
    $field_group['acfe_form'] = true;
    
    // return
    return $field_group;

}

Regarding “Blank Checkbox/Radio/Select”:

Message/Tab/Accordion fields are very specific field types, in fact they do not save any value (and get their field name are auto nulled). However, as you can see they cannot be used as conditional logic either. Applying the same behavior to checkbox/radio/select fields (with a switch), would be very experimental IMO and could lead to unexpected behavior.

When a field is used as “conditional logic”, it can “exclude” other dependant fields from saving. Tabs/Accordion/Message do not have such behavior, they are simply used for “display”. Checkbox/radio get their value saved, and if they are used as conditional logic, this value is used to know if a dependant field is supposed to be displayed or not. In the other hand, the tabs/accordions save the user preference (ie: last opened tab) in browser local storage (not in DB).

It looks like your end goal is Elementor integration. If you add such switch on radio/checkbox/select, you would have to hook inside Elementor in order to exclude fields that have this setting enabled. Elementor most likely exclude Tabs/Accordion/Message from available fields manually in the code (by field type).

@joecpu

I’m glad to hear that it now works as you wanted!

If you guys enjoy ACF Extended, feel free to submit a review, it always helps and it’s much appreciated 🙂

Have a nice day!

Regards.

Hello,

@bootword

Regarding “Advanced Settings as Default”:

There is no UI for global settings in the plugin for the moment. It will come in a future version. When it will come out, I’ll think about a “default field group” settings template, so you will be able to customize your experience, for all settings.

Meanwhile, you can add the following code in your functions.php file in order to force “Advanced Settings” in all new field groups creation:

add_filter('acf/validate_field_group', 'my_acf_field_group_advanced');
function my_acf_field_group_advanced($field_group){
    
    // Bail early if field group has been already saved
    if(acf_maybe_get($field_group, 'acfe_form') !== null)
        return $field_group;
    
    // Set field advanced settings
    $field_group['acfe_form'] = true;
    
    // return
    return $field_group;

}

Regarding “Blank Checkbox/Radio/Select”:

Message/Tab/Accordion fields are very specific field types, in fact they do not save any value (and get their field name are auto nulled). However, as you can see they cannot be used as conditional logic either. Applying the same behavior to checkbox/radio/select fields (with a switch), would be very experimental IMO and could lead to unexpected behavior.

When a field is used as “conditional logic”, it can “exclude” other dependant fields from saving. Tabs/Accordion/Message do not have such behavior, they are simply used for “display”. Checkbox/radio get their value saved, and if they are used as conditional logic, this value is used to know if a dependant field is supposed to be displayed or not. In the other hand, the tabs/accordions save the user preference (ie: last opened tab) in browser local storage (not in DB).

It looks like your end goal is Elementor integration. If you add such switch on radio/checkbox/select, you would have to hook inside Elementor in order to exclude fields that have this setting enabled. Elementor most likely exclude Tabs/Accordion/Message from available fields manually in the code (by field type).

@joecpu

I’m glad to hear that it now works as you want!

If you guys enjoy ACF Extended, feel free to submit a review, it always helps and it’s much appreciated 🙂

Have a nice day!

Regards.