Divi - Ultimate WordPress Theme & Visual Page Builder Elegant Themes Divi v4.24.2

[heyhayhello]

Divi v4.24.3 (updated 04-02-2024) - untouched​

- Fixed several compatibility issues with PHP 8.2.
- Fix deprecated messages when editing existing post with Divi Layout block in WordPress 6.5.
- Fix deprecated messages when adding new post or edit existing post in WordPress 6.5.
- Fixed image refinement issues by correcting endpoint usage and prompt handling.
- Added multiple upscaling and canvas limit to 8192px.
* ai-app/build/et-ai-app.bundle.js
* ai-app/build/et-ai-app.bundle.css
* ai-app/i18n/ai-image-editor.php
* includes/builder/api/DiviExtension.php
* includes/builder/class-et-builder-element.php
* includes/builder/feature/Library.php
* includes/builder/frontend-builder/bundle.js

Previous changelog: v4.24.2 ( updated 02-20-2024 )
- Fixed an issue in the Divi Builder that caused fields in the module settings modal to crash.
* core/code-snippets/app/boot.js
* epanel/theme-options-library/app/boot.js
* includes/builder/frontend-builder/bundle.js

@mk007 @maxv @teegraffer

 

[maxv]

Divi v4.24.3 (updated 04-02-2024) - untouched
- Fixed several compatibility issues with PHP 8.2.
...

Thanks for the share Now that we have the untouched it is easier to see what was changed in the one mk007 had on mega. That version had older language files (from 4.24.2) and had an extra directory full of bogus placeholder files \Divi\includes\builder-5\ - the files were all the same just placeholder nonfunctioning stubs for js or php. I'm not sure why anyone put it there - very strange! (it is definitely not malevolent - there are no references to it from any other file - it was completely vestigial and could be deleted.

Although Divi theme that is available for download here often has "null" in the title, it doesn't look like there is any null needed. However, I always remove the update checks in my own. If someone cares to do the same I just do these:

in Divi\includes\builder\conditions.php, I change et_builder_is_mod_pagespeed_enabled() just add "return false;" at the top of the function

return false;

in Divi\core\components\Updates.php I comment out the add_filter lines for updates, so it ends up like this:

//        add_filter( 'pre_set_site_transient_update_plugins', array( $this, 'check_plugins_updates' ) );
        add_filter( 'plugins_api', array( $this, 'maybe_modify_plugins_changelog' ), 20, 3 );
//        add_filter( 'pre_set_site_transient_update_themes', array( $this, 'check_themes_updates' ) );

These changes are not necessary, but reduce/eliminate the web requests your site will make. If you are using mod_pagespeed then obviously don't do the first one (this is why I don't upload my edits - this description is enough and also it would cause problems for people who use mod_pagespeed but don't carefully read).

 

[sultantourismae]

Please update 4.25

 

[krissiank]

Please update 4.25

 

[marketania]

4.25 is out.

 

[Parrey]

Im not sure if this is allowed, but heres a way to get an api username and key.
visit this page, demo for divi. have you dev tools open inside web browser.
change the layout on the page using the library and it does an api check of username and password.

https://www.elegantthemesdemo.com/?et_fb=1