Some people have been asking lately about Divi Children compatibility with the latests versions of Divi. But like I´ve responded to somebody who said “I have been checking your blog but I do not find any mention of compatibility of Divi Children with Divi 2.7.x“, I did not mention any incompatibility on this blog either, for the simple reason that I had not found any compatibility issue while working with Divi Children 2.0.8 and the newest Divi versions. Which means no news, good news.
Until I got an email from a Divi Children user, telling me about a recent compatibility problem not with Divi, but with the newer versions of WordPress. He was getting an error message due to a recently deprecated WordPress function.
What happened is that Divi Children was using the get_currentuserinfo() function to get the name of the child theme developer in order to use it as a default in the child theme generation form (to be used as one of the footer credits settings for the new child theme), and this function has been deprecated in the WordPress 4.5 release.
This issue does not affect the child themes created by Divi Children, as the function was only used by the plugin to get a default value, prior to the creation of the child theme.
Divi Children version 188.8.131.52 fixes this issue by using the wp_get_current_user() function instead of the deprecated one.
I´ve been testing Divi Children 184.108.40.206 with the new Divi 2.7.5 and WordPress 4.5.2 today and did not find any problem. Please let me know if you do.
Updating to Divi Children 220.127.116.11
The new 18.104.22.168 version is already available for download. Just follow the instructions for updating it if you have a previous version of the plugin installed in your site.
You don´t need to update your existing child themes
As I´ve said above, you won´t need to update any of your existing child themes. As long as they were created by Divi Children 2.0.8 (or by any previous version of the plugin and were later updated by Divi Children 2.0.8), you´ll get the following screen if you try to update them via the Install or Update Divi Children Engine tab of the plugin:
- New Divi Children 3.0.10 update released - April 7, 2022
- New Divi Children 3.0.7 version for WordPress 4.9 - November 15, 2017
- Understanding Divi Children Output Mode - October 11, 2017
Thank you very much for this update.
On one of my sites I have the following message, do I need to do anything else?
Your Divi Children Engine is already updated to the newest available version (1.0.2) installable by Divi Children plugin version 22.214.171.124
If you didn´t find any issues on that site and it´s working alright for you, then you don´t really need to do anything else. But your child theme was created by a version of Divi Children prior to 2.0.8, and Divi Children 2.0.8 was the release that addressed compatibility with Divi 2.4 and above (are you using a legacy version of Divi on that site?).
Divi Children 2.0.8 also introduced some improvements like enqueuing the parent stylesheet rather than using the @import method and changes to the child theme Customizer output in order to avoid Divi 2.4 overriding some child theme settings.
So you probably may want to update your child theme to have the newest available version of the Divi Children Engine, which is 1.0.3. If you want to do so, just update Divi Children and then let Divi Children 126.96.36.199 update your child theme by following this steps:
Always remember to back up your site first!
That’s great thank you Luis 🙂
I don’t know if you can help or if this is at all related but I’m at a loss! Here’s the story…
Client’s site is fine for the visitor but she can’t login. Gets this error: “Cookies are blocked due to unexpected output.” I’m pretty sure it’s not her cookies as she’d been fine up to now and she’s tried 3 browsers.
I’ve been researching and it appears it could be extra space at the start or end of functions.php. I’ve tried editing those to no avail. I’ve also done some troubleshooting including disabling various plugins and also disabling the child theme. The child theme was created with Divi Children. When I switch to just Divi all works well but I lose the customizations done in the child theme. So my guess is the child theme. Hence this post.
Changing to parent theme gets the client back in there and able to edit but I’d like to find the underlying cause and fix it. Do you have any clues? I know this post says I don’t need to update existing child themes. I’m running Divi Version: 2.7.5 and have Divi 2.0 installed. But I’ve disabled it to see if that helped. Site is at http://www.yescollab.org. Thanks.
Are you using a plugin to hide or move the default WP login page on that site?
Yes I am… does that suddenly cause this? I can try disabling it. Thanks.
Just a question, what is the best choice, the plugin or the divi child theme engine ?
It all depends on what you´re looking for. The plugin allows you to create as many child themes as you wish, giving them the name you want, having yourself as the child theme author, etc. But on the other hand a child theme created by Divi Children will have less customizing options than Engined.
It shouldn´t be that way, because my intention when I created Engined was to add all its features to Divi Children soon after the release of Engined (you may have read about that on several posts on this blog). Engined was a great child theme that took many months to develop and provided a lot of features not previously available in Divi out of the box (more than 500 settings in the Customizer). But all the (not backwards compatible) changes ET introduced after Divi 2.4 made it very difficult and tiresome to have it permanently updated to the latest Divi version, because I consider updates as “upgrades”, while in this case they would be something like “downgrades”. The bottomline is that I´m not updating or testing Engined against new Divi versions anymore. Needless to say, for the same reasons I didn´t add all the features included in Engined to the Divi Children plugin either.
Engined still offers many features not available in Divi, so you may want to try it. But you should do it at your own risk.
A couple of weeks ago I resumed the development of a new Divi Children version but, right after I did, I got the news about the new Divi 3 coming in 100 days. So I thought it better and I think I´ll wait to see what Divi 3 brings. I don´t want to work for a long time on features that ET will be releasing for Divi out-of-the-box. Also, I have to be careful about changes in the Divi code that can break previous customizations, as sadly happened with not backwards compatible code in the release of Divi 2.4 (that´s why they had to keep the Divi legacy version). Once bitten, twice shy.
Please disregard the email I’ve just sent. Your comment on this page answers it all, except one question:
Can I use your plugin on an existing Child Theme (Generated by Divi Space) or is it better to start over using your plugin?
Thanks for creating something awesome and making it free. Although I really don’t mind paying for it if that ensures you get a living out of it.
Divi Children´s mission is to create child themes. That means you can´t use any of the features Divi Children includes in the child theme without actually creating a child theme and using it as your active theme.
However, if your existing child theme hasn´t been customized further than adding some code to its stylesheet, or to its functions.php or to both of them, you can just create a new child theme with Divi Children and then copy your existing custom code to the appropriate file(s) of your new child.
Feel free to send me another email if this doesn´t answer your particular needs.
Receiving the following when I try to install. Suggestions?
Installing Theme from uploaded file: Divi_Children_188.8.131.52.zip
Unpacking the package…
Installing the theme…
The package could not be installed. The theme is missing the style.css stylesheet.
Theme install failed.
You´re trying to install a plugin as a theme. Divi Children is a plugin, so you should install it as such. Please read this post.
DUH! OK, so I officially feel totally foolish. The worst part is, I know better. Of course it’s a plug-in. I’ve used it before and have never had any problem installing it. Thank you very much for the correction. Thanks for the plug-in, too. Great product.