Squad Modules Lite

New

• Every form styler can now style three areas that previously had no settings at all: the grid that spaces the fields apart, the footer holding the submit button, and select fields on their own. The gap between fields belongs to the grid containing them and the space above the submit button belongs to the footer, so neither could be reached by adjusting the fields themselves. Available across all nine stylers — Contact Form 7, WPForms, Gravity Forms, Ninja Forms, Fluent Forms, Forminator, Formidable, MetForm and SureForms — in both builders and the Visual Builder preview.
• Gravity Forms gained controls for elements that were previously unstyleable: the next, previous, save-and-continue and file-upload buttons, the image-choice field, and the per-field validation message.
• Contact Form 7, WPForms, Fluent Forms, Formidable, Forminator, MetForm, SureForms and Ninja Forms gained a per-field validation message background, margin and padding.
• Divi 5’s Gravity Forms styler gained the design controls the Divi 4 one already had: form title, form description, field descriptions, sub-labels, the required indicator, section breaks with their titles and descriptions, and complex fields such as name and address.

Bug fixes

• The Divi 5 modules disappeared from the Visual Builder module library, loaded without any styles, or failed to build at all. The builder bundle is fixed so every module registers and its stylesheet loads in the builder and frontend.
• Gravity Forms styler: none of the design settings had any effect on most forms. The selectors no longer depend on which form theme is active.
• The form pickers in the Divi 5 builder listed no forms and could show “Oops, an error has occurred”; the available forms are now sent in time and the placeholder option no longer appears selected.
• The Divi 5 design sections for the Gravity Forms styler did not appear in the builder; all twenty now appear.
• Gravity Forms: the Field Elements toggle appeared with duplicated sub-tabs; the module’s definition now replaces the base one.
• Ninja Forms: the submit button’s design settings now match both <input> and <button> submit elements.
• MetForm and SureForms: the validation and error message controls are split into the per-field message and the form-level response.

Bug fixes

• Hover Box produced a fatal error instead of rendering in the classic Divi builder. It referenced one of Divi’s own classes without importing it, so PHP looked for that class inside the module’s own namespace and stopped with “Class not found” as soon as the module tried to output its overlay styles, which happens on every render.
• The Gravity Forms styler could stop the Divi 5 builder loading a form, showing “Oops! An Error Has Occurred. This content could not be displayed.” It captured the form with an output buffer, and if Gravity Forms failed while producing the form the buffer was left open, so stray output reached the builder and it could not read the response. The form is now requested directly, the way the Divi 4 module has always done it.
• Post Grid could take a page down. Its post-element filters passed the post object where the markup belonged, so any other plugin hooking them received the wrong type and crashed the page — WordPress’s own text formatting was enough to trigger it. The filters now pass the markup, with the post alongside it as context.
• With both Post Grid and Post Carousel enabled, every post element was rendered twice, once by each module. Each module now renders only its own output.

Improvements

• The gallery image helper was duplicated once per builder; it is now a single shared class.
• Documentation accuracy: several files still said Post Carousel was Divi 5 only and that 64 of the 65 modules ran in Divi 4. All 65 have run in both builders since 4.6.0.
• Post Carousel was missing from the WPML configuration, so its attributes were invisible to translation tooling.

Internal

• The code quality checks that had been switched off in CI are running again. PHP coding standards, static analysis and the PHP test suite were all disabled, so none of them had run against any change.
• Style and script linting could not report problems without also rewriting files, because both commands had the fix flag built in. Each now has a separate check and fix command. Turning checking on surfaced 958 stylesheet problems and 320 script problems that had been passing silently; all of them are resolved, and several were rules configured to contradict each other rather than faults in the code.
• Divi 4 preview components no longer nest conditional expressions several levels deep, and three of them declared their render method after private helpers. A shadowed variable and a stale module path in the type declarations are also fixed.

New

• Post Carousel is now available in the classic Divi builder. It previously existed only for the Divi 5 Visual Builder, so enabling it in Divi 4 appeared to do nothing. It shares Post Grid’s query and post elements, so every element type, icon and design option carries over.

Bug fixes

• Converting a Divi 4 layout to Divi 5 silently changed heading tags: Business Hours became a span, Flip Box titles became h3, Flip Box subtitles became a div, and the Advanced Divider’s text became a span. Those modules now expose the same heading-tag control in both builders, and a converted layout keeps the tag you chose.
• The uninstall routine has never run for anyone: uninstall.php was excluded from the released package, so removing the plugin left its options, transients and custom table behind.
• Modules that only work in one builder are now labelled, and the switch is disabled when your site cannot use them, instead of turning on with no visible effect.
• Button settings on Flip Box and the nine form stylers exposed a stray control created by a mis-nested field definition.
• The packager rewrote a date inside the changelog on every build.

Improvements

• Builder detection now asks Divi directly whether Divi 5 is enabled, so sites that deliberately run the classic builder are treated correctly.
• Accuracy pass over the bundled documentation: several files still described the previous release, and one told contributors to edit a generated file.

Internal

• Coding standards now check the module code. A pattern intended to skip node_modules was also skipping every Divi module, leaving 189 of 327 PHP files unchecked; the 522 issues that surfaced are fixed, including two double-escaped values in the login and lost-password forms.
• Divi modules can now be built inside the test suite, so field definitions are actually executed rather than only inspected. This immediately caught the button-field defect above.

Bug fixes

• Divi 4 parent modules now render their child shortcodes correctly under the latest Divi, fixing timelines and other nested modules that showed raw [disq_*] text on the front end and in preview.
• Inline Content: the Divi 4 item module had no settings and produced no output, so the whole module was blank. It now renders all five content types (text, icon, image, button, divider) and matches the Divi 5 output exactly.
• Logo Grid and Logo Carousel: column count, gap, logo sizing and every hover effect (grayscale, opacity, zoom) never reached the page in Divi 5. They now apply.
• Image Mask: the Divi 5 decoration layers rendered with no fill colour.
• Social Share: every share button linked to an empty target, “Icon + Text” never showed labels, and a second module on the page inherited the first one’s link.
• Heading level controls in Social Share, Step Flow and Team Member changed the text size but never the heading tag, producing a document outline the author did not choose.
• Post Grid: the Advanced Custom Field element bypassed ACF’s own value formatting; the Comments “Before Text” setting was permanently empty; pagination labels containing & were double-escaped.
• Dual Button: the alignment control did nothing in vertical layout.
• Star Rating: the default star size was ignored, and the review schema markup was malformed.
• Author Box: choosing the SPAN tag silently rendered an H4; avatar alt text was double-escaped.
• Divider, Business Hours, Flip Box: heading tag settings could resolve to an empty value and remove the element entirely.
• Timeline Item and Logo Carousel Item: border and radius settings never appeared in the builder.
• Lottie, Business Hours, Post Reading Time, Image Mask: several settings targeted elements the modules never output, so they had no effect.
• Google Maps (Divi 5): the module script was not enqueued and errors were silent.
• Contact Form 7, Fluent Forms, Formidable, Forminator, Gravity Forms, Ninja Forms, MetForm, SureForms, WPForms: a module added without a form selected produced a PHP warning; the Field Label typography control had no effect; Ninja Forms fired the wrong hook.

Security

• Gradient Text and Glitch Text now validate the wrapper tag and effect name against a strict allowlist instead of trusting the stored value.
• Flip Box buttons that open in a new tab include rel="noopener".
• REST endpoints no longer return raw exception messages.
• Extensions that are disabled can no longer load because of a faulty guard.

Improvements

• Divi 5 modules now register their per-instance CSS through Divi’s native style pipeline instead of writing an inline <style> tag per module, so the CSS takes part in Divi’s critical-CSS and deduplication.
• Design settings that are marked responsive now work on tablet and phone, where previously only the desktop value was ever used.
• New v4 plugin icon and icon set.
• Accessibility: decorative icons are hidden from screen readers, icon-only video triggers have labels, and empty avatar wrappers are no longer emitted.

Security

• Breadcrumbs schema output now escapes the home URL with esc_url().
• Visual Builder button previews add rel="noopener noreferrer" to links that open in a new tab.
• Hardened admin-script JSON parsing against malformed data.

Bug fixes

• Fixed a fatal error that could leave WordPress admin pages blank when another plugin passed a non-string value through the admin footer text filter (a strict return-type mismatch on PHP 8).

Improvements

• Confirmed compatibility with Divi 5.9.0.
• Network-aware uninstall now removes plugin data across all sites when the plugin is uninstalled on a multisite network.