Security Scan killed my blog (MySql db) Panic Time

  • jamesisin

    (@jamesisin)


    15 years ago

    I installed the plugin Security Scan and ran it. It recommended a couple of changes. One of which was altering my php database so that it wasn’t using wp_ as a prefix. I chose a new prefix and clicked the Start Renaming button. It changed much and failed on item (“Changing values in table wp_usermeta 1/3: Failed”).

    After that I was taken to the initial word press quick start page (as in no blog yet the beginning). I could use a little help with the giant UNDO button.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter jamesisin

    (@jamesisin)

    15 years ago

    The size of my ibdata1 file has not changed, which leads me to believe that my blog is merely no longer pointing to the MySql database correctly (rather than that the database is gone or corrupted).

    If that helps any…

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    15 years ago

    Did you change your configuration file?

    Thread Starter jamesisin

    (@jamesisin)

    15 years ago

    Can you give me a bit more information? File name? What ought I change?

    Thanks.

    Thread Starter jamesisin

    (@jamesisin)

    15 years ago

    Oh, I see. You mean my config.php file in WP…

    Ok, if I change that from wp_ (around the tenth line or so) that ought to point my blog at the correct MySql db?

    What about that one line of failure I mention above?

    Thread Starter jamesisin

    (@jamesisin)

    15 years ago

    So, I have made that config change (d’oh!). My blog is back. I am still slightly concerned about that one line of failure:

    Changing values in table wp_usermeta 1/3: Failed

    Should I be?

    Oh, and from the shores of Tripoli, er Ballard, I thank you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Security Scan killed my blog (MySql db) Panic Time’ is closed to new replies.