Fatal Error Conflict: BeBuilder vs WooCommerce Product Add-ons
Message: I am experiencing a "PHP Fatal error: Cannot declare class" when opening BeBuilder on pages.
The Conflict: It appears BeBuilder's initialisation process is force-including files from the /woocommerce-product-addons/includes/admin/ directory. Because the classes in those files (specifically WC_Product_Addons_Product_Export, Import, Admin_Notices, Admin_Order, and Admin_Ajax) are not wrapped in class_exists checks by WooCommerce, the site crashes when they are loaded a second time.
Request: Could your dev team ensure that when BeBuilder "pre-loads" third-party plugin components, it uses include_once or performs a class_exists check to prevent these collisions? This would make the builder much more robust when working with premium WooCommerce extensions.
Comments
Hey,
Please send us the WordPress dashboard and FTP access privately through the contact form, which is on the right side at https://themeforest.net/user/muffingroup#contact, and we will check that out.
Notice!
Please attach a link to this forum discussion.
Sending incorrect or incomplete data will result in a longer response time.
Therefore, please ensure that the data you send are complete and correct.
Thanks