If fresh install breaks site, then my solutions would not help. Either plugin is broken or some compatibility issue.
Hi Victor,
I did an upgrade from 3.6.6 to 4.0.27 and then to 4.1.3.
I’m just hoping that the plugin makers take their responsibility and come up with a working version. If I have to fix all my WP sites, it’s just too much work.
Oh ok, yes upgrading from 3.6.6 to later versions does cause issues in the database. In this case, my fix would work most likely… but it is time and work intensive and is only last resort to restore broken website.
So, it’s impossible to upgrade from 3.6.6 without having problems? They are awfully quite about this.
Some people were successful as far as I’ve seen, but based on frustration on this forum not everyone was lucky.
Everytime I click update on this plugin, which seems to update every week (insane), it breaks the site.
My solution is this, which seems to work:
1. after updating, if your site is blank, and cant log in, goto your cpanel, into file manager, and into the plug-ins section, and rename the plugin temporarily to turn it off, e.g. better-wp-security-OFF
2. then log-back into wp-admin,
3. then go back to file-manager, re-name the plugin back to it’s original name.
4. then go back to the website, click plug-ins, and re-activate, and it should be ok.
a plug-in shouldnt be this hard, it’s exhausting……
Well, in my case, Victor’s solution will probably help. What I’m not looking forward to is doing this for more than 30 websites. I’m considering to stay at 3.6.6. and go to 4+ with websites that need a bit more attention.
