I’m back with another Divi 5 progress update. If you aren’t familiar with Divi 5, check out our original announcement post. To put it briefly, we are recreating the builder in Divi 5 from the ground up, focusing on performance, stability, scalability, and extendability. It won’t come with many new features, but it will be way faster and more capable, and it will give our team and the community the tools we need to hit the ground running with fantastic new modules and features.
Last month, I gave a demo of the Divi 5 Visual Builder to showcase its lightning-fast speed, so if you missed that video, be sure to check it out.
I’ll discuss Divi 5’s extendability and give a quick demonstration in this month’s update. But first, let’s talk about what our team has been up to over the past month.
What We Accomplished This Month
We made a lot of progress last month. We are nearing the launch of Divi 5 Dev Beta, the next phase of the Divi 5 beta program, and I hope to announce its release in my next update.
While on the home stretch, we remain focused on simplifying the module creation process so that creators from the community and our team can build Divi 5 modules more quickly. The work we put in during this phase will pay dividends in the proceeding phases, with the ultimate goal being to get your hands on Divi 5 sooner.
Changelog Entries:
- Refactored all currently built modules to incorporate a new and improved element-based attribute system.
- Added saveInlineEditorValue Util Function In packages/module-utils To Store Value From Inline Text Editor
- Added canEditInline Util Function In packages/module-utils To Check If the Module Attribute Can Be Edited Inline
- Added onPaste Handler Event To The Inline Text Editor to Process Clipboard Data
- Replaced Inline Text Editor Event Based classNames With data-* Selectors (e.g: et-vb-editable-element–empty, et-vb-editable-element–html) In The Builder.
- Updated CSS For Inline Text Editor With data-* Selectors (e.g: [data-et-vb-editable-element]).
- Updated Inline Text Editor to Check Whether Module is Editable and The User have ProperPpermission to Edit
- Refactored Keyboard Shortcut Store To Disable Shortcuts When Inline Text Editor Is In Editing Mode
- Added Inline Text Editor functionality To Audio Module For Title
- Added Inline Text Editor functionality To Blurb Module For Title
- Added Inline Text Editor functionality To Bar Counter Module For Title
- Added Inline Text Editor functionality To Circle Counter Module For Title
- Added Inline Text Editor functionality To Code Module For code (HTML) Content
- Added Inline Text Editor functionality To Countdown Timer Module For Title
- Added Inline Text Editor functionality To Fullwidth Header Module For Title and Subhead
- Added Inline Text Editor functionality To Fullwidth Code Module For code (HTML) Content
- Added Inline Text Editor functionality To Login Module For Title
- Added Inline Text Editor functionality To Number Counter Module For Title
- Added Inline Text Editor functionality To Person (Team Member) Module For Name and Position
- Added Inline Text Editor functionality To Pricing Table Module for Title, Subtitle, Currency, Sum and Frequency
- Added Inline Text Editor functionality To Slider Module For Slide Heading
- Added Inline Text Editor functionality To Tabs Module For Tab Title
- Added Inline Text Editor functionality To Testimonial Module for Author, Job Title and Company Name
- Added Inline Text Editor functionality To Toggle Module for Title
- Added Inline Text Editor functionality To Wireframe View for Module Admin Labels
- Updated Inline Text Editor functionality To Set Default Text When Module Attribute Is Edited With Empty Value (e.g Admin Labels in Wireframe View Mode)
- Added Test Cases To Ensure Editing Mode For Inline Text Editor Doesn’t Get Activated For Locked Module
- Added Tests For In All The Modules That Use The Inline Text Editor To Ensure It Works As Expected.
- Added Base InlineRichTextEditorContainer And InlineRichTextEditor Components In The Builder For Inline Editing Of Rich Text.
- Introduced the ElementInnerContent class, a simplified version of the MultiViewElement class.
- Improved MultiViewScriptData class.
- Added custom filter and hook in Responsive Content FE script.
- Introduced MultiViewElement class.
- Dynamic Content: New Dynamic Content value format: `$variable(JSON_VALUE)$`.
- Dynamic Content: Introduced new attributes conversion functionality for Dynamic Content attributes.
- Dynamic Content: Introduced initial Dynamic Content rendering in frontend part.
- New approach on processing Dynamic Content values. The Dynamic Content values will be processed on the block parser before the document is parsed into list of block structures.
- Back ported the code to resolve the Dynamic Content built-in and custom field values based on the field name and settings.
- Back ported the code to generate the Dynamic Content built-in and custom fields based on different conditions.
- Dynamic Content: Introduced initial Dynamic Content rendering in VB
- Dynamic Content: Integrated Dynamic Content functionality into `ModuleElements` class.
- Dynamic Content: Implemented Dynamic Background Image functionality in VB.
- Dynamic Content: Introduced initial Dynamic Content UI on Module Settings in VB. Right now this is available as prototype on testimonial module’s input text with support on `site_title` Dynamic Content Option only.
- Inline RichText Editor: Added core TinyMCE editing capabilities to the Rich Text inline editor component
- Inline RichText Editor: Updated the Rich Text inline editor to retrieve editable content and save edited content.
- Module Attribute Refactor: Refactor Icon module’s attributes.
- Module Attribute Refactor: Refactor Social Media module’s attributes.
- Module Attribute Refactor: Refactor Video module’s attributes.
- Module Attribute Refactor: Refactor Search module’s attributes.
- Module Attribute Refactor: Refactor Full Width Code module’s attributes.
- Module Attribute Refactor: Refactor Pricing Tables module’s attributes.
- Module Attribute Refactor: Refactor Accordion module’s attributes.
- Module Attribute Refactor: Refactor Full Width Map module’s attributes.
- Module Attribute Refactor: Refactor Full Width Slider module’s attributes.
- Module Attribute Refactor: Refactor Map module’s attributes.
- Community Reported Bugs: Implementing Module Credit mechanism. Add Credit on module.json to display module credit.
- Community Reported Bugs: Enable selected tag on field description
- Transition Options: Added Transition Style Component for all modules which used ElementStyle.
- Module Elements: Introducing ModuleElements class to simplify elements creation on Audio, Blurb, CTA, and Testimonial modules.
Illustrating Divi 5’s Extendability
One of the most essential aspects of Divi 5 is its extendability. When I talk about extendability, I am talking about Divi 5 being nimble and capable from an API perspective and the many unique features we can create thanks to those improvements. I have also spoken about aligning Divi 5 with the future of WordPress, removing shortcodes, and integrating many of the WordPress block packages into Divi 5.
What does all of this mean for the future of Divi?
I asked the manager of our dev team to find a little free time to whip up a quick demo that illustrates these aspects so that I could share something fun in this update that is visually representative of Divi 5’s extendability. He came up with the Automatic Block Module. A module that turns every Gutenberg block into a Divi module, supercharging them with Divi’s wide range of design settings and allowing you to mix modules and blocks on the same page!
The block module grabs HTML elements from the block and dynamically generates option groups that give you complete control over its design. You can also generate new option groups on the fly, targeting and customizing any element.
While we created this block module for fun, and it’s neither finished nor polished, it is a wonderful demonstration of what we can do with Divi 5, and with relative ease, thanks to the new foundation we are creating.
Not only is it easy for us, but for you and the development community too, thanks to the open nature of the API. We may even finish up this Block Module and add it to Divi 5 as an official feature. But for now, we remain focused on progressing through the beta phases.
Divi AI Is Almost Finished!
That wraps up this month’s Divi 5 update. In other news, our first version of Divi AI is nearly finished, which will allow you to generate extraordinary images out of thin air and write and improve content with AI while you work in the Visual Builder. I’ve been having a lot of fun playing with the unfinished version and I am looking forward to wrapping it up and shipping it soon!
Stay Tuned For More Updates
I promised to give Divi 5 progress updates every month, and that’s what I plan to do! I can’t promise that every update will be exciting, but rest assured we are working as hard as we can to finish this huge project. Each day we get a little closer and the Divi 5 foundation gets a little stronger. We will soon be launching the Divi 5 Dev Beta, which means the foundation will be complete. From there, it’s full steam ahead on the user-facing features that you will get to test out in the Public Alpha later this year.
Leave a comment if you have any questions. See you in the next update!
Why are all the Divi Blog posts list items showing September 5? Is this a bug in the shift to Divi 5? 🙂
I was here looking for Divi 5 updates… would like to know when I can get on the beta. Not expecting an answer here… but very excited about the future with Divi 5.
Will the new Divi 5, support clamp typography sizes?
I have a client that needs a API implementation with templates/themebuilder. I am guessing that it makes more sense to wait with that project until Divi 5 is stable. Is there any update for the timeline of the release?
Thanks
Do we have any July news update?
It is a little dissapponting that there are still no august news to the progress? Are all in holidays?
I am so excited about Divi 5.0!!
This will change the Block-Editors space ;)!
One thing I would mention is, that your offer of Lifetime Payment is very nice and for those one who bought it, you are the lucky ones :D! But for the developing and the future of Divi I would recommend to cancel this option with the release of Divi 5.0. The customers who bought the Lifetime Package will remain but all the new customers should be in a monthly or yearly payment. I know it sounds harsh but it is necessary for staying alive as a company. If you leave the lifetime payment you will get more and more customers, but you dont get more “money”. As more customers elegante themes get, as more support and updates are needed.
Its just my opinion and I hope to see Divi healthy rising into the future.
Will you continue to support the current version of Divi for those of us that don’t have the time or interest to rebuild and relearn of all our websites every single time you folks decide you feel like starting your software over from the ground up? The last upgrade was an unmitigated disaster and I have no intention of doing that with you folks again unless you are going to pay me.
Divi, like WordPress, must evolve. We understand your concerns about upgrading to Divi 5 once it is released, but, you don’t have to be worry as it has backward-compatibility with Divi 4. We acknowledge the difficulties some users may face when adapting to major updates, and we’re constantly striving to improve our upgrade process to minimize disruptions. While it may be time-consuming, embracing Divi 5 can offer significant benefits, including enhanced features, improved performance, and increased security.
Is there any more info on the Divi AI feature anywhere?
I’m assuming that it’s using a third party LLM so would need api keys added.
Is there any functionality to help track token use? And can it be disabled/ restricted by role/cap?
Speed speed speed. That will make my day. But anything divi is great. Loved the theme from day one. Added divi booster from Dan from day one, and now (bought but not tested) php module, is really going to put it into a different bracket. Thank you so much for the hard work you are putting in for us.
Hello there!
Will you be fixing the issue regarding Dynamic content and ACF, where Divi used to require unique field names all over a project? Especially when building very huge projects using different ACF repeaters and other flexible fields, this is quite annoying having to make up unique field names for each field, while ACF already identifies each custom field by a unique key.
Divi should be using the key and from there be able to display corresponding field names and fieldset titles, so it is clearer which custom field is being displayed in the list of the dynamic content gui.
Thank you!
Best of all, I ask you to implement more features regarding the WordPress Multisite function. To show in subsites the contents (sections, rows, modules) about other subsites of the Network, implementing functions like these strings:
switch_to_blog( $blog_id );
function view(){
switch_to_blog(X);
return do_shortcode{‘[view-shortcode]’}
restore_current_blog();
}
add_shortcode(‘view’, ‘view’);
restore_current_blog();
I can’t wait to see the public version online! I manage a site in four languages, and I spend far too much time watching the wheel turn. I hope wpml integrates well with Divi 5 . Thanks a lot for
your work – laurent
Being able to generate an image AND choose whether it’s Portrait or landscape as opposed to just square – that’s a real winner for me!!
wow , I liked the tables and the style you can create.
Great work. Integration with the block editor is what will keep Divi relevant with the direction that WordPress is taking, making it attractive to a wider audience.
I must say that having a break from frequent updates introducing new features is refreshing while seeing Divi being optimised. Dare I ask if we will see performance improvements on the front end as well?
Thanks for the various updates, they are so nice! My attention goes to the Automatic Block Module, and leaves me asking – if any WordPress block can be a Divi module, then how will that affect current Divi modules and even the Divi Marketplace going forward?
Hey Nelson! Great question, I’d say the Divi Customers and the Divi Community as a whole wins, including the Divi Marketplace creators. For example, the same healthy competition in the broader WordPress ecosystem has proven to benefit everyone and there’s tons of great themes, plugins and products that have resulted and in the end everyone wins. While all the Gutenberg blocks being automatically able to be enhanced by Divi’s design tools is great, but I still think there is an edge due to Divi 5.0’s API features and flexibility and extensibility, there will be so much surface area for creative freedom for great Divi Marketplace creators like yourself to make distinguished and amazing native Divi Modules with the new API. We also hope to inspire some Gutenberg block developers to come over to Divi and port their work and get all the benefits of native Divi Modules!
Again in the end everyone wins and Divi will just be chock full of endless abilities to make amazing unique websites for everyone.
I’m dying to see what 5.0 is going to do for my existing divi sites as far as performance goes.
The AI looks like an amazing feature. But we all really need to know — will there be any possibility of copyright infringement on the images generated?
I must be missing something here. As a photographer I take an image and the copyright is mine. As a website designer if I create an image using AI then surely, in the same way, the copyright is mine.
I agree with barry – we need to be assured that we would never have to worry about any copyright infringement on the images generated.
I can’t wait to test it out. The speed improvements have my interest, but the extendability will be the foundation for the future. Great stuff!
Wow, this is awesome!