While waiting for bug fixes, then working on testing for:
- Genesis 3.3
- WordPress 5.4
- Yoast 14.0
Multiple updates rolled out including:
- a major Google core algorithm update on May 14
- new schema for recipes on May 20
- a major pagespeed insights update on May 28
- what appears to be some changes in Chrome some time in between
Minor releases (Genesis 3.2.2, WordPress 5.4.1, Yoast 14.1 + 14.2) have come along that further compounds this.
Due to the interactions between all these elements, there's no possible way for us to verify compatibility or draw connections between changes.
#1, #2 and #3 can all affect #4, #6 and #7.
If these changes were spread over the course of a year, it would be a busy year. The fact that they've happened in just over a month makes them unmanageable.
And because of #6 (the pagespeed insights update), we're expecting significant updates to WP Rocket, further compounding the issue.
There's no longer any usable benchmark, and there's no possible way for us to support thousands of different customers and their configurations. This is because troubleshooting is complex and time consuming.
Is anything broken?
We're running the following versions on all demo sites and there doesn't appear to be any theme or Feast Plugin related conflicts:
- Yoast 14.2
- Genesis 3.3.2
- WordPress 5.4.1
Any issues or bug fixes that we can detect and automatically roll out via the Feast Plugin will be done.
We'll be restricting support for update-related issues to very quick tickets: if we haven't seen it before or can't trace it to a very specific theme or Feast Plugin root cause within 5 minutes, then we'll have to pass on the ticket.
This is because our pricing model simply isn't built for time-consuming support of third party plugins.
This is a "best effort" on our end, but ultimately, these third-party plugins are not our responsibility to support. It's the third-party plugins responsibility to support themselves. That's what you pay them for.
Alternatively, you can sign up with NerdPress and pay them for maintenance.
Note that updating Yoast from pre-14 to post-14 will prompt you to reindex/"speed up" the database.
We have no idea what this does and can't offer advice about it. Make sure you do it on a staging site first.
How to do updates
The best way to approach updates is to perform them:
- on a staging site
- one per day
This increases your chances of noticing any major problems. Here's some tips:
- don't perform updates on the same day they're released if they're major updates
- prioritize older updates first
- clear your multiple levels of caching
- visually check your key pages:
- category page
- top recipe pages
- run these pages through:
- structured data testing tool
- rich snippets testing tool
- pagespeed insights
- don't perform multiple updates simultaneously
Sound overwhelming? Hire Nerdpress to manage your plugin updates.
You can also find this additional guide to updating plugins from Nerdpress!
Compounding all these changes is the fact that caching keeps old CSS and JS around longer than reasonably expected. We've seen an increase in "issues" that were no more than caching problems.
We have a guide to clearing your caching, but this still requires an intermediate/advanced level of knowledge.
As the themes and Feast Plugin don't implement or directly affect caching, any issues we deem to be caching-related will be tagged as such and closed. Please contact your caching plugin provider and/or hosting company for additional support.
Unfortunately this is all further compounded by the fact that you don't have a perfect knowledge of what's happening on your site.
VERY frequently we'll get a support ticket from someone who "suddenly" noticed a big change and attributes it to the wrong thing.
A setting that was changed a month ago, or a plugin that was installed previously, doesn't become noticeable until you update another plugin or clear a cache.
Often, the problem exists for weeks before a notification arrives from Google Search Console or a user complains about it. But because the site owner only becomes away of it today, they attribute it to something they did yesterday, incorrectly.
This is why troubleshooting is so complex and why we can't spend hours on every site for every problem. We only support a very limited set of configurations and plugins.