# How to Add a Frontend Post Form in Divi

> Build a post submission form, place its shortcode in a Divi page, match your theme's design, and test a real submission before you launch the page.

By Aleksan Aharonyan, November 18, 2026. Original: https://wpuserpublish.com/blog/divi-frontend-post-form/

A frontend post form in Divi is a shortcode you place inside a Divi module, not a Divi module itself. You build the form in a post submission plugin, copy its shortcode, and paste it into a Text module (or another module that runs shortcodes) on the page you built in the Divi Builder. The form then renders inside your Divi layout, at whatever width and spacing the surrounding row gives it.

## Key takeaways

- Set the form's post status to Pending before the page goes live, so every visitor submission waits for review instead of publishing itself.
- Paste the shortcode into a Divi Text module, because it runs shortcodes and keeps normal module spacing around the output.
- Style the fields with the form's own design preset and custom CSS, then use Divi's row and module settings for the space around the form.
- Test with a logged-out visit and with a low-permission account, then confirm the post arrived with the right status and that the notification email reached you.

## What you need before you add a submission form to Divi

You need Divi and the Divi Builder active, a plugin that provides the submission form and a shortcode, and a page to hold it. Everything else is a decision you should make before you build anything.

- **Divi itself.** The theme and the builder, on a site where you can install plugins. A child theme is worth having if you plan to add CSS beyond what the form settings cover.
- **A post submission plugin.** Divi's modules handle layout, text, images and buttons. None of them collects a post from a visitor, so the form and the shortcode come from a plugin.
- **A decision on who can submit.** Logged-in members only, or anyone including guests. That choice changes the form settings and whether you need a paid plan.
- **A decision on post status.** Whether a submission publishes immediately or waits for you. For most sites with outside contributors the answer is to wait.
- **A test account.** A Subscriber account is enough to submit and shows you what a member with the lowest role sees, which makes it the right role for testing.

## Step 1: Build the post submission form and set the post status

Create the form in the plugin first, because the shortcode you need in Step 2 does not exist until the form does. Add the fields you want contributors to fill in, then decide what WordPress should do with the post when they submit.

The form in this walkthrough is built with [Front User Submit](https://wordpress.org/plugins/front-editor/), a free plugin for frontend post submission and guest posting forms. You drag Post Title, a content editor, category and tag selectors and a featured image into the form, and the plugin generates the shortcode for you. The [form builder basics](/docs/forms/form-builder/) walk through the field list and the order that works for a typical submission form.

Keep the form short. Post Title, a content editor, a category selector and a featured image cover most guest posts and member articles. For the content field you choose one editor per form: EditorJS blocks, a Markdown editor, the classic WordPress editor, or a plain textarea. Pick the one your contributors already know, because asking a first-time writer to learn a block editor inside a submission form is where half-filled drafts come from.

The setting that matters most is Post Status. Publish puts the post live the moment the form is submitted; Pending holds it in the review queue. On any site where strangers or new members can submit, choose Pending. In Front User Submit you set the form's Post Status to Pending, so every post collected through the Divi page stays unpublished until an editor opens it. Pending is a normal WordPress post status, so those submissions appear in the same Posts list you already use, and you approve them the same way you would approve anything else.

Two more settings are worth five minutes now. The redirect after submit decides whether the writer stays on the page, opens their new post, or lands on a thank-you page you built in Divi. And if you let people edit their submissions later, the time lock stops edits a set number of hours after the post was created, which keeps old articles from changing under you.

## Step 2: Put the form on a Divi page with the shortcode

Save the form, copy its shortcode (it looks like `[fe_form id="12"]`), and paste it into a module on the Divi page where the form should appear. Divi's Text module runs shortcodes, so it places the form inside your layout like any other content.

Open the page in the Divi Builder, add a one-column row where the form belongs, add the module, paste the shortcode into it, and save. Leave the builder and view the page on the front end. You should see the full form sitting inside your Divi section, using the row's width.

Keep the row simple: one column, and the form as the only thing in it. A form squeezed into one column of a three-column row gives the fields too little room on a phone, and Divi does not reflow module contents the way it reflows modules. If you want a short introduction beside the form, put the text in its own row above.

The [shortcodes reference](/docs/getting-started/shortcodes/) lists every shortcode the plugin registers, including the user dashboard and the login and registration forms, in case the page needs more than the submission form.

One decision comes back here: by default the form expects a logged-in user, and a visitor who is not logged in sees a message you can edit in the form settings. That is the right behavior for a members' area. If you want anonymous visitors to submit, turn on guest posting in the form. Guest posting is a Pro feature, covered on [the plans](/pricing/), and guest posts have no author account, so author emails are not sent for them.

## Step 3: Make the form match your Divi design

Match the form with its own design preset first and with Divi's spacing settings second, because the plugin's stylesheet controls the fields while Divi controls the space around them. Changing Divi's typography settings on the module may change some of the text around the form, but it is not a reliable way to restyle the inputs.

Front User Submit ships several form designs, including a Clean preset made to look right on any theme, and a preview that shows a design on your own form before you commit to it. Start with Clean, set the button color to your Divi accent color, and only then reach for custom CSS. The [form designs and display settings](/docs/forms/form-designs/) cover the presets, the button colors, the message placement and the per-form CSS box.

Small corrections belong in the form's custom CSS rather than your child theme, because the rules travel with the form. Border radius, input height and label weight are the three that usually need adjusting to sit beside Divi buttons without looking borrowed. Keep the rules short and use the form's own class names so a Divi update cannot undo them.

Around the form, use Divi's module settings. A little top and bottom padding on the row, and a maximum width on the section that matches the rest of your pages, does more for the "built in Divi" look than any amount of CSS inside the form.

## Step 4: Test a submission from the front end

A submission form works when a real post arrives with the right status, the right fields and the notification email you expected, so test all three before you link anyone to the page.

1. Open the Divi page in a private window while logged out. You should see the restricted message, or the form itself if guest posting is on.
2. Log in as a Subscriber test account and submit a complete post: title, a few paragraphs, a category, a featured image.
3. Watch what happens after submit. The success message, the redirect or the new post should appear exactly as configured.
4. Open Posts in wp-admin and filter to Pending. Your test post should be there with the right author, category and image.
5. Check the admin notification email, then publish the post and check how it renders in your Divi theme's single post template.
6. If you allow front-end editing, open the post from the user dashboard and confirm the edit form loads with the saved content.

If any of that fails, the failure usually points at the step that caused it: no email means the notification settings for that form, no image means the upload field or file permissions, a post that published immediately means the form's post status, not Divi.

## Why the shortcode shows as plain text, and other Divi gotchas

A shortcode that renders as literal text almost always sits somewhere that does not run shortcodes, or has been broken by smart quotes during a copy and paste. Both take seconds to check.

- **The shortcode shows as plain text.** You pasted it into a field that does not process shortcodes. Move it into the body of a Text module and it will render.
- **The shortcode broke after pasting.** Word processors and some editors turn straight quotes into curly ones, so `[fe_form id="12"]` arrives as `[fe_form id=”12”]` and the plugin cannot read the ID. Retype the quotes inside the Divi module.
- **Visitors still see the old version of the page.** A page cache or Divi's static CSS cache is serving the previous markup. Purge the cache after every change to the form or its design.
- **The form sits in a tab, accordion or toggle.** Divi hides that content until the visitor clicks, which can leave a script-driven content editor uninitialized. Test the module open; if the editor stays blank, move the form into a normal row.
- **Logged-out visitors see "This page is restricted".** That is the login restriction doing its job, not a Divi problem. Enable guest posting if anonymous submissions are what you want.
- **The submit button does not match your Divi buttons.** Divi's global button styles usually do not reach inside the form. Set the button colors in the form's own design settings and the radius in its custom CSS.

When all of it works, the page behaves like any other Divi page: you edit copy in the builder, and the submissions stay in WordPress where you already review them.

## FAQ

### Does Divi have a built-in post submission module?

No. Divi's modules cover layout, text, images, buttons, forms for contact-style input and similar display elements, but none of them creates a WordPress post from a visitor's input. You need a plugin that builds the submission form and gives you a shortcode, then you place that shortcode in a Divi module.

### Can visitors submit a post without creating an account?

Only if the form has guest posting turned on. In Front User Submit that is a Pro feature; with the free version, visitors need an account, and logged-out visitors see the restricted message or a login form instead of the submission fields. Guest posts also have no author account attached, so no author emails go out for them.

### Where do the submitted posts actually appear?

They appear in the normal WordPress Posts list, with whatever status the form assigns. Pending submissions wait there until an editor publishes them, and published ones render through your Divi theme's single post template like any other post. If you gave contributors a front-end dashboard, they see their own posts by status without opening wp-admin.

### Do new contributors get a password?

If they register through a front-end registration form, they get the site's default role and usually an email with a link to set their password, the same one the WordPress registration page sends. If that email does not arrive, point them at the WordPress "Lost your password?" page on your site. That page is part of WordPress, so you do not need to build anything for it.
