How a page is checked

Divi ignores settings it does not understand, and it does not tell you. A page can save without an error and still come out wrong. MCP for Divi 5 checks every page in four steps to catch that.

1. Validate before saving

The structure is checked before anything is written. Divi 5 pages nest as section, then row, then column, then modules.

These errors stop the save, so nothing broken is written:

• a module that is not on your site
• a top level that is not a section
• a module that is not inside a column
• a column that is not inside a row

These warnings do not stop the save, but the tool gets them and can fix them:

• a setting group the module does not have, which Divi would ignore
• child modules inside a module that does not take them
• button padding in the wrong place
• rounded corners set with all, which Divi does not apply
• a gradient without enabled set to on, which would not show
• spacing written as a string, which is converted to the shape Divi needs

2. Save

The page is saved as a draft unless the tool is told otherwise. Replacing an existing page keeps the old version in WordPress revisions.

3. Read back

The saved page is read again and compared with what was sent. If they differ, a content filter changed it on save. The usual cause is a user without the unfiltered_html capability, which strips scripts, styles and some settings. Use an account that has it, or ask your site admin.

4. Render check

The page is rendered the way visitors see it, and any module that produced no markup is listed. The same check can run later on any saved page. It also reports unknown blocks, stray HTML between blocks and settings Divi will ignore.

The render check does not judge nested content or looks. After the checks pass, still look at the page.