• Resolved Ambyomoron

    (@josiah-s-carberry)


    Please do not forget to use the local DB prefix in the commands to drop database tables.

    Also, are you automatically dropping the tables when the plugin is deactivated?

    'db.seasp_csp' for query DROP TABLEseasp_csp; made by deactivate_plugins, do_action('deactivate_sea-sp-community-edition/Bluetriangle-free-csp.php'), WP_Hook->do_action, WP_Hook->apply_filters, Blue_Triangle_Automated_Free_CSP_deactivatePHP message: WordPress database error Unknown table 'db.seasp_directives' for query DROP TABLEseasp_directives; made by deactivate_plugins, do_action('deactivate_sea-sp-community-edition/Bluetriangle-free-csp.php'), WP_Hook->do_action, WP_Hook->apply_filters,

    If so, that is a VERY BAD idea. Drop tables when one uninstalls, but NOT when one activates.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author bluetriangle

    (@bluetriangle)

    Hey there, thanks as always for the feedback! To answer your original point, the plugin does both the DB prefixes and the old tables for older versions – this can cause an error message but shouldn’t hurt anything. With that said our developers will be adding a check or try-catch so that message doesn’t pop up in the future.

    And to your second point, you’re right – it appears the current functionality is to drop the tables when the plugin is deactivated. We’ve discussed with our developers and they will be correcting that to only drop the tables when the plugin is uninstalled.

    We’ll update you as the team works to address these issues!

    Plugin Author bluetriangle

    (@bluetriangle)

    Hello,

    The above two issues have been addressed in the latest update (v1.8.2). Please let us know if you have any more questions or concerns!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Use DB prefix when dropping tables’ is closed to new replies.