Submission
NF
Nadine Fraiss
Jan 2, 2026
Board
Bugs
Status
Reviewing
Get Updates
Powered by UserJot
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?
NF
Nadine Fraiss
Jan 2, 2026
4
BP
Bill Powell5 days ago
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.
avatar
Divi SupremeJan 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!
avatar
Dylan Roush3 weeks ago
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; } }
avatar
Divi Supreme2 weeks ago
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.