Rotheblog had about 7 hours of downtime today

I have been meaning to try to figure out why the newest version of kPicasa doesn’t seem to work on my site. The developer said the most likely culprit is that one of my other plugins is conflicting with the Picasa WordPress plugin.

The main problem, is that I can only test this on the live Rotheblog site. I have been slowly working on getting Xamp installed, so I can do testing locally, but that takes time that I don’t seem to have.

So I came up with the idea today, what if there is a plugin that would reactivate all of the plugins at once, kind of like the feature to de-activate all of the plugins already built into WordPress 2.0+? I know that re-activating all of the plugins is a feature that will be part of WordPress 2.5 in march of 2008, but I can’t wait that long….

So, I found a plugin called “Activate-All” on a website called Mass-Automation. I had been here before, downloading plugins, so I trusted this website right away. I looked through the requirements, version 1.0 of Activate-All works with WordPress 2.0+, that’s me, and I glanced through the comments and I didn’t see anything negative. I did notice that the last comment was in Jan of ’07, but that doesn’t mean anything.

So, I downloaded the plugin, uploaded it to my WordPress install, activated it, and…..white screen!

Oh, Crap!

Now what, I didn’t back anything up before hand….well, don’t panic. Just rename the plugin and everything will be fine. I did that, and nothing happened. I deleted the plugin. Still nothing. Now what?

Well, I spent a ton of time trying to figure just that out. Come to find out as I read through all of the Activate All plugin page, it says lower down that this plugin does not work with WordPress 2.3. Crap. Why isn’t this listed by the requirements, and not in with the rest of the text? It was my fault for not reading further, I am ADD sometimes. But, I digest a lot of information in a given day, and sometimes I make quick decisions based on trust of a website like this one.

So, I contacted the developer and searched the WordPress forums. I also emailed my webhost to see if I could get a backup restored….and I waited. For about 7 hours. The developer of the plugin got into my website with a temporary ftp login, and he fixed it. What a nice guy, he didn’t have to do that at all considering it was my error.

He did say that the problem was the newer version of the kPicasa plugin. Apparently, when I activated “Activate All”, it activated every plugin I had on my site, including ones that I left deactivated while I tried to troubleshoot them. I knew kPicasa was throwing a php error, that is how this whole thing started, my question is, why did Activate All, activate every plugin immediately? Shouldn’t it have added a button for me to control that? Kind of like the “De-activate” all button? So, while I knew a white screen meant a php error, and that kPicasa was causing it, everything basically falls back on the fact that Activate All will trash your site if you use it for WordPress 2.3. Going back to, read everything and don’t be like me….

That is why there was downtime today. It really got me thinking about the responsiveness of my host. I still haven’t heard from him, and it is over 12 hours later. This is just not acceptable of Marty Hoskins can be helpful, but lately he has been non-responsive, and even when I do get a hold of him, it can take an hour or so. Granted, he is one guy and he does a good job of answering all support emails, but I am at a point where I need answers quicker, and I would be willing to pay a little more.

So, I am at a cross roads a little bit. I did some research today into Bluehost. I really like what they have to offer, and I may try to get both of my sites switched over to them. Plus, I learned what the terminology Add-On domains means…multiple websites hosted with one hosting account, which is something I really want to do.

For now, things are working again. Thanks for being patient today.