Businesses have been hiring programmers for decades now. Back in the 70s it was something only Fortune 100 companies did. Today everyone from your local cafe to full-fledged software companies do it. Unfortunately few now how to hire a programmer.
Nearly every-single business outside of the tech sector gets screwed when paying an outside agency to write their apps. If you’ve hired a programmer recently it is very likely you are on that list. If you don’t think you’ve been screwed, you are likely just wallowing in a pool of naivety as your coder-for-hire laughs all the way to the bank.
Testing Store Locator Plus with lots of locations is a chore. Thankfully Cypress.IO data list processing makes this a lot easier.
It turns out that the old-school Selenium IDE scripts that we’ve been using to test Store Locator Plus for years will no longer work. We already knew Firefox versions beyond 54 broke things — but we kept an old install on hand so while we port 500+ test scripts to a new system. What finally broke the old-school Firefox bandaid was moving Store Locator Plus towards a reactive application using Vue.
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: