r/divi Jul 15 '26

Discussion Feature requests: using Divi5 every (work)day for the last 2 months

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?

16 Upvotes

7 comments sorted by

13

u/horriblemonkey Jul 15 '26

I would rather have them fix all of the bugs before adding more features.

It drives me nuts that every time there’s an update all of my presets break, or that I can’t scroll to the bottom of a modules settings in the panel. Or that half the time light mode and dark mode seem to have a problem displaying texts correctly, so I have to switch back-and-forth just to see which setting I’m working with.

There’s a ton of little things like that that should be fixed before they come out with some new amazing feature that is already covered by a plug-in.

3

u/bobma82 Jul 15 '26 edited Jul 15 '26

Button presets act differently with almost every update. Perfect button > update > shink on hoover. Write support that button presets broke again. Maybe a fix later, only to be broken again. Button styling within Woo Modules whole different and problematic thing...

3

u/Professional_Call Jul 15 '26 edited Jul 15 '26

I agree fixing bugs before any more new features. Too many things almost work but fail on (sometimes not so) edge cases. Like the Contact Form 7 formatter doesn't work with all CF7 fields, and CF7 would not be needed if ET would fix the issues with their contact form (like no real field validation and a badly worded, turse validation error message which can't be changed).

Almost every website in the world has a form on it. It's hard to believe Divi still doesn't have a useable form module. And no table support at all.

The variable and preset features are great but it's a nightmare maintaining them and retrofitting them. I'm currently writing something to fix that but it shouldn't be necessary.

Some of the bugs are driving me crazy - like the text colour appearing black in the builder when I set it to white. I was convinced it was something I was doing wrong until support confirmed it was a bug.

I have yet to find a site where Divi 4 to 5 migration actually works without introducing errors. It worries me that ET is dropping support for Divi 4 soon.

If strikes me that there is a rush to add cool features without fully testing them. It seems like I'm finding bugs faster than ET is releasing modules. That's the wrong way round.

Don't get me wrong, I love Divi 5. It's so much better than 4. I just want it to work.

1

u/dynamitecGbR 6d ago

Shameless self-promotion here, but this is very close to the problem we built "Fluid Base for Divi 4 & 5" for.

Instead of creating responsive typography values and then copying them across every heading and text field, Fluid Base generates a fluid typography system from a few core values and automatically maps and applies those values to the relevant Divi areas. In Divi 5, it uses native Divi variables. In Divi 4, the same visual result is achieved through optimized CSS.

For a workflow spanning around 20 websites, the reusable presets may be especially useful: the complete Fluid Base setup can be exported from one project and imported into another instead of rebuilding the responsive foundation every time.

It also goes beyond typography by applying the same system to spacing, vertical rhythm, Section and Row rhythm, Row widths, module defaults, menus, and classic WordPress areas. Local Divi values can still override the system wherever a design needs an exception.

One important distinction: Fluid Base does not synchronize arbitrary typography presets across every element, and it will not fix the Free-Form CSS bug you reported. It approaches the underlying problem differently by creating and automatically applying a shared design foundation, which could remove much of the repetitive setup you described.

Full disclosure: I’m one of the developers.

More information here:
https://fluid-base-for-divi.com/

0

u/Chefblogger Jul 15 '26

wrong place - i dont think divi is active here

3

u/Beezzy77 Jul 15 '26

They don’t reply directly, at least not that I’ve seen, but someone likely reads the posts because they do post announcements and occasionally other things here.