We want to be open and transparent about what is and what isn't supported when it comes to our Premium Extras and other offerings. This page provides information about those minimum version requirements and how we handle new releases of MODX.
This page was last updated on 2017-04-25.
Our Premium Extras typically require:
- MODX Revolution 2.5.x or up;
- PHP version 5.3.3 or up; increasing to 5.5.0 on July 21st, 2017
- All requirements that are needed for MODX
Active support for MODX Revolution 2.2.x ended on July 16th, 2015 (see announcement).
Active support for MODX Revolution 2.3.x ended on August 19th, 2016 (see announcement).
Active support for MODX Revolution 2.4.x ended on April 22nd, 2017 (see announcement).
We do not typically support:
- MODX sites using database drivers other than MySQL (sqlsrv, postgres etc).
- Pre-releases, latest development from Git.
There may be additional requirements for specific extras. Keep an eye out for requirements in the related documentation.
Future MODX Releases
We try to keep up with what's happening with MODX, and test our extras in upcoming releases before they are available. If incompatibilities with upcoming MODX versions are found, we aim to fix those before the stable release.
To ensure our requirements stay fresh and predictable, here's how we handle new MODX releases.
- For core bug fix releases (e.g. 2.5.7 is released following 2.5.6) we don't expect any issues and will treat anything that does come up as urgent bugs.
- Feature releases (e.g 2.5.0 is released following 2.4.4) are normally backwards compatible, but new features or changes in design may require us to make some tweaks to our extras. We'll test this during a release candidate phase if possible, and will publish a blog within 2 weeks of a new release if there are any known issues at that time. Following a new feature release, we also deprecate the previous version. We'll continue supporting the previous version for one year, after which we cease active support.
- Breaking releases (e.g. 3.0 is released following 2.x) may require a lot of work to support. We'll evaluate the impact of breaking releases on our extras as soon as possible, and aim to publish a detailed overview of our plans for each extra within a month after the breaking release. Updates to support a new breaking version may require an upgrade fee.