Skip to main content
Version: Divi 5

Login Form

Building a login form in Divi 5​

Use the Form module in the Divi 5 Visual Builder to build a frontend login form that uses WordPress user fields and, optionally, ACF user meta.

When to use this form type​

Use Login Form when you want users to sign in from a custom frontend page instead of the default WordPress login screen.

Prerequisites​

  • Divi Form Builder active
  • A page built with the Divi 5 Visual Builder
  • A protected area or redirect target for logged-in users

Step 1: Add the Form module​

  1. Open the page in the Divi 5 Visual Builder.
  2. Insert the Form module where the login form should appear.

Step 2: Define form settings​

  1. Select the Form module and open the Content tab.
  2. Set Form Title and a unique Form ID.
  3. Set Form Type to the Login option.
  4. Set Submit Button Text (e.g. "Log In").

Step 3: Plan your fields​

Login forms typically use:

  • WordPress user fields — at least Login Name (or Email) and Password.
  • ACF user fields — optional; add and map if you use ACF for user meta.

Include at least Login Name and Password.

note

For password options (e.g. show/hide, remember me), see the Form module Content tab field options and the Field types index.

Step 4: Add form fields​

  1. In the Content tab, add fields with Add New Form Field.
  2. For each field set Field Title, Admin Title, Field ID, and Field Type (e.g. Input for login name, Password for password).

See Field types for all types.

Step 5: Map fields​

  1. For WordPress user fields: set Field Mapping Type to User Field (Register/Login Form Only) and select the user field (Login Name, Password, etc.).
  2. For ACF user meta: set Field Mapping Type to User Meta Field (Register/Login Form Only) and enter the meta field name.

Ensure Login Name and Password are mapped.

Step 6: Customize the form​

Use the Content and Design tabs for redirect after login, messages, and styling. Some options (e.g. email notifications) do not apply to Login forms.

Verify it works​

  1. Test with a valid existing user account.
  2. Confirm login succeeds and redirect behavior is correct.
  3. Test with invalid credentials to confirm the user sees the expected error message.
  4. Confirm already-logged-in behavior is correct (for example, notice text or redirect).

Common setup mistakes​

  • Missing Password mapping
  • Incorrect field mapping type for login-related fields
  • Testing with an account that does not have expected permissions
  • Configuring options that are not relevant to login workflows

What's Next​