I wonder if you just need to empty the static cache in the Divi theme options. I've often run into styling problems just even updating the Divi 4 theme, then I just resave in the Theme Builder, empty the static cache, and all the styles work. I have a couple sites dependent on your plugins so I'm excited to see you all involved and active with Divi 5. Thanks for putting this out there!
Probably because the header and footer are made using the Theme Builder and they are still working on that. Nick said in a recent video that the Divi 4 API will load if it detects modules using the Divi 4 API - so it's basically still Divi 4 running on those pages . And that's probably the reason it still looks good.
Thanks for the report guys ! Just a question (important!) : if we check "theme auto-update" button, can it cause issues you talked about ? I heard from Elegant Theme that there are a kind of "functions" to check compatibilities in back-office first, before showing the change in the front office. So, is it better yo uncheck that auto-update box in theme part or not according to new update functionality?
Hey there @Madevcom! Don't quite me on this, but I suspect that your sites running Divi 4.XX will not auto-update to the Divi 5 Public Alpha. When Divi 5 officially releases, we will have more answers on the features to help for a smooth transition from Divi 4 to 5. Don't worry, we will have a few more dev letters before that happens and explore these with you!
![ILLSLICK - THE KING'S LANDING [Freestyle]](http://i.ytimg.com/vi/feIJJnNkTfk/mqdefault.jpg)
Wish more Divi 5 Best Practice tutorial come out, benefit for many learners, thanks. 😊👍
I wonder if you just need to empty the static cache in the Divi theme options. I've often run into styling problems just even updating the Divi 4 theme, then I just resave in the Theme Builder, empty the static cache, and all the styles work. I have a couple sites dependent on your plugins so I'm excited to see you all involved and active with Divi 5. Thanks for putting this out there!
Probably because the header and footer are made using the Theme Builder and they are still working on that. Nick said in a recent video that the Divi 4 API will load if it detects modules using the Divi 4 API - so it's basically still Divi 4 running on those pages . And that's probably the reason it still looks good.
Thanks for the report guys !
Just a question (important!) : if we check "theme auto-update" button, can it cause issues you talked about ?
I heard from Elegant Theme that there are a kind of "functions" to check compatibilities in back-office first, before showing the change in the front office.
So, is it better yo uncheck that auto-update box in theme part or not according to new update functionality?
Hey there @Madevcom! Don't quite me on this, but I suspect that your sites running Divi 4.XX will not auto-update to the Divi 5 Public Alpha. When Divi 5 officially releases, we will have more answers on the features to help for a smooth transition from Divi 4 to 5. Don't worry, we will have a few more dev letters before that happens and explore these with you!
@@DiviEngine Thanks !