[Plugin: WP Security Scan] CAUTION: SCREWED-UP MY BLOG!

Claiming that you didn’t do anything else is pointless.

I saw the error message from your site that said it was looking for a file you renamed.

The plugin doesn’t rename any files. You even said in an earlier post that you renamed files from wp- to jp-. Never in the history of WordPress has anyone ever said to do that.
You misunderstood that the purpose was to rename the database tables from wp_ to something other than wp_.
The plugin’s code can not change any file names, and it can not overwrite any content in the database. It is not possible.

You’re correct that for a very few users, the automatic table renaming functionality doesn’t work (I told you this a few posts ago). However, it just simply doesn’t do anything, and gives you a message as such. That has nothing to do with your issue.

I’ll say again, you should have read the documentation and/or asked before doing something that you obviously had no clue about, leading you to change WordPress core filenames.

Considering that the website in my profile is the same website for the plugin and also that WP Security Scan is under my profile, yes, obviously I’m the author of the plugin.

Really aside from the renaming of files,,, that was all me and no blame on your software for that. It’s late and I didn’t have any ideas…

But it did do just what it’s supposed to do and go out in the database and change all the tables prefixes… and it worked damn fine too.

What happened after that I really don’t know. but when it renamed the tables something happened and it took me down a merry path… not one that I wanted to go do this late…
For the record I changed the files on my server not the tables. one part was my fault in response to it’s changing my database tables… I’m not a database geek so I called them files.. sorry and it caused confusion. But what it did to my blog was real everything after it’s damage was my fault and it caused me a few hours to correct the files.
I’m now reconfiguring the blog so it’s not too pathetic looking.
Jeff

I’ve ended with a “screwed” site so I might post my wishes here.

It’s all about changing the DB prefix. I suggest to check if wp-config.php is writable before doing the DB edits. Mine wasn’t but DB has changed. WP naturally couldn’t find any tables and rendered “install” page.

I changed the config file manually (or I could change the permission of course). But a newbie could feel rather desperate if something like this happens and he/she doesn’t grab it.

Hope I didn’t miss above proposed improvement somewhere in previous posts.

Keep up the good work,
m.

Mellthy,

The plugin does check to see if wp-config.php is writable, if it isn’t it tells you to do it. If this didn’t happen, please email me at michael (AT) semperfiwebdesign (DOT) com to report a bug.

Forums are a great thing, but I specifically ask in the documentation and in the plugin (where a link is provided) to email me with any bugs, comments, or suggestions. I can’t possibly monitor every forum post, especially when ones like this are filled 80% with people who are incorrect and just venting their unrelated frustrations.
I don’t believe you fall into that category. If this is the case, please email me so we can determine if a bug exists in the situation you describe.