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 2016-09-27.
Our Premium Extras typically require:
- MODX Revolution 2.3.x, 2.4.x or 2.5.x;
- PHP version 5.3.3 or up;
- 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 will end 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.
Additional or different requirements may be necessary for specific Extras on top of this baseline, especially new extras. This will be clearly mentioned in the documentation for that specific Extra if so.
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. However it is possible that there are issues with our extras in unreleased versions. If issues are identified, we'll try to resolve them prior to the stable release.
If new stable releases of MODX are made available, here's what happens.
- For core bug fix releases (e.g. 2.4.1 is released following 2.4.0) we expect all our extras to continue to work as expected and no minimum versions are changed. We recommend staying up to date at all times.
- Feature releases (e.g 2.5.0 is released following 2.4.4) are usually backwards compatible, but new features or changes in design may require us to make changes to our extras. To catch these, we test our extras in these new feature releases and will publish a blog post within 2 weeks of the stable release with any known incompatibilities. Following a new stable feature release we also deprecate the older feature release, which will reach end of life one year after the initial announcement.
- Breaking releases (e.g. 3.0 is released following 2.x) are called breaking for a reason, so we're unable of making a commitment for our Extras prior to seeing how big the breakage is. We might choose to deprecate an extra, release updates that work around the breaking changes, develop ports specific to the new release or something else entirely. Following a breaking release we'll evaluate what it means for each of our extras and announce detailed plans for each of our extras within a month of the stable release.