• I used this plugin to change the table prefix. It changed it to a butt-ugly, random prefix. So I decided I want to choose my own table prefix. Every time I try, it says “Error – Could not get tables or no tables found!”

    The question is, why was this plugin originally able to change the table prefix, but afterwards unable to change the table prefix? I didn’t change the database name or login information in wp-config, nor do I have any problems with accessing the database or the website itself. So it must be this plugin (Better WP Security) that prevented any further changes to the table prefix.

    Another thing is, this plugin says it changed the login page url, but I can still access my-site//wp-login.php So obviously that did nothing to improve my site’s security. By the way, I can not log in to my site through the new login url that Better WP Security supposedly created.

    https://ww.wp.xz.cn/plugins/better-wp-security/

Viewing 4 replies - 1 through 4 (of 4 total)
  • @martin Pierce

    Assuming both change database prefix attempts were performed within the same WP Dashboard session my, guess is that you are running into a bug.

    Try it again after logging out and logging back into WP Dashboard.

    dwinden

    @martin Pierce

    I used this plugin to change the table prefix. It changed it to a butt-ugly, random prefix. So I decided I want to choose my own table prefix. Every time I try, it says “Error – Could not get tables or no tables found!”

    I used this to change my prefix but make sure when you try to change the prefix again, that you are using the new butt-ugly random_ prefix_ and not wp_ since that no longer exists now that you’ve already changed it. I also made sure that the prefix in wp-config matches the new prefix. So put the butt-ugly random_ prefix_ in to wp-config, save, then try to login to your dashboard and change it to one you prefer. I think that is causing the message no tables found.

    I am no wizard at this stuff but it is what I did. Hope it helps!

    Best Wishes

    Thread Starter Martin Pierce

    (@martin-pierce)

    dwinden, both change database prefix attempts were not performed in the same session. Initially, that may have been the case, but I logged out, cleared my cache, and tried to change the database prefix again on another day.

    Summer, sorry but I don’t understand what you’re trying to say. Here’s my response to what you seemed to be saying…

    Entering the same prefix will not result in a new prefix. wp_ no longer exists, but by the same token, the same is true of any prefix that I may put in the blank field (other than the buttuglyrandomprefix, which I clearly do not prefer).

    FYI, the “butt-ugly” prefix is hx0iemubt7_ (I changed it slightly for security purposes). You seem to be saying that I should enter hx0iemubt7_ again, as if that would make a difference. However, I don’t think you would say that since that would make no sense. Please clarify. Thank you.

    Martin

    My quote: Technology makes idiots of us all, except for the “geeks”.

    Thread Starter Martin Pierce

    (@martin-pierce)

    Summer,

    In summary, I don’t see a difference (from a technical standpoint) between entering as a new prefix:

    wp_ (which surrenders any security I might have wanted)
    wp123_
    hx0iemubt8_ (slight change to hx0iemubt7_)

    Or even something without the underline such as:
    wpabcd

    Martin

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Plugin Permanently Resets Table Prefix’ is closed to new replies.