Divi Plus 2.0.1 – WordPress Plugin

Divi Plus is an expansion plugin for Divi Builder. Its whole purpose is to give Divi more modules, more template options, and more design controls without switching themes or rebuilding sections with custom code. I use it on sites that are already committed to the Divi ecosystem and need extra content modules, fancy layouts, filters, timelines, hotspots, carousels, image effects, or WooCommerce-oriented design blocks.

It is useful for marketing sites, agency builds, portfolios, course pages, and brochure-style business sites. It is much less interesting if the project already feels overloaded, because adding “more Divi” can also mean adding more CSS, more JS, and more places for performance issues to start.

How it works in real projects

Divi Plus is a plugin layer on top of Divi. The main logic usually works like this:

• it registers extra Divi modules;
• those modules become available inside the Divi Builder;
• each module stores its settings in the page/post content data;
• frontend CSS and JS are loaded to render sliders, grids, hotspots, galleries, filters, and other interactive elements.

So most edits happen in the builder, not in PHP files:

• module content;
• spacing, colors, animation, layout controls;
• responsive behavior exposed by module settings;
• page-level structure inside Divi layouts.

The hardcoded side is the plugin’s module code, frontend assets, and whatever render callbacks power those modules. In practical terms: styling and content are easy; changing module behavior at a deep level is not.

Where it usually breaks

The most common failure is not Divi Plus itself. It is the combination of:

• Divi;
• Divi Plus;
• performance plugins;
• sometimes Cloudflare or server-level caching;
• and a page trying to do too many animations at once.

Typical symptoms:

• modules render in the builder but look broken on the frontend;
• carousels or sliders stop moving;
• filterable grids do nothing when clicked;
• hotspots, image effects, tabs, or popups fail after JS optimization;
• layout spacing looks different between logged-in and logged-out views.

My check order is simple:

1. Open DevTools → Console
   Look for JavaScript errors first. If one module script crashes, several Divi elements can look “randomly broken.”
2. Check Network
   Make sure Divi and plugin assets are actually loading on the affected page.
3. Temporarily disable JS delay/defer/minify
   Especially if the issue involves:
   • sliders
   • tabs
   • filters
   • popups
   • hover/animation-heavy modules
4. Purge all cache layers
   Divi sites often hold onto stale CSS longer than expected.

If optimization is the cause, I usually exclude the obvious foundations first:

• jquery
• jquery-core
• Divi frontend scripts
• Divi Plus frontend/module scripts if your optimizer lists them separately

That is usually enough to confirm whether the break is a script-loading issue or a real plugin conflict.

Performance reality

Divi Plus can save time, but it is not free in performance terms. Every extra module system increases the chance of:

• larger CSS bundles;
• more frontend JS;
• layout shift from animation-heavy sections;
• slower editing on long pages.

So I treat it like a toolbox, not a buffet. If a page needs three enhanced modules, fine. If it needs twenty animated ones, the site usually starts feeling heavier than it should.

Best results come from:

• using only the modules actually needed;
• avoiding stacked animation effects;
• testing mobile separately;
• not combining aggressive optimization with untested interactive modules.

Updates, licensing, maintenance

Because this is a premium plugin, the clean path is simple: keep it properly licensed if you want official updates, support, and vendor access.

Manual updates are standard WordPress work:

• upload the new ZIP via Plugins → Add New → Upload Plugin, or
• replace the plugin folder over FTP/SFTP.

As with most builder add-ons, do not edit the plugin files directly. If you patch CSS or JS inside the plugin, the next update will wipe that work. Put custom CSS in Divi theme options, a child theme, or your site’s custom stylesheet instead.

When I would use it

I use Divi Plus when:

• the site is already built on Divi;
• the client wants richer modules without custom development;
• the extra modules solve a real design problem.

I avoid it when:

• the build is already slow;
• the page relies on too many third-party Divi extensions;
• the site needs long-term simplicity more than extra effects.

That is the honest tradeoff: more module power, but also more moving parts.

FAQs (the stuff people actually trip over)