I’ve written articles on Jetpack Autoupdate before — you’ll find some of them in the Jetpack blog. For many neglected sites autoupdate of plugins is a good idea. Plugins often have security patches that you should not ignore. Sometimes they have compatibility updates to allow them to work with the latest update to WordPress.
However autoupdate of ANY software, whether on your phone, desktop computer, or mobile device is only as good as the software doing the update. Over the years I have yet to find a single software company that can publish a 100% never-fails update to their software stack. Of all the companies that are pushing software, Apple seems to be the least prone to fatal crashes — the kind that take your business or personal productivity offline for hours or days. They are not infallible by any means and introduce plenty of “oh, that’s a pain in my ass” bugs on a regular basis.
Even season veterans such as Till cannot escape the millions of combinations of site installs that may create corner cases that break software. Something in the latest 1.3.6/1.3.7 updates to his plugin, or possibly changes to WordPress, or changes to the underlying operating systems or PHP have broken the Redis Object Cache plugin.
This will manifest itself as a non-responsive website , usually with a basic 500 (Internal Server Error) reply.
The quick fix is to disable REDIS by adding this line to your wp-config.php file:
define( 'WP_REDIS_DISABLED' , true );
This will force the object-cache.php file that the plugin has you move into the WordPress root directory to not run any of the code within.
Wait for a future Redis Object Cache plugin update before turning it back on.
If you are running your own Linux server — an AWS EC2 instance, perhaps, you may want to check that your etc daemon I’d not accessible.
Read this ARS Technica article for more info:
An interesting article I found in my Google News feed today from Venture Beat:
“WordPress now powers 30% of websites”
WordPress now powers 30 percent of the web, according to data from web technology survey firm W3Techs.
It’s worth noting here that this figure relates to the entire Web, regardless of whether a website uses a content management system (CMS) or not. If we’re looking at market share, WordPress actually claims 60.2 percent, up from 58.7 percent in November 2015. By comparison, its nearest CMS rival, Joomla, has seen its usage jump from 2.8 percent to 3.1 percent, while Drupal is up from 2.1 percent to 2.2 percent.
After discussing projects over the past week, one of the guys at Automattic brought up CypressIO. If you’ve been following the recent posts on Lance.Bio you know that the path to running automated web testing has run from Selenium IDE, the QA tool of choice for the past few years for Store Locator Plus, to recent forays into Selenium Webdriver. Webdriver is powerful but difficult to code and soon led to the discovery of WebdriverIO, then Mocha and Chai on top of that. The new stack makes it easier to write more advanced tests than we could in Selenium IDE — but it was like pulling teeth to get all the right pieces installed and working.
More info, less pain
That is what CypressIO promotes on their home page. “Test your code, not your patience.” and “No more async hell.” — if you’ve gone through the Selenium Webdriver setup you’ll understand what both of these mean. It takes several false starts to understand all the pieces you MUST install to get Selenium Webdriver working. CypressIO has made it easy; it is even easier than they promote on their website with the most recent builds.
I’ve only started simple test writing but in less than 20 minutes I had a fully functional test running with all the extras from a completely “clean” install base. If you have NodeJS and NPM up-to-date and a faster Internet connection than we have in tech-orphan Charleston South Carolina, you can be up and running in 5 minutes.