This blog post contains information about WordPress 5, GDPR and the Cerber security plugin. Also read about how I was able to connect the versions of my book on Amazon.
While doing a quarterly WordPress update for a customer, we spotted a mystery file at the root of the WordPress installation. It’s a hosting_provider_filters.php file.
If you’re new to WordPress you might be dismayed to find that there are two WordPress websites, WordPress.org and WordPress.com. Both sites provide resources for people that want WordPress blogs or websites. The key differences are hosting and restrictions.
WordPress 5 is scheduled to be released this year. It’s NOT a typical release. It contains one change that’s causing a huge amount of debate. WordPress 5 will replace the editor with an entirely new system.
I’ve had an interesting few weeks. Just when I get a handle on one issue, another one pops up. Most of the challenges involved contact forms. Here’s the scoop . . . .
Cerber’s problem with flagging old URLs as “probing for vulnerable PHP code” has been fixed.
In a recent security scan of a client’s site we found a mystery file located at the root of the WordPress installation. It’s a ssv3_directory.php file. A little Internet research lead me to believe that it’s a file that BlueHost installs. So I started asking some questions . . .
In the past I’ve used the Limit Login Attempts and IP Filter plugins to keep WordPress sites safe from brute force attacks. I’m now using WP Cerber.
Here’s the scoop on WordPress 4.8; there aren’t as many problems as I’d feared, but there are more than WordPress would lead you to believe.
SG Optimizer will go through all the code for your theme and plugins looking for things that won’t work with PHP 7.0. Once the plugin is done with its analysis, it gives you a list of any problems that it finds.