Squad Modules Lite

Breaking

• The MetForm form styler has been removed. MetForm builds its forms for Elementor, so a MetForm form in a Divi page is an Elementor document with its own per-form CSS that the styler could not win against, and its fields are Elementor widgets rather than form fields. The module had also stopped registering against current MetForm. It was off by default, so this only affects sites that turned it on.

New

• Form stylers for , and , in both builders — bringing the library to 67 modules and 11 form stylers.
• Every module now carries an icon drawn for it, and the eleven form stylers show their plugin’s own brand mark.
• Post Grid and Post Carousel show real posts while you edit, and let you pick categories and tags from a list instead of typing comma-separated IDs.
• The form stylers show the real form in the Visual Builder, drawn by the same code that renders it on the page.
• Charts are authored in a data table rather than three text boxes that had to agree with each other.
• Divi 5 modules gained four option groups Divi provides for its own modules — Interactions, Scroll Effects, Sticky and Transform — plus the module-level Link option on 39 modules.
• Divi 5 caught up with the classic builder across seventeen modules. Advanced Divider, Flip Box, Typing Text, Dual Button, Post Grid’s Load More, Business Hours, Post Reading Time and the form stylers all gained settings that existed in Divi 4 and had no counterpart, including per-side element styling, text fill and clipping, icon layout, divider lines, and hover-revealed and image button icons.
• Every form styler can colour and size its checkboxes and radios, and seven more can style the message shown against a field that failed validation.
• The Checkbox and Radio size setting now actually resizes the control.
• The Forgot Password and Reset Password switches on the Extensions page now do something.

Bug fixes

• Every form styler’s Design tab did nothing in the Visual Builder. A module renders its CSS twice — once for a saved page, once for the builder’s canvas — and the canvas rendered only the module’s own group, so of Gravity Forms’ 33 design groups the builder drew one. Colours, typography, spacing, buttons and messages were visible only after saving. Seventeen further modules had the same split, and the reverse case left thirteen modules’ settings off the page entirely.
• Advanced Button and Hover Box could not be used in the Visual Builder at all: both were replaced by Divi’s error panel, so neither could be placed, selected or edited, while a saved page rendered them correctly.
• A module’s own links ignored every typography and colour setting. A shared reset marked seven properties !important on every link inside a module, which beats specificity, so on the 13 modules using it any setting for a link-based element did nothing.
• Twenty-two of the Gravity Forms styler’s thirty-one design sections produced no CSS at all, and several others were overruled by the plugin’s own default styling or painted elements belonging to another section.
• Forms styled by this plugin reached visitors unstyled, because the form plugin’s own stylesheet was loaded only while the Visual Builder was open.
• Converting a page from the classic builder dropped settings the modules already had, and turned icons, spacings, ratings, colours and flip directions into shapes Divi 5 does not read.
• Dynamic content — a post title in a button, an author name in a heading — printed its raw placeholder instead of the value, on the page and in the builder.
• Images, Lottie files, videos and icons chosen in a Divi 5 module could render as the literal word “Array”.
• Applying a saved preset to a Divi 5 module could overwrite text, links and images on the module you applied it to, and a preset saved from a form styler applied its button styling twice.
• Post Grid and Post Carousel filtered by one tag when several were chosen and showed every post when set to the current category; Post Grid’s Load More button never appeared at all.
• The Divi 5 Star Rating always wrote an <h2>, breaking heading order, and the Number Counter gave its image an empty alt attribute with no way to set one.
• Duplicating a post kept only the first value of any meta field stored across several rows.
• Uploading an SVG consisting only of a DOCTYPE declaration reached the XML parser as an empty string.
• Ninety-nine design settings across twenty-nine modules were filed as content rather than design, so presets and Copy Module Styles carried the wrong things.
• Eight classic-builder modules and four Visual Builder previews drew something other than their content, and a form styler that hit an error vanished from the builder with no explanation.

Internal

• The JavaScript side of the build is now checked in CI: ESLint, Stylelint, the type check and Jest all run, none of which ran before. Stylelint went from 958 errors to zero and ESLint from 320 problems to zero.
• The type check had been passing while examining no code at all, and fifteen JavaScript test suites had been failing to compile rather than failing to pass.
• Five suites now render the modules rather than reading their metadata, and the design suites ask the browser which rule won rather than trusting the emitted CSS.
• Fifty development dependencies are gone from the install, and the toolchain no longer straddles two major versions of Babel.
• The compatibility layer kept for the class names retired in 3.3.3 has been removed.

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.

• Older releases are listed in changelog.txt, which ships with the plugin and is the full record.