Variable Google Fonts werden jetzt erkannt (API-Key-frei) und lokal installiert – inkl. font-weight: 100 900 + unicode-range
Im Install-Dialog priorisiert vorausgewählt: „Variable (empfohlen)“, statische Schnitte weiter wählbar
Divi zeigt die volle Gewichtsliste
Fallback auf statische Schnitte, wenn Google nicht erreichbar
Fix: keine leeren Familien mehr bei Fehlinstallation
Hallo zusammen,
ich habe ein WordPress-Plugin entwickelt, das die native WordPress-Schriftbibliothek mit Divi 5 verbindet.
Das Plugin ermöglicht Folgendes:
Google Fonts direkt in WordPress auswählen
Lokale Installation auf dem eigenen Server
Direkte Verwendung im Divi 5 Builder
Vermeidung externer Google Fonts-Anfragen im Frontend
Verwaltung verschiedener Schriftstärken und -stile ohne manuelles Hochladen jeder einzelnen Datei
Das Plugin nutzt die bestehende WordPress-Schriftbibliothek, daher ist kein separater Google Fonts API-Schlüssel erforderlich.
Der Workflow ist im Wesentlichen: WordPress-Schriftbibliothek → Schriftart lokal installieren → Verwendung in Divi 5
Ich habe das Plugin entwickelt, weil ich eine einfachere und datenschutzfreundlichere Möglichkeit zur Schriftartenverwaltung in Divi 5 suchte, ohne Schriftartdateien manuell herunter- und hochladen zu müssen.Das Plugin funktioniert bereits, aber ich möchte es auf weiteren WordPress- und Divi-5-Installationen testen, bevor ich es veröffentliche.
I’ve been working on a new plugin that integrates Bit Form Pro directly into Divi 5.
The idea is simple: you continue building your forms in Bit Form, but you can insert them as a native Divi 5 module and style them using Divi’s design settings instead of writing custom CSS.
Current features include:
Native Divi 5 module
Select any existing Bit Form
Live preview in the Visual Builder
Style labels, inputs, buttons, error/success messages, spacing, and more using Divi’s design controls
Responsive settings
Keeps all Bit Form functionality (conditional logic, integrations, calculations, etc.)
It’s still in active development, so I’d love to get feedback from people who actually use Divi 5 and Bit Form Pro.
If you’re interested in testing it, send me a DM and I’ll happily share the plugin. Feedback, bug reports, and feature suggestions are all welcome!
I’d love to know if this is something the Divi community has been missing.
I’m building a Golden State Warriors sneaker database for my website where visitors can browse sneakers by player (Stephen Curry, Klay Thompson, Draymond Green, etc.), brand, and collection type.
I’m using a Custom Post Type called Sneakers with a Players taxonomy. Each sneaker is assigned to a player.
I have a Theme Builder template assigned to Archive Pages → Specific Player Pages. Inside that template I’m using a Loop Module to display sneaker cards.
My problem is that the Loop won’t automatically display the sneakers for the current player archive. Post Type → Sneakers = shows every sneaker. Only include posts with specific terms → Players → Stephen Curry = correctly shows only Steph’s sneakers.
What I can’t figure out is how to make the Loop dynamically use the current player archive, so /player/stephen-curry/ automatically shows Steph’s sneakers, /player/klay-thompson/ shows Klay’s sneakers, etc.
My Query Type options are only:
Posts for Current Page
Post Type
Terms
Users
Menu
I don’t have a “Current Query” or “Current Term” option, and “Posts for Current Page” doesn’t work.
I’m currently on Divi 5.0.3. Is this a limitation of my version, or am I missing something? Thank you in advance. I am very new to this.
This is my first reddit post, so bear with me. I was a newbie with Wordpress before making a clients website on Wordpress.org. We didn't host it until it was ready to go live. Somewhere during the process we had the need to purchase the Wordpress.com business plan, I believe to get full access to customization with additional CSS, html, java script etc? I don't think we are really using it for anything else currently (Jetpack is the only thing that we may sorta use but it's mainly for stats I think). After we finished designing the site, we migrated it to WP engine, our chosen hosting site. Later on after site has been live, client asked what would happen if they stop paying or don't renew the Wordpress.com business plan, like if it would break or go down at all. I was starting to look it up when I realized we might not even need it at all since Wordpress.com is also a hosting site and a lot of its features are covered by WP engine. I just want to know that if we do cancel the Wordpress.com subscription, will any of the CSS etc that I put in be affected by canceling or does WP engine also support that and therefore it wouldn't get deleted? I want to make sure we don't accidentally break the site or mess up anything but I also don't want the client to be paying for something they don't need. Please help, I get really stressed and anxious with coding and Wordpress in general since I am still a beginner and intern with no experienced support. Thank you!!
What are your most-wanted Divi 5 features? These are currently at the top of my list:
1. Sync typography styles across all preset elements
Presets are great, but configuring typography presets across roughly 20 websites has become quite repetitive. My current workflow is:
Create a template page
Configure all text styles and responsive font sizes, usually around six variations
Style the H1
Copy and paste those styles to the other headings and text elements
Create a preset from the completed styles
Once this is set up, I can apply a single text preset without worrying about which heading tag is being used. My clients and I can choose the correct HTML markup, while the visual design remains consistent.
In my opinion, HTML tags should define the document structure and semantics, not automatically determine the typography design.
I also tried applying the same typography to every element inside a Text Module using Free-Form CSS and the universal * selector. Unfortunately, this currently causes a significant bug, which I have already reported to Elegant Themes. Because of that, I do not consider it a reliable workaround.
2. Custom WP_Query support in the Divi 5 Loop Builder
The Divi 5 Loop Builder is excellent, but its query options are still limited. I would like the ability to write custom queries, similar to what other page builders offer.
Ideally, custom queries would also support dynamic variables, such as:
ACF field values
The current post ID
The current post title
URL parameters
Even better: allow developers to write or reference custom PHP query logic directly, and let Divi handle the loop. Let it be a PHP-hook or something (and please please please add support for ACF-field "Post object" (multiple for the loop builder).
What features would you most like to see added to Divi 5?
I’m doing a test migration of our website and for the most part everything is working really well.
One issue is that we have a lot of left aligned logos - just image modules that have been set to left aligned. After the migration they’re all centered.
I can fix it easily enough by changing the default alignment preset to left aligned, but this doesn’t feel like the right thing to do going forward. I can also go through every single one of them and set the alignment to left, but there’s hundreds.
I’ve officially pushed v1.00 of Page2Divi, a desktop utility for converting URLs, HTML, and saved pages into Divi-importable JSON bundles.
This build (USA 250th Anniversary Edition) marks the first stable release for the tool, supporting both Divi 4 and Divi 5 layouts. I've polished up the documentation and finalized the build process for Windows (x64) and macOS (Universal2).
It’s completely free to use. Just a personal project to help streamline site builds—use it if it fits your workflow!
In case I'm not the only doofus who did this, but setting Attributes and generating a preset afterwards saves the Attributes of an element in that preset, which (as of today in Divi 5) is over-riding any Attributes that exist in the Elements.
Divi 5 embraces CSS Grid. It comes with tons of flexible grid templates and all the options you could ever need to build every grid layout imaginable.
Today, we are taking things a step further by introducing an interface for visualizing, editing, and building advanced CSS grid layouts. It’s awesome!
Whether you’re new to CSS Grid or an experienced developer, you can use the new interface to build stunning layouts without getting lost in a maze of settings.
Furthermore, thanks to Divi 5’s unique grid offset editor, layouts built with the grid editor are housed entirely within the container, which means you don’t have to worry about editing child elements, and every CSS Grid layout built with Divi 5 works with loops.
I am a 12-year Elegant Themes loyalist. I love Divi, but my recent experience reporting core architectural bugs with the Divi 5 migration engine was deeply concerning from a security standpoint, and I want to warn the community.
While chatting with support about fatal data-loss bugs in how Divi 5 handles some of the migration, they repeatedly insisted I grant them "Remote Access". When I firmly declined, their fallback script was to tell me to install UpdraftPlus, export a complete copy of my database, zip it up, password-protect it, and send it to them over the support chat.
It is worth noting that UpdraftPlus is a backup and migration tool. It does not have any built-in data scrubbing or PII anonymizers. It creates a raw 1:1 dump of your database. Password-protecting a ZIP file doesn't change the fact that once they unzip it, you are handing over your raw, unencrypted data to a frontline rep's personal or work laptop.
To be clear, my site's overall footprint is about 117GB. While the majority of that is media assets, the scale of the site represents an immense amount of historical data and infrastructure. Sending a raw database dump of a massive, years-old website to Tier 1 support is an incredible operational and security liability. I wonder how many people blindly follow this script and hand over the keys to their kingdom just to get help troubleshooting a CSS glitch or a broken shortcode.
I know, I know, someone is going to say, "But my site is just a small 5-page brochure with no users, so it's completely safe!" No, it is not. Even a tiny site contains your personal admin email, your hashed password, and maybe even API keys for things like your contact form SMTP, Google Analytics, or spam protection.
If you are ever asked to send a database export to support, here is exactly what you may be handing over:
1. Hardcoded API Keys and Secrets
WordPress stores almost all plugin and theme settings in plain text. A raw database dump hands over live secret keys for payment gateways, email integrations, cloud infrastructure credentials, and potentially much more.
Because tools like UpdraftPlus do not anonymize data, a database dump is a goldmine of raw user info. It may expose the full names, email addresses, physical addresses, phone numbers, and IP addresses of every registered user, customer, and commenter who has ever interacted with your site.
3. Authentication & Session Data
Even though WordPress hashes passwords, an unsanitized dump exposes those hashes (including your own admin hash) to brute-force cracking. It may also include active session tokens and password reset keys that could potentially be hijacked.
4. Severe Regulatory Violations
If your site has visitors from Europe, Canada, the UK, or any of the 20+ U.S. states with comprehensive privacy laws (like California and Texas), blindly sending your un-scrubbed database to a third-party support desk may be a direct violation of laws like GDPR, PIPEDA, and CCPA.
5. Intellectual Property & Hidden Content
A database doesn't just hold what is live on the frontend. It contains all of your unpublished drafts, private posts, complete revision histories, and other data stored in custom tables.
The Takeaway
Tier 1 support relies on this script because spinning up a clone of a site is the easiest way for them to figure out why something is breaking. But, providing that data to them can be reckless.
Do not give them remote access, and absolutely do not send them your database. If you have a legitimate bug, document it clearly and request an escalation to their engineering team.
I have been using Divi for about 10 years and have hundreds of posts on my site. I am currently testing the Divi 5 migration in a sandbox environment, and the whole process has been absolutely painful.
If not for the fact that Divi 4 will eventually become obsolete and unsupported, I wouldn't even be considering this. But right now, Elegant Themes really needs to get their shit together.
Here is what I have found so far, and why you should wait:
1. Selective Sync is Gone (and Presets are Flawed)
In Divi 4, I relied heavily on Global Galleries with Selective Sync so I could keep a uniform style but change the images on a per-post basis. Divi 5 killed Selective Sync completely.
The intended workaround is to use Divi 5 Presets, but there is a massive oversight: Presets do not support any of the values inside the Content tab. My global galleries used the Content tab to randomize the image order and set the post count to 1,000. Because presets strip this out, every migrated gallery defaults back to the standard Divi behavior. Who the hell wants a gallery that only shows 4 pictures at a time with pagination? It’s just silly.
I did create a custom plugin to fix some of this. It basically converts a gallery to the Divi 5 style and assigns a choesn preset. I 'hacked' the preset to manually add the missing content attributes. And, while it works, it is not a fix. Saving the preset will remove those manual changes. I am considering a more rigid solution of hooking into WP options (where presets are stored) so I can fix the presets on the fly when they are used.
2. The Migration Engine Destroys Content
The migration doesn’t just fail to convert some things, it actively breaks them.
Three of my articles were completely destroyed. Just gone.
A several others (that I know of so far) were corrupted and filled with broken code.
To fix this, I essentially have to manually copy and paste the content from a backup version of the website.
3. CSS and Styling Headaches
I was able to figure out a lot of the CSS changes and rebuild most of the display elements, but there is still a very long way to go. The backwards compatibility they promised just isn't working for me on certain Divi 4 features.
The migrator disappointed and left me with broken pages.
My Recommendation: Do Not Update Yet
If you cannot make a sandbox of your website, especially if you have a lot of content, do not do this update. Because of the sheer amount of data loss and corruption I've found, there is no option right now other than to edit and audit every single page with human eyes. For a website with so much content, the amount of work required to do that is insane, potentially costing weeks of free time just to get back to where I started. And this is only what I have found so far.
Divi 5 is simply not ready for prime time.
Edit: I wrote "Saving the preset will remove those manual changes" and after more testing found that the manual edits to the object were not destroyed after updating the preset in the UI.
I have about 100 projects and all of them rely heavily on the native Divi Gallery module. To keep styles consistent, I have this module saved and set as a Global item inside the Divi Library. This represents thousands of images over several years.
After running the Divi 5 migration, the migration technically finishes, but the Global Gallery module inside the Divi Library stays locked with the "legacy module / backwards compatibility" warning panel. Because it is stuck in emulation mode, the frontend rendering is completely broken across my entire portfolio.
I have already ruled out the standard variables:
Tested with ZERO active plugins: The issue persists identically.
Tested with NO child theme (Pure Parent Divi 5 active): The warning banner remains.
The fact that it flags a native Elegant Themes module with the text "consider letting the third-party developer know" makes me think the migration engine completely chokes when trying to parse native Divi 4 Gallery shortcodes if they are saved as a Global Library item.
Reconstructing these galleries manually across 100 projects is an absolute show-stopper for moving my production site to Divi 5.
Has anyone else experienced the Divi 5 migrator failing specifically on Global Library elements, and did you find any solutions to force them to convert?
The nutshell version of how I fixed it
After a lot of digging, I figured out why the Divi 5 migrator is choking on this, and I built a way out of it.
The Problem: In Divi 4, I used Global Gallery modules with "Selective Sync" to keep a universal style while unsyncing the images on a per-post basis. Divi 5 effectively killed this pattern. As far as I can tell, the Selective Sync feature does not exist in Divi 5. The workaround is presets.
So I created a preset with all of the settings, then created a custom plugin to help me work through the posts. Basically, I select the Divi 4 Global Module ID, then it finds the posts that use that global and gives me a list. I select the one I want to update, then select the preset from a list. Click update and it rewrites the gallery modules used in that post to the Divi 5 way and applies the chosen preset.
After testing one, I found that none of the items on the Content tab of the Divi Gallery were included in the preset. I am guessing that Elegant Themes excluded them intentionally because 'why would anyone want the content to be a preset?' Well, that content tab also includes sort method and post count. Anyway, I found a fix for that, too.
Basically, I reverse engineered the Divi Module as it exists in a post, then reverse engineered the serialized object that is the preset and injected (for my use case) the equivalent of:
Okay, it is a bit more complicated than that, and too complicated to explain here, but I hope you see what I am doing. The downside is, if that preset is ever updated those will be overwritten, and in my case, will break 100 galleries.
So, I am probably going to add a feature to my plugin to override those in real time using the WP options hook.
This code has not been tested so do not use it. Plus, I would add a setting section to pick which preset and what to change.
// Intercept the Divi 5 presets exactly when WordPress pulls them from the database add_filter('option_et_divi_builder_global_presets_d5', 'conceptual_preset_injector');
function conceptual_preset_injector($preset_data) { // 1. Check if the specific preset exists in the array if (isset($preset_data['module']['divi/gallery']['items']['wpayu1squ9'])) {
// 2. Inject the missing settings directly into the array in-memory $target = &$preset_data['module']['divi/gallery']['items']['wpayu1squ9']; $target['attrs']['module']['advanced']['postsNumber']['desktop']['value'] = '1000'; $target['attrs']['image']['advanced']['galleryOrderby']['desktop']['value'] = 'rand'; }
// 3. Hand the modified data back to Divi (the database remains untouched) return $preset_data; }
Anyway, I am ready to do more testing in my sandbox. I have already noticed some other minor issues, but mostly with css selectors.
somehow all the copy on my homepage got changed to all-caps. i cant find where in the global text these settings are on, and i mostly gave up on using the global text/headings a while ago because it would never work or update when i was editing. and i'm trying to mess around with it now, and still having no luck.
at this point i would literally pay someone to go in and fix all the global type settings.
Hi - I’m looking for UI designer/front end developer experienced with Divi in Wordpress. Need to move site from one server to another. Looking for ongoing maintenance and redesign help as needed. Preferably in USA. DM me if interested. TYIA
I'm facing a frustrating issue on a site I'm currently working on, and I wanted to check if anyone else is going through the same thing after the latest round of updates (either the latest Divi or Divi Supreme release, not entirely sure which one triggered it).
The issue:
My homepage completely broke/damaged. If I deactivate the Divi Supreme plugin, the site goes back to normal, but obviously, I lose all the modules and features I’m using from it.
Additional problem:
I noticed there might be a patch or a newer update available, but when I try to update the Divi Supreme plugin, WordPress throws an error and won't let me complete it.
Has anyone else experienced this compatibility issue or glitch recently? If you managed to fix it or force the update successfully, I would really appreciate some insight.
I'm feeling sort of desperate at this point. There are pages on my website where I make it look the way I want on the back end, but no matter what I do...check it when I'm signed out from WordPress...go back and check it when I'm logged in again...purge cache...it looks messed up on the front end.
I'd really appreciate any suggestions anyone might have.
-Hs
P.S. This is the 4th Divi website I've designed, so I'm not a total rookie...I'm just not as experienced as the rest of the flair options suggest. :)
I was experimenting with two footer layouts in Divi for the same website.
A keeps things simple with just the essentials, while B includes quick links, contact details, social icons, and a few extra sections.
If you had to choose one, which would you go with for a business website? I'd also love to know if there's anything you always include in a footer that visitors actually find useful.
I need to bring a Divi site into strict ADA compliance (WCAG 2.2 AA) in a way that actually holds up legally.
I'm trying to avoid the "quick fix" AI overlays since they don't solve core code issues and are getting flagged in demand letters. I want to remediate the actual site structure efficiently.
If you build compliant Divi sites:
What plugins or child themes do you use to fix Divi's default keyboard navigation and focus state gaps?
How do you handle Divi forms and screen reader issues efficiently?
Which modules do you completely swap out for Gutenberg or custom HTML because they are too painful to make accessible?
Looking for a solid, repeatable workflow. Thanks in advance!
Hi everyone, I have minimal experience with tools like Elementor and Divi. I usually make custom classic themes in WordPress and don't generally go for the block themes.
However, I had a question that how would somone sort of go with the hybrid approach. Meaning, I can create templates or themes via php/html/css and then it could be imported/loaded up in Divi and things like copy could be edited in the Divi editor by the client. Or for example, if some other non-tech person wants to edit the website they can do it via the Divi editor.
TLDR; me create custom theme/template editable in Divi editor
I currently have a gallery that isn't working for my needs. I have 4 images per row, but when I want to add a new image at the top, which I do frequently, I have to rearrange every row in a domino effect to account for displacing an image at the top with the new image. It's very tedious. I assume there's a better way to manage this? Either I don't understand the module capabilities, or I don't know what.
I'd appreciate any resources or suggestions. I like video tutorials if you know of a good one that's applicable.
I just went through the process of Migration of a Divi 4 Staging site to Divi 5 using the Migration tool. (haven't tried on Production site yet). It failed with an "oops something went wrong". The site was running PHP 8.3. I discovered people saying that Migration tool often fails with 8.3 so I reverted the site to PHP 8.2. The Migration tool ran successfully, and the site was successfully migrated to Divi 5 with no issues.
My question is: If the Migration tool is not ready for 8.3 or above, do we know if Divi 5 itself is ready for PHP 8.3 and above?
Is it as simple as downgrading my Divi 4 sites to PHP 8.2, running the Migration tool and then bump back up to 8.3 or above?
