I got the same error after update…had to disable the plugin via ftp.
I am getting same error as soon as i updated it.
Fatal error: Call to undefined function is_user_logged_in() in /hermes/bosnaweb04b/b2980/ipg.kajlabroscom/kajlabroscom/wp-content/plugins/better-wp-security/modules/free/hide-backend/class-itsec-hide-backend.php on line 213
hey I solved this and my site is online now,
delete the plugin file with a file manager and disable the plugin manually from database, in option table you will find all the activate plugin entry. delete this line from the field
i:1;s:41:"better-wp-security/better-wp-security.php";
now reinstall the plugin I hope everything will be ok then.
Seemed to update OK on an individual WP install but messed up on my WP MU install. Good thing I use a dedicated server with my own backups. I suggest waiting to update this until it is to the next version.
Good luck all!
I got the same fatal error after upgrading to iThemes Security Pro 1.5.8. I replaced 1.5.8 with an earlier version from a BackupBuddy backup, and that solved the problem. I will probably wait until iThemes fixes the bug before trying another update.
You are working on this bug, right, iThemes folks? 🙂
This is the first glitch I’ve experienced with iThemes Security/Better WP Security in an otherwise stellar track record. I have total confidence in the iThemes talent so expect it will be fixed soon.
Cheers,
Melissa 🙂
delete the plugin file with a file manager and disable the plugin manually from database, in option table you will find all the activate plugin entry. delete this line from the field
i:1;s:41:”better-wp-security/better-wp-security.php”;
I haven’t been able to find this in the database.
I’m pushing 4.2.13 as we speak. Melissa, I ain’t going to bed until I can squelch this. The odd thing is it doesn’t happen in any of our testing sites.
30 seconds till 13 is up.
4.2.13 is up. Please verify it works for you and I’ll mark this ticket as resolved.
I just successfully updated to 1.5.9! Woohoo!!!
You guys are the BEST.
Thanks a million!
m. 🙂
Thanks for the update! My apologies for the frustration
No worries and thank YOU for springing into action so quickly!
Happy coding,
m. 🙂
@hlanggo
Open phpmyadmin then go to the wp_option table (it can be any_option) and find option id 36 and check its value.
@author, thanks for fast action, the ticket is resolved then 🙂
@asifsaho
It seemed to have been disabled automatically. When I went to the Plugins page, there was a notice stating that it’s been disabled due to error cause the plugin folder was deleted.
@hlanggo may be but my situation wasn’t same 🙂 anyway is your problem solved?
Looks like it though I have decided to disable this plugin on two of my websites. This is the second time an update broke the website.
