the_target

I resolved the issue by manually reinstalling the plug via FTP. Set to overwrite files and now working perfectly. Premium users can get manual installation and license key info at:
https://kb.yoast.com/article/34-how-can-i-update-my-premium-plugin#manual

Hope this helps.

Confirmed. Same issue here.

How can 4-5 words be too long for an SEO title?

Not resolved.Pagespeed still says to leverage browser caching for this New Relic js; even though it should be on the page at all.

White Screen here as well.

So the only resolution to the white screen problem is to uninstall the plugin as described above including modifications to .htaccess? Or did I miss a more practical resolution?

Got the better-wordpress-security directory renamed and this time the plugin became Deactivated. Deleted the directory and will remove all aspects of it in the database.

This used to be a solid tool, not so much anymore.

Tried removing the RewriteRule in .htaccess. Also failed to resolve problem.

# END Ban Users
# BEGIN Hide Backend
# Rules to hide the dashboard
RewriteRule ^/XXXXXXX/?$ /wp-login.php [QSA,L]

# END Hide Backend

Just tried uploading 4.2.13 to the server to see if this would resolve the issue. This also failed to resolve the issue.

Just tried uploading 4.2.13 to the server to see if this would resolve the issue. This also failed to resolve the issue.

Interesting that even with the directory name changed, the system still emails me database backups and notifications of files that have been changed. Still haven’t resolved the issue.

Tried renaming the “better-wp-security” directory to “better-wp-security-old” to cause the plugin to enter a deactivated state.

Made no difference.

I decided to take a simple route regarding this 4.0.5 problem.
The objective was to get Better WP Security into a “deactivated” state.

What I did:

1. Using an FTP client, I renamed /wp-content/plugins/better-wp-security to /wp-content/plugins/better-wp-security-old

2. This allowed me to login into the WordPress admin interface.

3. Once in the admin panel, going to “Plugins” will show that Better WP Security has been disabled due to an error.

4. I returned to the FTP client to restore the /better-wp-security folder name.

5. The current state is that the plugin will sit until I see that a version 4.0.6 or higher has been released to remedy the situation.

Also using the W3 cache and Liveblog functionality is not displayed on the blog entry.

Just updated and it worked perfectly! Very well done.

Also tried a plugin called “Twitter Embed” that didn’t seem to help either.