Well it has been a crazy summer for me, first trying to update Engined to make it compatible with Divi 2.4 as I had promised, and then we also had the Divi 2.5 update. But anyway, Engined 2.0 is finally here.
Why did it take so long
I´ve tried to release the new version of Engined on several occasions but it really gave me a hard time. Every time I finished a section and checked everything, there was something new in Divi 2.4.x that screwed up something else that was working alright before with Divi 2.4.(x-1). It´s been a crazy mess with all those Divi updates. I even had to finally remove some settings because there was no way to make them work with the last Divi updates, and the worst part of it is that they were working with the previous 2.4.x versions and that some of them are not covered by Divi out-of-the-box.
And then, when I had the new update finished by the middle of August, I knew about the Divi 2.5 update, so I had to hold the release once again and wait to make it compatible with Divi 2.5.
What´s new in Engined 2.0
There´s nothing new or fancy about Engined 2.0 apart from its Divi 2.4 + Divi 2.5 compatibility. In fact, I even had to remove some of the original features of Engined.
But I wanted to bump the version number up to 2.0 nevertheless. In the first place because a lot of things needed to be changed under the hood, so the new version is quite different from the previous one. Also, I thought I´d better changed the version number to 2.0 because I think I should still offer the previous Engined 1 as a legacy version (to be used with the Divi 2.3 legacy version), leaving at the same time some room for Engined 1.X updates if needed.
Divi 2.4 added quite a few panels and sections to the Customizer. Engined panels and sections show now a different bluish background instead of the default white background, so they can be easily identified at a glance:
Features removed in Engined 2.0
Magic Codes were introduced as a means to modify not the styling but the functionality of Divi modules. However, the existing Magic Codes were not longer needed because:
- The functionality provided by the Magic Codes for the Blog modules can now be handled by the Offset setting in the Divi Blog module.
- The much needed option for the CTAs links to open in a new browser tab (that was provided via the cta_outbound_link Magic Code) was finally added by ET to the CTA module in Divi 2.4.
So Magic Codes may come back at any time if they are needed for future features, but for the time being they´ve been removed from this version of Engined.
Sections with Custom Rows
I´d originally included the Section with Custom Rows custom selectors and settings in Engined because Divi was missing something that was quite important in my opinion: rows couldn´t be customized in Divi versions prior to 2.4, they didn´t even have settings for it!
But after Divi 2.4 you´ll find interesting settings to customize your rows. The functionalities and responsiveness provided by the new Divi 2.4 structure for sections and rows are far superior to anything you might accomplish with the Section with Custom Rows feature avilable in the first versions of Engined.
Some Customizer settings have been removed, others have been added
Due to incompatibility issues with Divi 2.4, some Customizer settings have being removed from Engined, most of them in the Main Header and in Main Sidebars or Custom Sidebars sections. You may need to check the changelog if you are going to update a site you´ve previously customized with Engined.
For example, the settings Hide header on homepage load or Hide header on page load for all pages are no longer available in Engined. If you´ve used these options they will not wor for you in Engined 2.0, so you´ll need to set the HIDE NAVIGATION UNTIL SCROLL Divi option in the Customizer, under Header & navigation > Header Format.
Another example is the Sidebar width setting, along with other related settings such as Sidebar-Content Separation, Sidebar end side horizontal padding or Widgets content side margin, which didn´t work alright due to the new way Divi handles the sidebar width in percentages instead of pixels and other Divi CSS changes. So if you want to customize your sidebar width now, you need to use the USE CUSTOM SIDEBAR WIDTH Divi option in the Customizer, under General Settings > Layout Settings, but you will also find some new settings available in Engined 2.0 to customize your sidebar, such as Sidebar-Content spacing (%) or Sidebar inner width (%), among others.
Repeated or equivalent settings
After the Divi 2.4 update, some settings are now repeated in Divi and Engined (why, ET seemed to have read my mind in some cases!). Here´s an example: Since its 2.4 version Divi lets you set the color and opacity of the Footer Bottom (or Bottom Bar as they´ve named it on the Customizer). As you probably know, this setting already existed in Engined, so there are now two different places where you can customize your Footer Bottom background.
You might wonder why I don´t just simply remove from Engined every setting that is now available in Divi. There are a couple of reasons for it. The first one is to provide compatibility: if for instance you´ve used Engined to customize a site and you´ve modified your Footer Bottom, I want your site to work as you expected and I don´t want to make you go to the new Divi settings and start customizing the same things again. Another reason is that some of the repeated settings in Engined belong to a group of settings some of which are not available in Divi, so it makes sense to have them all in the same place under a particular Engined customizer section, even when there´s an equivalent setting in Divi.
Customizer settings precedence
In general, Engined settings will take precedence over the Divi settings available in the Customizer.
This is the way it works: If you set any Engined setting value out of the default value, the equivalent Divi setting will not work at all, and you´ll only be able to style the corresponding element via the Engined setting. However, if you leave the default value set in the Engined control, the equivalent Divi setting will work instead.
In the Footer Bottom background example I used above the default value is #000000 (black) with a 0.32 opacity, both in Divi and in Engined. So if you leave that value untouched in the Engined Footer Bottom background color and Footer Bottom background opacity controls (Engined General Settings > Footer Bottom section), you´ll be able to modify the background using the Divi setting (in Footer > Bottom Bar section). But if you move the Engined settings out of their default values and save your changes, they will take precedence and the equivalent Divi controls will not work.
Be careful because sometimes the Divi preview code can play tricks. For example, if you´ve customized the Main Footer background color with Engined (making it different from the default #222222 dark grey color) and then you try to modify the footer background color again but this time from the Divi setting (in Footer > Layout), your´re going to see the background color changing in the Customizer preview, but the color will revert back to the one set in the Engined control as soon as you leave the Customizer.
So, this is a general rule for settings that exist both in Divi and in Engined: If you want a default Divi setting to work, leave the equivalent Engined setting with its default value (or set it back to it if you´d already modified it).
Engined 2.0 and its Legacy version
As I mentioned before, I´m still offering the previous Engined 1 as a legacy version (to be used with the Divi 2.3 legacy version). If you want a copy of it, go to the Engined Legacy version page.
If you want to use the new Engined 2.0 with the current version of Divi, you can download it here.
If you´ve used a previous version of Engined and you want to update your site to work with the current version of Divi, you should update Engined manually:
- Deactivate Engined by switching your active theme (for example to the parent Divi).
- Delete your old version of Engined.
- Update Divi.
- Download the latest version of Engined.
- Install the new version of Engined in your site.
- Once you activate Engined, you´ll notice your previous settings will still be there for you.
Latest posts by Luis Alejandre (see all)
- How to Get a Quasi-Sticky Footer for Divi - May 11, 2017
- Of child themes and missing Divi sliders - November 25, 2016
- Divi Children 2.0.9 and the new Divi footer credits editor - September 10, 2016