This page will maintain the compatibility information for the Feast Plugin. We currently support:
- WordPress 5.9.3
- Genesis 3.3.5
- PHP 7.4
Note the distinction compatibility - compatibility means we've tested for it and support it.
Not having tested it does not mean it doesn't work, it just means that you need to fix your own problems that arise from using an untested version.
Why isn't the most recent version supported?
The quick answer is that releases from WordPress aren't tested to be backwards-compatible with all plugins.
That means that they break things if they want to, and wait other people to fix it for them.
Our releases are compatible with the version they're released for, not any future unknown changes.
Support and maintenance costs around $300/month from companies that specialize in this, such as Nerdpress.net.
We do regularly update our themes and plugins for compatibility with the most recent version, but there has to be a compelling reason for it. Bug fixes, upgrades, enhancements are often useful.
Introduction of new (buggy) features that nobody asked for aren't a compelling reason for us to test compatibility for.
New versions will eventually be supported, once major issues have been identified and fixed. We send out a notification when this happens via the newsletter.
Can I update to an unsupported version?
If you have the ability to test on a staging site, thoroughly troubleshoot issues, understand the full theme + WordPress + PHP + hosting stack, there's no problem with updating.
For most bloggers, this is a waste of time. You don't make money fiddling with technical garbage on your site. There's very rarely any updates that are likely to benefit you in the short-run, except for security and bug fixes.
Releases from WordPress and Genesis (and themes and plugins) typically run on a "semantic versioning" system.
- Major releases introduce new features that aren't backwards compatible, and typically require fixes or upgrade instructions
- Minor releases often introduce new features that aren't well tested, and will require multiple iterations to refine
- Patch releases are typically fine, but we still recommend waiting a few weeks for a new patch to fix any issues caused by the previous patch
- except for WordPress itself, where "patch" is more of a "minor" release and should be delayed
Maintaining compatibility information with other plugins/software is time consuming, and not something built into our pricing model. Because of this, we do not provide guidance on the most recent plugin updates for every plugin, or every update.
When and if we become aware of an issue, we send notifications via the newsletter.
You should always test your updates on a staging site, or have a recent (daily) backup from your hosting company ready to restore if something goes wrong.
Note that compatibility issues often don't show up for days or week after an update is performed, making troubleshooting very complex.
If you're looking for a service that actively tests and updates plugins for you, we recommend NerdPress.