Divi 5 runs Divi 4 modules it can’t convert in backwards compatibility mode. They load Divi 4’s engine, make the page slower and need a reload to edit, and they can sit in the page, its header or footer, or a Component, where they’re hard to find. Legacy Modules lists every one that shows on a page, where it is, why it’s legacy and what to do about it.
What a legacy module is
When Divi 5 converts Divi 4 content, a module it can’t turn into a Divi 5 module is kept in its Divi 4 form, and Divi 4’s engine runs it on the page. In the Visual Builder, Divi calls these legacy modules. A module ends up legacy when:
- it comes from a plugin or child theme that has no Divi 5 version;
- it’s a Divi module with settings Divi 5 can’t convert, usually added by a Divi 4 extension;
- it’s a Divi 4 module that Divi 5 doesn’t convert;
- the content was never converted, so it’s still saved as Divi 4 shortcodes.
Legacy Modules is part of Diagnostics, so it’s read-only and there’s nothing to switch on. It needs Divi 5. On Divi 4 the tab says so, because there every module is a Divi 4 module.
What it scans
Give Legacy Modules a page ID and it reads everything Divi shows on that page:
- The page itself. Posts and other content types work the same way.
- Its Theme Builder layouts: the header, body and footer Divi uses for that page. Areas that are switched off in the template are skipped.
- Components used in any of these, and Components inside those Components. Only published Components are scanned, because Divi only shows published ones.
- Off-canvas panels that belong to the page or to its Theme Builder layouts.
You can also enter the ID of a Theme Builder layout, an off-canvas panel or a Divi Library item to scan only that, with the Components it uses.
Run a scan
- Find the ID of the page. In Pages → All Pages, hover over the page title: the edit link in your browser’s status bar contains
post=followed by the ID. - Go to Divi Doctor → Diagnostics → Legacy Modules.
- Enter the ID in Page / post ID and click Find legacy modules.
If nothing has that ID, the result is marked Issue with not found and No post, page or layout with this ID. The quicker way to a scan is the toolbar count, below: it opens the scan for the page you’re on.
The toolbar count
While you’re logged in as an administrator, open a page of your site. If Divi ran any Divi 4 module on it, the WordPress toolbar at the top of the page shows Legacy modules: N. Pages without legacy modules don’t show it. Hover over the item to see how many modules Divi ran in backwards compatibility mode and their shortcodes. Click it to open Legacy Modules with the scan for that page already run.
- Only administrators see it, and only on the front end of a Divi 5 site, not in the Visual Builder. Visitors never get it, and it doesn’t change the page.
- On a view that isn’t a single page or post, such as a blog archive, the link opens Legacy Modules without an ID.
- The number counts every Divi 4 module Divi ran on that view, including the items inside a module, such as each slide of a Divi 4 slider. That’s why it can be higher than the number of rows in the scan, which lists each legacy module once.
- While it counts, Divi Doctor also notes which plugin or theme registers each Divi 4 module, so the scan can name it. See Which plugin adds a module.
To hide the toolbar item, see For developers.
Read the results
The results start with Scope, which says what was read:
| Row | What it shows |
|---|---|
| Theme Builder | How many layouts Divi uses for the page and the template they come from, for example 3 layout(s) from "All Pages". none (this page uses the theme’s own header and footer) means no Theme Builder layout applies. This row isn’t shown when you scan a Theme Builder layout itself. |
| Scanned | How much was read, for example 5 post(s): the page, 3 Theme Builder layout(s), 1 Component(s), 0 off-canvas panel(s). |
| Limit | Only shown when there was more to read than one scan covers: a scan stops after 80, and this row says how many weren’t scanned. |
If nothing runs in backwards compatibility mode, you see No legacy modules and Nothing on this page runs in backwards compatibility mode. Otherwise the heading counts what was found, such as 3 legacy items, and a table lists each one:
| Column | What it shows |
|---|---|
| Where | The post it’s in, with its type, title and ID, for example Page "About" #20, Theme Builder footer "Main footer" #45 or Component "Newsletter" #88. Below that, the place inside it, such as Section 2 › Row 1 › Column 1. Admin labels you’ve given sections, rows and columns are shown in brackets. Top level means the module isn’t inside a section, and Whole layout means the whole post is still Divi 4 content. Then an Edit link. |
| Module | The module’s name and Divi 4 shortcode, for example Text (et_pb_text). For a module Divi 5 doesn’t have, a From line can name the plugin or theme that adds it. |
| Why it is legacy | The reason. See the next table. |
| What to do | The fix for that reason. |
The Edit link goes where you can edit that post: the page’s edit screen, Divi → Theme Builder for a Theme Builder layout, the Visual Builder of the page an off-canvas panel belongs to, or the Divi Library edit screen for a Component. A global off-canvas panel that belongs to no page has no link.
Why a module is legacy
| Why it is legacy | What to do |
|---|---|
| A Divi 4 module from a plugin or child theme that has no Divi 5 version. | Update the plugin that adds it to a Divi 5-ready version, or replace it with a Divi 5 module. |
| A Divi module with settings Divi 5 can’t convert, followed by the names of those settings. A Divi 4 extension added them, so Divi keeps the whole module in Divi 4 form. | Update that extension to a Divi 5 version, or delete the module and add it again as a Divi 5 module without those settings. |
| A Divi 4 module kept in Divi 4 form, though Divi 5 has this module. | Delete the module and add it again as a Divi 5 module. |
| A Divi 4 module that Divi 5 doesn’t convert. | Replace it with a Divi 5 module. |
| This content is still saved as Divi 4 shortcodes, so Divi runs all of it with its Divi 4 engine. Where says Whole layout, and Module lists the Divi 4 modules in it. | Open it in the Visual Builder, which converts it to Divi 5, and save. Check the result before you publish. |
| A legacy module whose shortcode could not be read. | Open the layout in the Visual Builder and look for modules marked “Legacy”. |
Which plugin adds a module
For a module Divi 5 doesn’t have, the Module column adds From: and the plugin or theme that registers it, for example Example Modules (plugin). Divi Doctor learns this on the front end, when it counts the module for the toolbar. If the From line is missing, do what the note under the table says: open the page while logged in as an administrator, then run the scan again.
Fix a legacy module
- Click Edit under the post named in Where. For a Theme Builder layout, open the layout from Divi → Theme Builder.
- In the Visual Builder, go to the section, row and column from the path.
- Follow What to do: update the plugin that adds the module, or replace the module with a Divi 5 module.
- Save, then run the scan again, or reload the page and check the toolbar count.
Note: A Component shows on every page that uses it. A legacy module inside one shows up in the scan of each of those pages, and fixing it in the Component fixes all of them.
Limits
- Legacy Modules and the toolbar count need Divi 5.
- One scan reads up to 80 posts, including up to 50 off-canvas panels.
- The scan reads the content as it’s saved, while the toolbar counts what Divi ran on one view. The two numbers can differ.
- The From line only appears for modules Divi Doctor has seen on the front end.
For developers
To hide the Legacy modules toolbar item, use the ddoc_bcm_admin_bar filter, for example in a code snippets plugin or your child theme’s functions.php. The Legacy Modules screen shows the same line.
add_filter( 'ddoc_bcm_admin_bar', '__return_false' );
With the item hidden, Divi Doctor no longer counts modules on the front end, so it can’t learn which plugin adds a module and the From line stays empty.
Questions
What are legacy modules in Divi 5?
Legacy modules are Divi 4 modules that Divi 5 couldn’t convert, so it keeps them in their Divi 4 form and runs them in backwards compatibility mode. They load Divi 4’s engine, make the page slower and need a reload to edit. A module ends up legacy when it comes from a plugin or child theme with no Divi 5 version, has settings Divi 5 can’t convert, or is still saved as Divi 4 shortcodes.
How do I find which modules run in backwards compatibility mode in Divi 5?
Go to Divi Doctor → Diagnostics → Legacy Modules, enter the page’s ID in Page / post ID and click Find legacy modules. The scan reads the page, its Theme Builder header, body and footer, the Components it uses and its off-canvas panels. Legacy Modules is part of Divi Doctor, a plugin for Divi 5. It’s read-only, so there’s nothing to switch on.
How do I fix a legacy module in Divi 5?
Follow the What to do column in the scan. Click Edit under the post named in Where, go to the section, row and column from the path, then update the plugin that adds the module or replace the module with a Divi 5 module. Content still saved as Divi 4 shortcodes is converted when you open it in the Visual Builder and save. Then run the scan again.
What does the Legacy modules count in the WordPress toolbar mean on a Divi 5 site?
It’s the number of Divi 4 modules Divi ran in backwards compatibility mode on the page you’re viewing. Only administrators see it, and only on the front end of a Divi 5 site. Click it to open Legacy Modules with the scan for that page already run. It can be higher than the scan’s row count, because it counts the items inside a module, such as each slide of a Divi 4 slider.
How do I hide the Legacy modules item in the Divi 5 admin toolbar?
Use the ddoc_bcm_admin_bar filter, for example add_filter( 'ddoc_bcm_admin_bar', '__return_false' ); in a code snippets plugin or your child theme’s functions.php. With the item hidden, Divi Doctor no longer counts modules on the front end, so it can’t learn which plugin adds a module, and the scan’s From line stays empty.
Related pages
- Site checks, Exception Watch and hosting: the other Diagnostics tabs.
- Page Scan: find the CSS field that broke a page’s styling.
- Request Profiler and Site Weight: see where the time goes when a page is slow.