Jan 2

Plugin is causing a critical error

I got the Divi Supreme Pro Beta Version for testing with Divi 5, but after installing the plugin caused immediately after activating a critical Wordpress error and strangly changed one setting in a hero section (but nothing else at least what I am aware of), I just recognised it because my nav bar was transparent and suddenly there was a white background (I thought it was a background but turned out I had to set the margin at minus to make it transparent again, so it just had space that showed white and no actual "background). So I am not able to test it. Anything that can help with that?

Closed

changed status toClosed·3 weeks ago

Mar 7, 2026

Hey Divi Supreme, I have just updated to Beta 17 in Local Flywheel environment - unfortunately the pages are not saving anymoree. Disabling plugin solve the problems.

Mar 14, 2026

Hi there, Good day to you, Please reach out to us at support@divisupreme.com with a temporary login to your site to take a look. Thanks!

Mar 5, 2026

Update: Please update to Beta 17, which includes a fix for this issue.

Feb 13, 2026

I've had the same issue & reported it to them. It's happened on every site that I've tested on. I pulled the error logs and the plugin is looking for a file in the wrong directory. My hosting's file structure is apparently different than what Supreme Pro is expecting. On a sidenote, I had the exact same issue with the Divi Gravity Forms plugin and reached out and the developer created a patch and sent me an updated plugin and that fixed that plugin. Just waiting on Supreme Pro to do the same

Jan 30, 2026

I sent an email to support about this same error. They said "The behavior you’re describing is unusual, and we haven’t received similar reports from other users so far." Can someone advise if this has been investigated.

Jan 5, 2026

Hi Nadine, That's indeed a strange behavior and hasn't been reported by anyone else. Could you please send us an email at support@divisupreme.com with a temporary login to your site to take a look. Thanks!

Jan 10, 2026

I had the same error in Beta 15. and it is the same in 16. the issues was the i had to make /wordpress/wp-content resolve to content directory /www/wp-content using a symlink or container mount. With ChatGPT's help: Root cause Several Divi 5 module files in Supreme Modules Pro hardcode the Divi DependencyInterface path using ABSPATH . 'wp-content/...'. In split path installs where WordPress core lives under /wordpress but wp-content is mounted under /www/wp-content, that path resolves to /wordpress/wp-content/... and fails, causing fatal errors. The line that needed changing In each affected module file, this line was the problem: require_once ABSPATH . 'wp-content/themes/Divi/includes/builder-⁠5/server/Framework/DependencyManagement/Interfaces/DependencyInterface.php'; What it was changed to Replaced with a theme path based loader that does not assume wp-content sits under ABSPATH: $interface = 'ET\\Builder\\Framework\\DependencyManagement\\Interfaces\\DependencyInterface'; if ( ! interface_exists( $interface ) ) { $dependency_file = trailingslashit( get_template_directory() ) . 'includes/builder-⁠5/server/Framework/DependencyManagement/Interfaces/DependencyInterface.php'; if ( file_exists( $dependency_file ) ) { require_once $dependency_file; } }

Jan 16, 2026

Hi there, Thanks for sharing more details on this. I've forwarded this to our team for further checking on this and we'll get back with more info.

Mar 4, 2026

Has there been any traction on a long-term solution for this? I'm still having the issue on my Divi 5 sites when I try to activate Supreme Pro on Flywheel hosting

Mar 4, 2026

Hi there, The update should be available soon. In the meantime, please send us an email at support@divisupreme.com, and we’ll provide you with a hotfix version of the plugin so everything works properly until the official update is released. Thanks!

Mar 5, 2026

The updated file you sent to me solved the issue. Much appreciated!