Support » Plugin: All In One WP Security & Firewall » Database prefix change caused website crash

  • asteeman

    (@asteeman)


    This plugin caused my website to crash. I chose to change my database prefix as recommended. There came an error message that a certain db view failed (“fatal error”) and upon viewing the site in another browser tab I got the message that I didn’t have permission to do anything. Trying to get onto the login page did not work either, gave the same error.
    The saving grace was the instruction of making a database backup, which I had done, and the detailed instructions on how to restore the backup database file on the tricks and tips FAQ page. My website works again as normal.
    Upon visiting the support forum, I saw other instances of crashed websites after database prefix changes. Until this issue is resolved, I cannot recommend this plugin.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, sorry to hear about your issue.

    Upon visiting the support forum, I saw other instances of crashed websites after database prefix changes.

    Can you share the links to the the other threads regarding this issue? I am interesting to know as well.

    Until this issue is resolved, I cannot recommend this plugin.

    I can assure you that there is no issue as far as I know. I have carried out this changes in my sites many times without any issues. Can you share more information about your server specs?

    Thank you

    • This reply was modified 3 months ago by  mbrsolution.
    asteeman

    (@asteeman)

    Hello, I found this forum entry with the same issue:
    https://wordpress.org/support/topic/table_prefix-change-crashed-my-website/

    I wouldn’t know about relevant server specifications, other than that I specified to use PHP 7 on the relevant domain. After updating the tables, the plugin checked the MySQL tables of type “view”. It found the errors of which I have a screenshot but I don’t see an option to upload that.

    After that it reported a fatal error:
    Uncaught error: Call to a member function log_debug() on null in /home/…/wp-security-database-menu.php:596.

    And then follow details on “Stack trace” at 3 detailed references to various issues with AIOWPSecurity_Database_Menu. The lines referenced are 447 (for the Stack trace), and 198, 77, and 20 for the AIOWP issues.

    • This reply was modified 3 months ago by  asteeman. Reason: Added more information
    Plugin Contributor mbrsolution

    (@mbrsolution)

    Thank you for providing the extra information. This will help the developers investigate this issue further.

    Kind regards

    asteeman

    (@asteeman)

    The developers can contact me for that screenshot with detailed information.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, how can the developers contact you? I checked your site but I don’t see any contact form?

    Thank you

    • This reply was modified 3 months ago by  mbrsolution.
    asteeman

    (@asteeman)

    Oh, I thought they would perhaps contact me via this forum as well. But I’ve added a link to a page with a contact form at the bottom of the About page, so that can be used. Thanks for pointing this out.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this review.