Hi @dienies, Was the conflict with both Burst and Complianz or just one of them?
It’s very important for us to know which plugin there was an issue with. Can you share the plugin that you experienced a conflict with? Then we can reproduce the issue, and contact the developer about the issue.
Hi Roger, I installed Complianz again and everything works perfectly fine. Not brave enough to install Burst again because I think that first time round the site broke right after I activated Burst installation.
I added Google Analytics to the header so wont be using Burst in anycase. Would you be so kind to send me the relevant names or tables in database that I can search for to deep clean in the database? Thank you.
There are multiple plugins on the site, please don’t judge me – I inherited the site and always cautious to delete plugins left and right before I know their purpose.
The following might be relevant: Divi, Simple Membership Plugin (and their addons by wp.insider), Wordfence, Siteorigin bundles, Popups for Divi (by divimode), Display PHP version, Easy Child Theme (by Ashok), Shortcode in Menus (by Gagan), and UpdraftPlus – and now of course Complianz.
I can already see what you are thinking.. ‘no wonder it broke!’ I am in process on reducing them one by one 🙂
Thanks so much for working on this!
@dienies you can use the code from the Burst deactivate script, and add it as a mu-plugin:
$options = array(
'burst_activation_time',
);
foreach ($options as $option_name) {
delete_option($option_name);
delete_site_option($option_name);
}
global $wpdb;
$table_names = array(
$wpdb->prefix . 'burst_statistics',
);
foreach($table_names as $table_name){
$sql = "DROP TABLE IF EXISTS $table_name";
$wpdb->query($sql);
}
This will remove all Burst data.
Let me know if that helps.