Troubleshooting

Common issues when developing Divi Extensions and how to triage them.

Module doesn't appear in the visual builder

Check in order:

1. JSX compiled? yarn start must be running. If you haven't run it since the latest JSX change, the visual builder is loading stale code.
2. Slug match? The slug static property in the React class must exactly match the slug returned by the PHP module's get_name() / init(). A mismatch silently drops the module from the builder.
3. Registered in includes/modules/index.js? The auto-registration of modules happens through this file. If your import/export is missing, the module is invisible to the runtime.
4. PHP errors? Open the PHP error log. A fatal in the module's PHP class blocks the whole extension from loading.

Settings tab is empty

• get_fields() returned an empty array. Verify the method has a return statement.
• Settings were added to a tab_slug / toggle_slug that doesn't exist. See Module Settings Groups for the valid slugs.

show_if rule has no effect

Per Settings Field Visibility:

• The referenced setting must exist in get_fields().
• The expected value is compared as a string, not a typed value.
• show_if_not and show_if are mutually exclusive on a single field.

Custom CSS field doesn't show in the Advanced tab

Per Defining Custom CSS Fields For Modules:

• The CSS selector must point at an actual element your module renders.
• The slug of the CSS field must be unique within the module.

yarn start errors out

• Make sure you're on the LTS NodeJS — newer Node majors can break older create-divi-extension tooling.
• Delete node_modules/ and yarn.lock, then yarn install again.

Cross-references

• Full environment requirements: Divi Development Environment.
• Compatibility flags that affect which features you can use: Compatibility Levels.