• Resolved Dienies

    (@dienies)


    Hi team, thanks for great plugin. I use this plugin on various sites and it works like a charm, but on the latest website there was a plugin clash. No worries, I will add a cookie consent banner manually. BUT however, the crash/clash caused that I had to delete Complianz and Burst Analytics via the file manager. I was not able to tick “delete all data upon uninstall” because I could not get into WordPress dashboard. I deleted the plugins and can safely log into WP.

    My question: What file names can I search for to completely remove all traces from the database (for both Complianz and Burst) ?

    Thanks so much in advance.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    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.

    Thread Starter Dienies

    (@dienies)

    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!

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @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.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Database names’ is closed to new replies.