I'm afraid I must appologise for my previous post about Bulk Delete deleting my entire blog and about it being a dangerouis plugin.
What I posted was completely accurate but I now have new information that leads me to believe that the problem was NOT with the Bulk Delete plugin.
I manage 2 WordPress blogs. One about bikes and one about credit cards. My original post was about the bike blog being deleted after using the Bulk Delete plugin.
I just now started to cleanup spam posts from the pending folder in my second blog (the credit card one) and, as I mentioned above, I did not trust the Bulk Delete plugin so I was doing this the manual WordPress way by selecting 20 entries at a time then selecting "Move to Trash" in Bulk Actions dropdown box in WordPress then clicking on "Apply".
This was very tedious because I had over 3,000 spam messages. So I had been patiently deleting 20 at a time until I got down to the last 120 posts.
Then, all of a sudden, I had the same situation as before. After I clicked on Apply (with the standard WP delete) I got sent to the Word Press initialiation page. I started a new browser session, went to my credit card website, selected the link to the blog and got the initialization page again. This has been up and running for over a year now and I have not made any changes to the blog setup.
This time I went into SQL through my control panel and checked the Word Press tables. I could see that they were still there but I still could not get to my blog - Any attempt went to the Word Press Initialization page.
As I was looking into this. I tried one more time (maybe 10 minutes later) and to my relief my blog came up again.
Therefore, I now believe that this problem had more to do with either Word Press, the MySQL database or something to do with my hosting service, like some kind of timing issue. I suspect maybe the database was in some busy state and could not process any requests until it completed what it needed to do (but that is pure speculation).
I believe that the Bulk Delete plugin probably triggered this same situation but I believe that the problem is external to the plugin.
It would be difficult to track down exactly what had happened in these situations but I wanted to post the information here in case anything like this happens to anyone else.
Once again I apologize for my previous comments about the Bulk Delete plugin as I do not believe that it was the source of the problem.