WordPress How To Log In and View Divi DB Form Submissions

A visitor fills out your website’s contact form, but the notification email never reaches your inbox. Where do you look next? If your WordPress site has a compatible Divi form database plugin installed and configured, a saved submission may be waiting in the dashboard.

This guide walks you through logging in to WordPress, finding the Divi DB submission area, opening individual entries, and using any available filtering or export tools. It also explains what to check when entries are missing and how to handle the personal information that forms collect.

This guide reflects WordPress and Divi workflows as of 2020; plugin names, tools, and interfaces may have changed since then.

Before you begin: what Divi DB does

Divi’s Contact Form module lets visitors send information through forms built with the Divi Builder. A separate database-storage plugin can save supported submissions in WordPress so that you can review them later, rather than relying entirely on email notifications.

Here, Divi DB refers to the Divi form database plugin installed on your site. Plugins with similar names can have different menus, supported fields, and features. The exact wording on your screen may therefore differ from this guide.

The important distinction is that using a Divi form does not, by itself, guarantee a searchable submission archive. A compatible storage plugin must have been active and working when the submission was sent. Installing one today generally will not recover messages submitted before it was recording them.

Before proceeding, make sure you have:

• Your website’s address and WordPress login credentials.
• A WordPress account allowed to view the plugin’s submission screen.
• A compatible Divi form database plugin installed and active.
• The name or page location of the form you want to review.

If you only need to read inquiries, ask your site administrator for the appropriate access rather than sharing an administrator login.

1. Log in to your WordPress dashboard

Open the login page

For a standard WordPress installation, enter your website address followed by /wp-admin/ in your browser:

https://example.com/wp-admin/

Replace example.com with your own domain. If you are not already logged in, WordPress will usually send you to its login screen. You can also try the standard login endpoint:

https://example.com/wp-login.php

These examples assume WordPress is installed at the root of the domain. If it lives in a subdirectory, include that directory in the address. Some websites also use security tools that change the public login URL. If neither address works, ask the site administrator or hosting contact for the correct location.

Check that the address belongs to your website and uses HTTPS before entering your password.

Enter your credentials

Enter your username or email address and your password, then select Log In. Complete any additional authentication step your site requires.

If you cannot remember your password, use Lost your password? and follow the reset instructions sent to the email address associated with your account. Check your spam folder if the message does not arrive.

Avoid repeatedly guessing passwords: security settings may temporarily lock out your account or IP address. If you no longer control the account’s email address, ask an authorized administrator to help.

Confirm that you are in the right site

Once logged in, you should see the WordPress administration area with a navigation menu on the left. If you land on the public website instead, use the top administration bar to open the dashboard or revisit /wp-admin/.

Check the site name and domain before continuing. This matters especially if your organization has a live website and a separate staging copy: entries collected on one are not necessarily available on the other.

2. Find the Divi DB submission screen

Look through the left-hand WordPress menu for the form database plugin. Depending on the installed product and version, it may have its own menu or appear beneath another menu, such as Divi. Look for wording related to the plugin’s name, form entries, or submissions.

Open that area and locate the submissions list. This is the screen where saved form records should appear.

If you cannot find the menu

Do not assume the submissions have been deleted. A missing menu often points to a plugin or permissions issue.

If your account has permission to manage plugins:

1. Open Plugins → Installed Plugins.
2. Find the Divi form database plugin and note its exact name and version.
3. Check whether it is active.
4. Consult its documentation for the submission-screen location and required permissions.

If you cannot see the Plugins menu, ask an administrator to perform these checks. WordPress roles and plugin permissions determine which screens are visible; being able to edit pages does not necessarily mean you can read form submissions.

Do not install a second storage plugin or change settings simply because you cannot find the first one. Confirm the existing setup with the person responsible for the site.

3. Locate and open a saved submission

The submission list may show dates, form identifiers, page references, or submitted field values. Available columns depend on the plugin and how the form was configured.

Start with an entry you recognize, such as a recent inquiry or a controlled test submission.

1. Identify the relevant form or page, if the screen groups entries that way.
2. Find an entry using its date or a recognizable field value.
3. Use the entry’s link, row action, or details control to open it.
4. Review the stored fields, such as name, email address, and message.

Some plugins display the submitted values directly in the table rather than on a separate detail page. Follow the interface provided by your installation.

Check the full record before responding

Read the entire message and verify the contact details before passing an inquiry to another team member. A short preview may leave out information that changes how the request should be handled.

Treat submitted content as untrusted. Avoid opening unexpected links or downloading files without following your organization’s security process.

If the displayed time seems wrong, compare it with Settings → General → Timezone and the plugin’s documented timestamp behavior. A timezone difference can make an entry appear outside the period you expected. Do not change the site-wide timezone just to find one message.

4. Filter or search for the entries you need

As the archive grows, browsing every row becomes impractical. Use the controls your plugin actually provides; search and filtering options vary by version.

Possible controls include a form selector, date range, keyword search, or sorting by a column heading. Not every Divi database plugin includes all of these.

For a focused search:

1. Select the relevant form, if that option exists.
2. Choose a date range broad enough to include the expected submission.
3. Search for a distinctive value, such as an email address, if supported.
4. Apply the filters and check any additional result pages.

If you get no results, clear the filters and try again with fewer restrictions. An incorrect form selection or narrow date range can hide a valid entry.

A browser’s Find command searches only text currently loaded on the page. It does not search the entire submission database or entries on other pages.

5. Export submissions when the plugin supports it

An export can help with follow-up, reporting, or transferring inquiries into another approved system. Look for an export or download control in the submission area and check the plugin documentation if its purpose is unclear.

Before exporting:

1. Decide which records and fields you actually need.
2. Apply relevant filters, if supported.
3. Check whether export uses those filters, selected rows, or the entire archive.
4. Download the file and verify its contents.

Do not assume that the rows currently visible are the only ones included. Check a few records and the total scope before sharing the file.

Handle CSV files carefully

If the plugin exports CSV, you can open it in a spreadsheet application. Import phone numbers and other identifiers as text when necessary so leading zeros are not lost.

Visitor-supplied values can also be interpreted as spreadsheet formulas. Be cautious with fields beginning with formula-significant characters such as = and use your organization’s safe import procedure. Do not enable unexpected prompts or external connections.

Store exports in an approved, access-controlled location. Avoid leaving customer information on a shared computer, and remove temporary copies when they are no longer needed.

If your plugin has no export function, ask your site maintainer about supported alternatives. Direct database access is not necessary for routine submission review and should not be your first workaround.

6. Troubleshoot missing submissions

An empty list does not prove that nobody submitted the form. Work through the likely causes before drawing that conclusion.

Confirm the form is supported

A page built with Divi can contain forms from other plugins or embedded third-party services. A plugin that records Divi Contact Form submissions may not capture those forms.

Check which tool powers the specific form, not just which builder created the page.

Run a controlled test

Open the live form in a private browser window and submit a clearly labeled test using non-sensitive information. For example:

Name: Website Test
Message: Storage check, please ignore this test inquiry.

Use an email address you control if the form requires one. Confirm that the form reports a successful submission, then return to WordPress, clear filters, and refresh the submission list.

Check the database entry and notification email separately. Email delivery and database storage are distinct checks: success in one does not prove success in the other.

Escalate with useful details

If the test is missing, give your site maintainer the page URL, test time, plugin name and version, and any visible error. Ask them to check compatibility, configuration, and relevant logs.

Avoid deactivating plugins or switching themes on the live site as an initial troubleshooting step. Test potentially disruptive changes on staging with a current backup available.

Keep submission access and retention under control

Form entries can contain personal or confidential information. Limit access to people who need it, use individual accounts, and avoid forwarding complete exports when a single inquiry will do.

Agree on a retention policy instead of keeping every entry indefinitely. Before deleting records, confirm that any necessary follow-up is complete and that the deletion is authorized. Do not assume the plugin offers a recoverable trash area.

Also remember that exports and backups may contain copies of deleted entries. Include those copies in your organization’s data-handling process.

Takeaway

To review Divi DB submissions, log in to the correct WordPress site, find the installed plugin’s submission screen, and open the relevant records. Use available filters and exports carefully. If an entry is missing, verify permissions, form compatibility, and storage with a controlled test rather than relying on email notifications alone.