Jul 3
I updated version 5.0.0-beta.09 and all the modules on my page disappeared
This update caused most of the modules on my website built with this plugin to be lost
Closed
Jul 4, 2025
Hi there, We have sent out a newsletter update on this issue and I've attached it as well so you can read and as David said, Divi & Divi Supreme are both still in beta so it's not a good idea to use on live/production sites just yet. Thanks for your understanding.
Jul 6, 2025
Divi Supreme I still have a white screen trying to editing any page.
Jul 7, 2025
Divi SupremeWe’ve revamped how slug classes work, making them cleaner and shorter, which helps pave the way for better stability and structure moving forward. You’ll just need to re-add those modules and retest — all the settings are still there. How to do it specifically, delete the old module? How to ensure that the set data is not lost? Can't we make a migration process? Or record a video tutorial
Jul 8, 2025
DicolorLED this is my question too. Do we roll back to 5-27-25 version, delete every single Divi Supreme module site-wide, update to version 7-4-25 and try to re-add them? What happens if we still get a blank page when we reinstall version 7-4-25?
Jul 3, 2025
Hi there, Apologies for the inconvenience, we're looking into this issue and will release an update asap. I'll let you know once we have more info on the issue. Thanks for your patience.
Jul 3, 2025
The same happened to me, and now I activated automated hourly backups. It's important to understand that Divi is in Alpha and Divi Supreme is still in Beta... you need to be extremely careful.
Jul 4, 2025
David Mesa NoackThanks for reminding me. I was careless. It seems that I need to check the situation in the forum before updating to make sure there is no problem before updating.
Jul 3, 2025
I have rolled back the entire site to the backup on July 1st. This is terrible. Please fix this serious bug before we try to update.
Jul 3, 2025
This is a really bad update, I lost half the work on my site, can this be fixed?
FYI: Rolling back to Supreme beta version 5-27-25 fixed this issue for me.