FREEForms UI

Manage Advanced ACF Forms from the WordPress administration. This module is an enhanced version of the native ACF Form feature. While all native settings can used, Dynamic Forms adds many new settings and introduce “Actions” for a complete control over the form behavior.

Dynamic Form

The unique form slug

Render & map fields of the following field groups

Add actions on form submission

Click the "Add action" button below to start creating your layout
0 Custom action

Set a unique action slug

0 Email action
0 Option action

(Optional) Target this action using hooks.

Choose which ACF fields should be saved to this option

Fill inputs with values

Choose which ACF fields should have their values loaded

0 Post action

(Optional) Target this action using hooks.

Click to initialize TinyMCE

Choose which ACF fields should be saved to this post

Fill inputs with values

Choose which ACF fields should have their values loaded

0 Redirect action

(Optional) Target this action using hooks.

The URL to redirect to. See "Cheatsheet" tab for all available template tags.

0 Term action

(Optional) Target this action using hooks.

Click to initialize TinyMCE

Choose which ACF fields should be saved to this term

Fill inputs with values

Choose which ACF fields should have their values loaded

0 User action

(Optional) Target this action using hooks.

Click to initialize TinyMCE

Choose which ACF fields should be saved to this user

Fill inputs with values

Choose which ACF fields should have their values loaded

1 Post action

(Optional) Target this action using hooks.

Click to initialize TinyMCE

Choose which ACF fields should be saved to this post

Fill inputs with values

Choose which ACF fields should have their values loaded

Apply field groups locations rules for front-end display

Whether or not to create a <form> element

Form class and id

class
id

Add class to all fields

wrapper class
input class

Whether or not to create a form submit button. Defaults to true

The text displayed on the submit button

HTML used to render the submit button.

HTML used to render the submit button loading spinner.

Whether to include a hidden input field to capture non human form submission. Defaults to true.

Whether or not to sanitize all $_POST data with the wp_kses_post() function. Defaults to true.

Whether to use the WP uploader or a basic input for image and file fields. Defaults to 'wp' Choices of 'wp' or 'basic'.

Determines element used to wrap a field. Defaults to 'div'

Determines where field labels are places in relation to fields. Defaults to 'top'.
Choices of 'top' (Above fields) or 'left' (Beside fields)

Determines where field instructions are places in relation to fields. Defaults to 'label'.
Choices of 'label' (Below labels) or 'field' (Below fields)

Override the native field groups HTML render

Extra HTML to add before the fields

Render your own customized HTML.

Field groups may be included using {field_group:group_key}
{field_group:Group title}

Fields may be included using {field:field_key}
{field:field_name}

Extra HTML to add after the fields

Hide the general error message: "Validation failed. 1 field requires attention"

Hide the successful notice when an error has been thrown

Do not prompt user on page refresh

Choose where to display field errors

Add class to error message

Hide form on successful submission

A message displayed above the form after being redirected. See "Cheatsheet" tab for all available template tags.

HTML used to render the updated message.
If used, you have to include the following code %s to print the actual "Success message" above.

PROActive Forms

The pro version allows developers to manually activate Forms individually using the “Active” switch in the sidebar.

Getting Started

Just like ACF Forms, first you need to create a Field Group that will contain the form’s fields. You can then create a new form from the ACF > Forms menu and assign that field group to the form. Once saved, the form will now map the Fields from the Field Group. This means those fields will be usable directly from the UI.

Out-of-the-box, the form will do nothing on submission. You’ll have to add one or multiple actions to define what you want to do with the form. Once correctly configured, you can display the form using acfe_form() function or [acfe_form] shortcode. Usage example:

<?php get_header(); ?>

    <?php 
    
    // Using Form Name
    acfe_form('my-form');
    
    // Using Form ID
    acfe_form(120);
    
    // Using Form Array
    acfe_form(array(
        'name' => 'my-form'
    ));
    
    ?>
    
<?php get_footer(); ?>

Override Settings

You can override form settings directly in PHP by passing the setting key and its value.

acfe_form(array(
    'name'                         => 'my-form',                // Call by name
    'acfe_form_uploader'           => 'basic',                  // Force Uploader to basic
    'acfe_form_html_submit_button' => '<button>Submit</button>' // Change Submit Button 
));

Pass Custom Data

It is possible to pass custom data to the form using PHP. Those data can then be retrieved in the UI using the {form:my_user} Template Tag or in hooks using the $form['my_user'] parameter.

acfe_form(array(
    'name'    => 'my-form',
    'my_user' => get_current_user_id() // Add Current User ID
));

Custom data can also be passed using the acfe/form/load filter. Usage example:

add_filter('acfe/form/load/form=my-form', 'my_form_settings', 10, 2);
function my_form_settings($form, $post_id){
    
    // Add Current User ID
    $form['my_user'] = get_current_user_id();
    
    // Return
    return $form;
    
}

Forms Cheatsheet

Dynamic Forms have many Template Tags available that can be used in the UI. Those tags let you retrieve various dynamic data in order to customize the form behavior.

Learn more

Forms Helpers

You may use different PHP helpers in the forms hooks in order to cutomize actions behaviors.

Learn more

Forms Hooks

Dynamic Forms are bundled with general hooks allowing you to change the form settings, add validation rules and trigger a custom action on submission. Those hooks are tied to forms, and act independently from Actions.

Learn more

Forms Actions

Actions are pre-defined templates that trigger a specific behavior. There can be an unlimited number of Actions per form. While every Actions have unique features like create a post, a user or send an e-mail, they also have their own validation & submit hooks.

Form Actions also have their own specific hooks that allow you to change their behavior. Learn more about Actions:

Custom Action
E-mail Action
Option Action PRO
Post Action
Redirect Action
Term Action
User Action

Export/Import Forms

It is possible to export and import Forms in a Json file using the ACF > Tools menu or directly within the Dynamic Forms UI.

Hide the module menu

ACF Extended use the native ACF setting show_admin to determine if the module menu should be displayed or not. You can read more about that setting on the ACF article How to hide ACF menu from clients. Usage example:

add_filter('acf/settings/show_admin', '__return_false');

Disable The Module

The Form module is enabled by default. It can be enabled and disabled in the Settings UIPRO, or with the following code:

// Using acf/init
add_action('acf/init', 'my_acfe_modules');
function my_acfe_modules(){

    // Disable Dynamic Forms
    acf_update_setting('acfe/modules/forms', false);
    
}

// Or using acfe/init
add_action('acfe/init', 'my_acfe_modules');
function my_acfe_modules(){
    
    // Disable Dynamic Forms
    acfe_update_setting('modules/forms', false);
    
}