Upgrading from 2.0.5
Last updated Oct 10th, 2026 | Page history | Improve this page | Report an issue
Support the team building MODX with a monthly donation.
The budget raised through OpenCollective is transparent, including payouts, and any contributor can apply to be paid for their work on MODX.
Backers
Budget
$185 per month—let's make that $500!
Learn moreUpgrading to Revolution 2.0.5¶
This upgrade process applies to you only if you:
- Use Form Customization
- Have a custom Access Policy
- Use the
extension_packagessetting
If you use none of these, skip this page. If someone else set up your site, ask them whether any of these are in use before upgrading.
Back up your database before upgrading. If the upgrade goes wrong, post on the forums.
Form Customization Updates¶
Form Customization was rewritten and now only works on Resource pages. On upgrade, the following are erased:
- Rules not targeted at Resource pages.
- Inactive rules — 2.0.5 has no “Inactive Rule”, only inactive Sets and Profiles.
The rewrite cut FC to Resource pages, and the old rule editor was powerful but confusing.
An FC “Set” is a collection of Rules for one page (create or update a Resource). Constraints belong to the Set, not the rule, and Sets can target specific Templates. A “Profile” is a collection of Sets, restricted to User Groups, active or inactive.
Four new tables and classes:
| Table | Class |
|---|---|
[prefix]_fc_profiles |
modFormCustomizationProfile |
[prefix]_fc_profiles_usergroups |
modFormCustomizationProfileUserGroup |
[prefix]_fc_sets |
modFormCustomizationSet |
[prefix]_actions_fields |
modActionField |
Your old rules migrate automatically: UserGroup restrictions become separate Profiles, and within them rules are split into Sets by page type (create or update) and constraints, since constraints are now set-based. You then edit rules inside a Set in the UI.
Access Policy Updates¶
An Access Policy Template holds a list of Permissions you add to or remove from — what an Access Policy used to be in the UI. An Access Policy itself now shows a checkbox list of Permissions from its Template, so defining a policy is a matter of checking boxes.
To create a manager policy, base a new Access Policy on the Administrator Template.
Old policies upgrade into the Administrator Template if they used only Administrator permissions. Custom policies with their own Permissions get a generated Access Policy Template.
extension_packages Changes¶
The extension_packages setting changed to JSON. The old format:
package_name:package_path,another_package:another_path
The new format:
[{"package_name":{"path":"package_path"}},{"another_package":{"path":"another_path"}}]
Existing settings upgrade automatically; you do not adjust them by hand.
See Also¶
- Troubleshooting Upgrades
- Upgrading to 2.2.x
- Upgrading from 2.0.x to 2.1.x
- Upgrading to Revolution 2.0.0-rc-2
Support the team building MODX with a monthly donation.
The budget raised through OpenCollective is transparent, including payouts, and any contributor can apply to be paid for their work on MODX.
Backers
Budget
$185 per month—let's make that $500!
Learn more










