Divi email form not working: read its reply

An email signup does two jobs in one click. It checks the fields on the page, then sends the address to a mailing service you connected in the builder. The visitor sees the result only in the same small box, so every failure in the second job looks like a failure of the first. A key that was replaced, a list that was deleted, or a request the browser blocked can leave the visitor with a spinner or a vague line. Nothing on the page says which one it was, and the subscriber count stays flat.

• Enter a valid address and press Subscribe. Note whether the box shows a success line, an error line or nothing.
• If the form has a name field, leave it empty and check whether it is required and where the error shows.
• Open the browser console on Subscribe. A request to the mailing service that never finishes is the signal.
• Check the connection to the email service in the builder, and confirm the list the form uses still exists.
• Open the page in a window with no browser extensions and submit again. If it works there, a blocker is the cause.

The signup box looks like one action, but the page runs two steps in a row. First it confirms the fields are filled in and valid. Then it hands the address to the mailing service, and waits for that service to answer. The reply the visitor sees comes from the second step, and it is drawn in the same small box as the first. A problem with the connection, the key or the list therefore looks the same as a field that was left blank, and a visitor cannot tell the two apart.

The owner tests the first step well. They type an address, press Subscribe, and see the success line, because the connection was set up on the day the site was built. A few weeks later the mailing service rotates the key, or someone deletes the list the form pointed to, and the first step still passes. Only the reply changes, and only when a stranger submits from a new browser.

Read the box first. A success line means the service accepted the address. An error line means the form knows something went wrong, and that text often names the field at fault. A spinner that never stops means a request did not finish, which is the hardest case to see from the page. Open the browser console and submit again. A request to the service that stays pending, or a script that failed to load, explains the spinner. An empty box after submit, with no console entry, usually points at the form's own validation.

A simulated visitor fills in the signup box, presses Subscribe, and records the reply it sees. If the box spins, shows an error or stays empty, the report gives the step, a screenshot of the box at that moment, and any request that did not finish in the browser. The run cannot see your mailing service, so it cannot confirm that the address reached the list. It shows what a visitor sees in the box, which is the part you can fix first.

Signups break when something inside the mailing service changes: a list is merged, a key is replaced or an account is moved to another plan. The form itself stays the same, so nothing on the page looks different. After any change in the mailing service, submit the signup from a clean window and check the success line before you tell anyone the form is live.