Upgrading to 2.1

Revolution 2.1 saw the removal of much legacy code that was marked deprecated in pre-2.0 releases. This is partially responsible for the vast improvements in speed and efficiency across the MODX core in this release.

Many of the most common and popular Extras have been upgraded and tested with 2.1 accordingly. While Extras developers have had a long time to start using the more up-to-date object-oriented API and stop using the old Evolution-style API calls, some Extras may still not work as expected or work at all. As a result it is very important to test your site in a safe environment before deploying to ensure changes in the codebase do not cause problems.

Uploading files for an upgrade overwrites all the core files. You can only go back by restoring your backed up files and database. This is why you should test before upgrading your production/live site.