Skip to content

docs(3.0): 2.6+ upgrade floor, notable manager UI, CRC processors - #617

Open
Ibochkarev wants to merge 1 commit into
modxorg:3.xfrom
Ibochkarev:docs/issue-121-upgrade-floor-crc-ui
Open

docs(3.0): 2.6+ upgrade floor, notable manager UI, CRC processors#617
Ibochkarev wants to merge 1 commit into
modxorg:3.xfrom
Ibochkarev:docs/issue-121-upgrade-floor-crc-ui

Conversation

@Ibochkarev

Copy link
Copy Markdown
Collaborator

Description

Setup refuses upgrades from MODX older than 2.6.0 (version_compare(..., '2.6.0', '<') in modinstallrunnerweb.class.php). The 3.0 upgrade index still read as any 2.x and only recommended 2.8 for deprecation logs. 2.8 stays the recommended stepping stone after 2.6.

The CRC overview still said "2.2 and later only" and the tutorial copied core/model/modx/processors/resource/*.class.php. Those files are gone. Create/update processors are \MODX\Revolution\Processors\Resource\Create and Update. getInstance() still looks for {class_key}CreateProcessor / UpdateProcessor. Old modResource*Processor names are aliases until 3.3.

Mark-H asked for a notable manager UI page and marked it lower priority than features. This adds that page and links it from the upgrade index. Tooltips, profile/resource forms, uberbar trim, System Info success notice, and normalize.css are listed there. Login, installer, and language stay on their existing pages.

English and Russian. Dutch upgrade pages get the 2.6+ floor (NL has no separate CRC/UI tree).

Checked against revolution origin/3.x.

Overlap: #601 also edits upgrading-to-3.0/index.md. #616 already has a shorter manager-ui page plus CRC processor notes. Rebase whichever merges second.

Affected versions

3.x

Relevant issues

Refs #121

…cessors

Setup refuses upgrades below 2.6.0. The upgrade index still read as any 2.x and only recommended 2.8. CRC extras still copied 2.x Resource processor paths.

Refs modxorg#121
@Ibochkarev
Ibochkarev requested a review from Mark-H August 19, 2026 04:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant