I am so impressed with the speed with which Mak responds to the changes to DIVI5. However this presents me with big challenges. I am not working on websites full time anymore but I do have several websites I need to update in the near future. Do I want until the design system is more settled or dive in now? Do I throw away my current DIVI4 design and start cleanly? I have 125 blog posts, 20 pages and a large media library so it is not a trivial project. Any suggestions from you folks who are more adept at DIVI5? My own site which needs an upgrade is here: https://sanderfeinberg.com Thanks!

UPDATE NOW: The PHP project has released PHP 8.5.12, 8.4.27, 8.3.36, and8.2.35 to fix two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, that can allow unauthenticated remote code execution.
Read The Full Post Here
The PHP project says all PHP users are strongly encouraged to updateimmediately. We recommend making sure every site you manage is running apatched version of PHP as soon as possible.
Remote code execution means an attacker could run their own code on your server.“Unauthenticated” means they would not need to log in first. In its advance notice onOctober 20, the PHP security team rated both vulnerabilities 9.2 on the CVSS v4.0scale, which falls in the Critical range.
Every WordPress site runs on PHP. These are vulnerabilities in PHP itself, notin WordPress, a plugin, or a theme, so WordPress automatic updates will notfix them. PHP has to be updated on the server.
Who is affected:
According to the
PHP security advisory
, all PHP installationsserving web requests are at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed. The PHP project considers the risk highest formod_php, where it has a demonstrated exploit in which an unauthenticated requestcan trigger the attack before any application code runs.
Fixed versions:
PHP 8.5:
update to 8.5.12
PHP 8.4:
update to 8.4.27
PHP 8.3:
update to 8.3.36
PHP 8.2:
update to 8.2.35. The PHP project says PHP 8.2 reaches end of lifeon December 31, 2026, and will receive no security fixes after that date.

There's an important distinction between what I'm trying to achieve with Frames and what I'm building with the Krafter Components Library.

Although there is some overlap, they are designed to solve two different problems.

1. Frames are about complete layouts and speed.

Frames are pre-designed sections such as Heroes, Testimonials, Pricing Tables, Features, FAQs, and Contact sections.

The idea behind Frames is simple: instead of building an entire section from scratch, you can insert a professionally designed layout that already follows your design system, including typography, spacing, colours, and responsive settings.

Frames are primarily about getting a complete section onto your page quickly and then customising it for that particular page.

2. Components are about smaller, reusable building blocks.

The Krafter Components Library focuses more on individual design elements such as Cards, Buttons, Notices, CTAs, Pricing Cards, Feature Cards, and other UI elements.

These are the building blocks you use to assemble more complex layouts.

For example, imagine you want to create a services section containing six cards.

With Frames, you could insert an entire pre-designed services section.

With Components, you could choose individual card designs, arrange them however you want, and create a completely unique services section.

You could also save that finished section as a Divi Component if you wanted to reuse and synchronise it across your website.

3. The biggest difference is where AI comes into the workflow.

This is actually one of the main reasons I want to keep the two concepts separate.

My long-term vision for KrafterPRO is an AI-assisted workflow where AI understands your design system and has access to a library of individual components.

Instead of asking AI to insert the same pre-designed section repeatedly, I want it to intelligently select and assemble components to create unique layouts.

For example, AI could take a heading, three feature cards, a testimonial, and a CTA component and assemble them into a completely new section based on the user's requirements.

That gives us much more flexibility and helps avoid the generic, repetitive AI-generated websites we're seeing today.

If everything is packaged into complete sections, we lose some of that flexibility. We'd often need to break those sections apart or work around their existing structure to access and rearrange the individual elements.

4. Divi Components are the technology, not necessarily the product structure.

This is probably the most important distinction.

I'm not saying that Frames and Components need completely different underlying technologies. In fact, they can absolutely share the same foundation.

Divi Components provide the ability to save and reuse elements, including synchronising changes where appropriate.

But that doesn't mean every reusable element serves the same purpose.

Think of it this way:

• Components = The individual building blocks.
• Frames = Complete, ready-to-use sections assembled from those building blocks.
• KrafterPRO = The design system and tools that help keep everything consistent.

Ideally, these should all work together.

5. What about maintenance and development?

The goal is to reuse as much of the underlying architecture as possible while keeping the user experience focused on two different workflows: building complete pages quickly with Frames and building custom layouts using individual Components.

Ultimately, I want users to have a choice. Someone who wants to build a website quickly can use Frames, while someone who wants more granular control, or wants to work with AI to assemble unique layouts, can use Components.

The bigger vision isn't simply to create another Divi layout library. It's to build an ecosystem where design systems, reusable components, complete layouts, and AI all work together.

Mak . I'm a little confused about something. Previously you were creating "Frames". Now you're creating "Components". I'm curious if you'll be continuing to develop and create lots and lots of frames .. OR .. will you stop creating frames, and instead focus on Components? (I'm thinking you'll drop frames and turn this into Components. Is that correct?) Please explain what you plan to do with these two features in KrafterPro. Thanks, Gary

Mak said yesterday that we should have the Krafter Starter Site in our Downloads if we are eligible. I purchased Divi University + Lifetime, and Mak said that I qualified for the free upload. Please let me know who I should contact to make this happen.

I have Initia but don't want to buy Krafter Starter Site if it's the same or close to the same produkt. MAK . @funnelstoincome

Today at the live Components session it come up an idea of an Mini Course for beginner. Now we wonder how many of community members would be intressted of an course that starts over from scratch with Divi 5 -->KrafterPro --> Divi Components workflow by MAK.
Also with an endpoint with live Q & A ZOOM meeting by newbies.
We just want to now how many would be interessted then come up with an sign up list.
Keep up with good learning work !

/ Robert J

Per the Divi 5 Components session today, I am very interested in your offer to do a beginners training series for lifetime KrafterPRO members... thanks!

Also, since Components are basically replacing Frames (which was included in KrafterPRO lifetime), maybe this could be added or at least discounted?

It is disappointing that KP Lifetime members don't get the new components, or even a discount, especially as they seem to replace Frames, which were included. It strikes me that Components are actually simpler than frames.

Mak . 

1. I'm not seeing information in various areas in the Divi University Dashboard area including the Downloads area, Licenses area, Purchase History or Profile. It's displaying nothing at all.

2. I'm still not seeing the new Krafter Starter Site to download or access in any way.

3. When I look at Divi University on my mobile phone (iPhone 15) the layout of things makes it almost impossible to use. Can you look at this and see if you can resolve this so we can access the community and our dashboard areas from our mobile devices?

Thanks,
Gary