All available WordPress updates were applied to auxiliary WordPress sites. Does anyone actually read these posts?
All available server updates were applied. All had important ones and were rebooted except to dev servers, but none had any so important as the PHP update that broke a couple websites last week.
All available updates were applied to auxiliary WordPress sites.
All available updates were applied to servers. No time for a joke — busy, busy busy! PS: the updates to PHP broke OPN and CURep. In addition to reconfiguring Apache httpd, a new build of Xapian and its PHP bindings was required to fix the issue. All is well now.
All available updates were applied to auxiliary WordPress sites. It was a pretty intense day. Stock themes were all updated, and the WordPress core was updated, and also some plugins. The core is now apparently sensitive to PHP version and warns you if you have an older version. I’m not sure I like that, mainly […]
All available server updates were applied to … you guessed it … servers! They all had to be rebooted because of one or another. A few servers got some pretty intense updates. It was an exciting time to be a server admin.
Most auxiliary WordPress instances had no updates, but on those that did, the application of updates happened. And now it is a better world.
All available server updates were applied. Only Ubuntu servers had any, and those were deep, so all the Ubuntu servers were rebooted. The RHEL/CentOS servers had no updates available, so I’ll let them age another week at least before they get a reboot.
All none available WordPress updates were not applied to auxiliary WordPress sites.
All available updates were applied to servers. Not all had updates, but the ones that did had updates to rather important web-related packages. All updated servers were rebooted.