Is it safe yet to accept the 6.1.1 plugin update?
-
We have been reading posts for about a week about how The Events Calendar plugin upgrade to version 6.1.1 has been throwing fatal errors that result in broken websites.
In our correspondence with the developers, we were told they are working on a fix to the reported issues, but that a 3-day weekend for Juneteenth slowed their efforts.
Then, everything went silent, and we haven’t heard anything.
We are still seeing a few posts about issues with the latest update.
When can we get an all-clear, or see a newer version that addresses the fatal errors already reported in this support forum?
-
Well, fortunately, for us — we have learned our lesson the hard way and have not even attempted to try any updates, or tests, at all. Rather, we also are relying on the reported stack traces, tests, and end-user reports to determine when the “dust has settled” on this update.
Once we see reports that no more fatal errors exist, we’ll begin our own testing regimen to confirm no more errors exist. And, we also have the paid version, by the way, and utilize that for extended support once we actually begin our own testing routines, using ITIL framework to ensure all parties are involved in the testing.
But, we start here, in the public domain to see what the larger population is experiencing first.
Unfortunately, this is not the first time this has happened with Events Calendar updates, and so we have let our IT team know to view all future plugin updates with a wary eye — watch the support forums first, then test in a staging/test environment.
But, lately, in the last 18 months, there have been at least two updates that have completely crashed websites — I mean literally wiped out the home page. So, we’re not taking any chances.
I do have to say, this has been the most problematic plugin we use, when it comes to updates.
I strongly recommend improved testing methodologies that are based on knowledge of your overall audience.
Thank you for your reply. It seems most serious and considerate. But, it does seem some industry standard testing methodologies that used to be employed might have gone wayside: ITIL V4, for example. AGIL methods? Are you using them? Regression analysis and testing? Github? (I can only hope.)
If there are “too many themes and plugins to keep up with,” then maybe you’re not keeping up.
Again, you should limit your scope of support — but make it clear what you support, to your end-users. Update your automated-testing to weed out unsupported devices and browsers, and to throw out an automated notice that can be used to inform end-users!
For example, in my line of IT dev work, we had to stop support on older versions of Apple software and completely stop support of Internet Explorer browsers. This was several years ago. We were able to send a mass email to the entire enterprise (several tens of thousands of users) to update, or change, or go unspported.
But, it remains a stark example.
Your plugin update notices might need to include a notice of what still breaks, and why it breaks, and why it is NOT supported, or NO LONGER supported. Etc. That kind of thing.
But, without such notices, the unexpected happens — everyone, everywhere just expects your plugins to magically work everywhere. That’s unrealistic.
- The topic ‘Is it safe yet to accept the 6.1.1 plugin update?’ is closed to new replies.
