Thank you!
Now if we only knew what caused the problem to begin with so we didn’t choose the same options again.
Worked for me, thank you very much. Luckily I only have one more site using the plugin, might hold off upgrading until the next version arrives!
Thanks again Viktor.
You’re welcome. Lucky you, I had about a dozen to go through ha!
Don´t work for me, i “work” before read your solution. 🙁
maniaka, are you still having a problem with your website? Did you start a thread for your problem I can see?
Hi, Viktor:
First of all, thank you so much for the helpful information, so glad I found it here.
It is so confuse for the recently upgraded iThemes Security plugin and caused so many problems. I just upgraded to the latest version a few minutes ago, but after that, the whole site was locked out with an “error” blank page showing up. After restored db, the whole site came back, but then again. I did several times restored, but got the same thing again and again, currently, deactivated the plugin, the whole site runs normally.
After I read through your article, I have questions, can you answer for me? Really appreciate it!
– Is there any “risk” for: Delete tables with “itsec” & Delete “itsec” options??? What are these steps really for? Do those tables and data no longer useful for new iThemes Security?? Would like to know what those for? Can you explain more?
I have to deactivate the plugin to prevent further lock out the whole site, but I would like to understand more before do anything.
Thanks again for the helpful article, really appreciate it. Hope I will get answer from you soon.
Hi wpinklady,
All plugins add some sort of information to WordPress database to save settings, information, etc. This plugin does this too. Unfortunately, when you deactivate plugin – in most cases – database entries are not deleted and remain in the database.
For some reason, new version of iThemes Security has issues with database entries created by Better WP Security plugin.
The only way to fix it, is to remove old entries and allow plugin to add new entries once you re-activate it again. When you simply re-activate plugin now, it does NOT override those entries. It simply uses them, breaking your website.
That’s why deleting them fixes the issues.
There’s always some risk when you mess with database, but if you follow my instructions carefully (including backing up database), you should not have any issues. As long as you don’t delete any other stuff, you’ll be fine.
Hope that explains it.
Hi, Viktor:
Thank you so much for answering my questions, really appreciate it. I will follow your instructions and will let you know if it works or not. Thanks again for your quick respond, really appreciate it.
Hi, viktor:
Questions:
After followed your instructions, deleted those tables and data, go back to back end and reset settings. Question: will those tables disappear forever, is that correct??? If not, then what went wrong???
And, more problem, after reactivated and reset settings, why it forced back end to https, which this site does not have SSL? And, then locked out from back end, until restore the org. wp config file.
Now, getting even more problems…..getting more headache….:(
What should I do next??? Now, I have to deactivate this plugin again….
Hi,
When you delete those tables, they do disappear. BUT, when you reactivate plugin new tables are created.
SSL issue as far as I read in other threads (since I did not have that issue) is related to either wp-config.php file and/or htaccess file.
1. Make sure your htaccess file has standard code like this, delete everything else:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
If that’s what you have already, or it still doesn’t fix. Next step.
2. Check your wp-config.php file.
Make sure you don’t have these:
define( 'FORCE_SSL_LOGIN', true );
define( 'FORCE_SSL_ADMIN', true );
If you do, delete them.
If you followed above steps, and removed database entries correctly, and it still does not work. Then it’s possible it might be having a conflict with something else either theme or plugin.
I do assume your WordPress version is up-to-date, at least 3.8. If not, then it is possible outdated version has issues with new plugin.
Hi, viktor:
Question: after reactivated, the table did not recreate, so…..um…..weird…..did I do something wrong?????
The htaccess looks the same, I guess it did change the wp config file, because after I changed it back to the one before reactivated the plugin, then I can go to the back end to deactivate the plugin again.
Let me try one more time…..
Anyway, have to say thank you so much for your really really quick respond, I do really appreciate it.
Really hesitating updating this extension in case the update borks the one site I have it already installed on. I have held off upgrading any other sites because of the buggy plugin.
Hi, viktor:
Redo, so far so good…..(yes, the tables did recreate), will wait to see if they really work (please don’t lock out this time…..).
Another issue:
I posted several days ago (but no one replied), regarding this plugin conflicts with WooCommerce, don’t know if the latest version will work with WooCommerce well or not?
Viktor, thank you very much for your help today, it’s really really helpful!! 🙂
Hi, you’re welcome. Hope it does work.
Not sure about woocommerce, since one issue I had with it was resolved after I reset database. So see if woocommerce issue is fixed after all is good with the plugin.
I saw a thread that latest versions of this plugin fixed some of the issues with woocommerce and other stuff. So upgrade to latest version is in order. “Technically” upgrade should work fine now, without locking anyone out. I will be upgrading this weekend all our client websites, so I guess I’ll find out 🙂
