The first thing I did was go into MyPHP and removed plugins from cpanel. I could not get into my admin dashboard from wp.
http://www.hiddenwebgenius.com/blog/web-development/deactivating-wordpress-plugins-using-phpmyadmin/ Deactivating WordPress Plugins using PHPMyAdmi
I don’t know anything much about cpanel… and I easily followed this advice. (When you clip and paste their SQL command, their web address is cited. Of course, just delete that portion so it’s just the SQL command.) Please make sure you follow their advice to copy what is in your active plug-in list. That way, if you make any mistakes, you can simply restore things to as they were and start over. (I saved mine in Word.)
So, if you cannot get into your wp admin panel, you remove the plugin through cpanel following those instructions above.
For me, even after I removed this plugin, I still had problems. Called. They told me I had way high CPU usage when my page would load. You can check this from your cpanel. Load your page… and watch and refresh your cpanel page where it has the CPU usage bar. That was the problem.
In short, remove the plug-in, but check your CPU usage and probably call your hosting company to check your hosting out.
I called, and my host company at first said it was probly my plug-ins. I have a lot. (Wasn’t this plug-in. I’d already removed this plug-in and I had a problem before this plug-in… just not so dramatic.)
Host company told me to go through and remove all my plugins, delete them, and reinstall by one. Test CPU usage after each install… see what plugin was causing the problem trial and error. (Note, I did not want to deactivate any plug in where I might have to reconfigure. Like Askimet, etc. I doubt Askimet was the problem… more likely a homebrew plugin not a professional at that level. So, I did not take his advice to remove them all. But I deleted 90%.)
Then, I could not reinstall even one plugin. Problem between server and wp communication.
So, I called hosting company. This time, they looked more in depth at their server side… and it was their server. So, took a little time and they fixed their server. Since then, I have not had any like problem. (But, they were very pleasant, nice, and helpful when I called… and it made sense to tell me to try to remove plug-ins to try to find the problem. Go Daddy has been very pleasant to work with, and I am not at all upset that they had a server problem and at first told me to remove my plugins as part of the “testing to see what it is wrong”. I give them an “A” for service… plus, they made it super ez for me as a newbie to buy their hosting, set up my site, and communicate with them. I think they’re great! 🙂
**I have not yet re-installed this plug-in. I am going to get all of my design stuff done before I concern myself with cache, compression, and minify. If you go to my site, you will see my load time is still slow. I really need these cache, compression, minify, etc. plug-ins.***
So, before I make an effort to re-install or install any security plug-ins, it is necessary to look at them and read up to see which conflict. Even in their details in the plug-ins, they will tell you if one security plug-in conflicts with another. I’d advise, when re-installing, really check that out and read other wp user knowledge base whereever it’s found on plug-in conflicts.
Also, please make certain to do the backup of your site that you can restore to “before I installed the plugin”. Probably very good advice before install of ANY plugin, but security plugins are necessarily trying to compress and minify your data… it’s what they do… so they are reconfiguring some things. Very important to do backup, even especially, before any install of a security plugin.
So, that was the advice of the hosting company, that’s what I did, but it was truly server side.
So, I want to be clear that in my case, this plugin was “not to blame” for my white pages.
I appreciate the developers for their hard work in creating this plugins for free… and I think the proper thing to do is after a site is all put together, and when it makes money (if it’s a business site), or when it’s set up and creates enjoyment as a hobby or non-commerce site, to donate to them.
I certainly don’t want to give anyone a wrong impression that it was the fault of this plugin why I had the problem, when it was server side before and after install of this plug in.
That’s my long advice! Ask me for advice, I give it! 🙂 lol I even advise all to donate to these hardworking volunteers who create and make available “free” plugins. They are not volunteering, really. They are providing a free service in the hopes that people will use their free product and voluntarily compensate them after the fact. It’s a lot of hard work they do, and I really appreciate them.
Best wishes with your site!
