Fatal error when deactivating with the option to remove all data

  • Resolved bostrb

    (@boosterbast)


    10 months, 3 weeks ago

    I attempted to deactivate the burst plugin and selecting the option to remove all statistics and settings. This resulted in a fatal error. Please tell my how I can remove the burst plugin and all its settings without getting a fatal error. Please find the error message below (I have removed my domain info from the paths). My wp database is renamed so I think that might be the reason why this error happens.

    Een fout van het type E_ERROR werd veroorzaakt op regelnummer 787 van het bestand ….public_html/wp-content/plugins/burst-statistics/class-admin.php. Foutmelding: Uncaught Error: Call to a member function get_results() on null in …../public_html/wp-content/plugins/burst-statistics/class-admin.php:787
    Stack trace: 0 …/public_html/wp-content/plugins/burst-statistics/class-admin.php(625): burst_admin->delete_all_burst_configuration() 1 …/public_html/wp-includes/class-wp-hook.php(324): burst_admin->listen_for_deactivation() 2 …/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 3 …/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() 4 …/public_html/wp-admin/admin.php(175): do_action() 5 …/public_html/wp-admin/plugins.php(10): require_once(‘…’) 6 {main}

    thrown

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @boosterbast,

    Sorry to hear you are encountering this problem. We missed adding a “global $wpdb” at the start of the function which caused the fatal error.

    I have fixed this on our GitHub: https://github.com/Burst-Statistics/burst

    You can delete the current version and then upload this one. After that, the deleting of all data should work.

    Sorry about the hassle!

    Kind regards,
    Hessel

    Thread Starter bostrb

    (@boosterbast)

    Will this work without any problems? Because when I installed burst statistics. I had to manually set the site to debug mode so that the burst statistics database correctly was set to the renamed database.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @boosterbast it has been tested successfully on our environments, so I expect that this will work without issues.

    Thread Starter bostrb

    (@boosterbast)

    Thanks for the reply. Just followed the steps you described and the fatal error did not occur.

    How can I see that the burst data is now actually removed?

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    In the database, the tables starting with burst_
    should now be removed.

    Thread Starter bostrb

    (@boosterbast)

    The tables are removed. Thanks for the support!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Fatal error when deactivating with the option to remove all data’ is closed to new replies.