A team quotation should cover the branch, not just its first page.
Use an explicit before-and-after map to make the delivery decision concrete.
Include descendants in the work request
Resource 21 has one child, resource 22. Moving 21 changes both paths in this exercise. A quote based only on the selected parent misses the child link that visitors and internal navigation may still use. List the affected IDs and old paths together.
Resolve collisions before the move is accepted
Support already contains resource 31 at /support/specs. Moving resource 21 there with the alias specs would produce the same destination. The preview identifies the conflicting resource and refuses the move. Changing the alias to technical makes the two destination paths distinct.
Make URL continuity part of acceptance
The successful MD84 move retains a pair of old-to-new redirect rules with its receipt. Ask the commissioned team to implement the agreed redirect behavior, update the relevant links and verify the receiving URLs on the deployed site. Include cache refresh and reversal responsibilities in the release plan.
Two resources move. Two URLs need a receiving plan.
MD84 contains six resources. Move resource 21 and its child 22 beneath Support. The alias specs collides with resource 31; technical produces two distinct destination paths. Inspect the changes, then retain the approved move and its two redirect rules.
Agree the URL result before commissioning the implementation.
Operate the resource exercise, keep its acceptance cases and use the MODX references to establish your installed site’s behavior.
Try the resource move and its refusal cases
Use the six-record workspace to reproduce a duplicate destination, a descendant cycle and a valid two-resource move. Change inputs after preview to see why the approval must follow the current plan.
Open the resource move demoCheck aliases against the installed URL settings
MODX resource fields include parent, alias, URI and URI override. Friendly URL and alias-path settings affect the resulting address. Bring these settings, content-type suffixes and any frozen URIs into the assessment.
MODX primary reference: resource fieldsDiscuss child URI refresh with the developer
The MODX save reference describes recalculating affected resource URIs and refreshing child URIs. Use it to identify the implementation and release checks needed for the installed version and its customizations.
MODX primary reference: saving resourcesScope an adjacent application action separately
If a separate business application sends work to the website team, describe its selected record IDs and capacity rules independently from the CMS resource move. An explicit interface boundary keeps the two development requests quotable.
Discuss a CodeIgniter application changeCommission a team against the entire resource change
Set the project boundary around the affected records, receiving URLs and people authorized to release the work.
Identify the MODX installation and the delivery owner
Share the MODX edition and version, PHP environment, installed extras, templates and source arrangements. Identify the site owner, developer contact and release approver. Provide an authorized development copy and explain which manager action or visitor journey the engagement must change.
Set the team engagement and its first acceptance result
Describe the resources, templates, snippets or integrations included in the request. Agree who will implement and review the work, the planned allocation, review checkpoints and quotation. Supply one representative change with records and expected outputs rather than leaving its completion open to interpretation.
Map the selected branch and the existing destinations
MD84 begins at revision 4 with six resources. Products is 20; its Specs branch is 21 with child Install 22. Support is 30 and already has Specs 31. Moving 21 beneath 30 affects two resources. The preview must examine the target paths against all six current records.
Challenge the parent and alias before approval
Keep specs as the alias to expose the collision with resource 31. Try child 22 as the destination parent to expose a cycle. Then choose Support 30 and alias technical: 21 becomes /support/technical and 22 becomes /support/technical/install. The other four resource paths stay unchanged.
Approve a current move and retain its URL map
The Publisher reviews the prepared revision and acknowledges the two redirect rules before applying the move. Observer may inspect it. Editing the alias or parent clears preparation. A simulated external edit advances the site revision and requires another preview. Receipt MD84-M1 retains both moved IDs and both old-to-new paths.
Receive the implementation and verify the release
Accept the commissioned work in the actual MODX installation with its permissions, context settings and routing. Receive the source revision, configuration changes and verified URL map. Agree the release window, backup and reversal steps, monitoring checks, defect support and responsibility for subsequent changes.
Give the development team a site baseline it can assess
- List resource contexts, URL settings, content types, templates, chunks, snippets and extras affected by the change. Include a small sanitized tree and the current paths. Identify frozen URIs and external links that require special handling.
- Specify access to the development environment and source repository through your authorized process. Include manager permissions and any integration contracts. Agree review and deployment access with the people responsible for the site.
- For ongoing work, define the team allocation, backlog owner, priority changes and acceptance cadence in the quotation. For a contained change, define its records, deliverables and release boundary. Any additional work needs an agreed scope adjustment.
Include routing, migration and support in the delivery boundary
- MD84 uses a single context, slash-separated aliases and no content-type suffix. Its Publisher role, revision guard and retained redirect receipt are requirements to discuss for the commissioned workflow. Assess the actual site’s URL generation and authorization rules before implementing them.
- Quote redirect handling explicitly, including the response code, old URL coverage, query-string behavior, link updates and any existing redirect chains. Check the selected resource and its descendants after cache refresh, with the required permissions enforced on the server.
- If the work includes a version upgrade, hosting move or content migration, inventory extras and environment compatibility separately. Agree a protected backup, trial migration and release reversal criteria. Document source ownership, required licences, hosting responsibility and the support period in the engagement.
Six records that make a resource move an assessable project
Use IDs and complete paths to specify the change your development team must deliver.
| Record | Example inputs | Required output and control |
|---|---|---|
| Installation baseline | MODX version; context web; URL, suffix and URI-override settings | Assess the receiving installation and the resources whose addresses may change. |
| Resource tree | 10 Home; 20 Products; 21 Specs; 22 Install; 30 Support; 31 Support Specs | Keep stable identities and parent links; resource 22 is a child of 21. |
| Move request | Resource 21; destination parent 30; requested alias technical | Reject a descendant as parent and require an acceptable alias. |
| Destination check | /support/specs is already occupied by 31 | Refuse the specs collision; inspect both paths produced by the valid technical alias. |
| Current approval | Revision 4; Publisher; preview and acknowledgement | Rebuild the plan after input changes or a later site revision before applying it. |
| Move receipt | MD84-M1; IDs 21/22; two redirect rules; revision 4 to 5 | Retain the accepted old/new paths; repeated application requires a new valid plan. |
At revision 4, move resource 21 from Products 20 to Support 30. Alias specs conflicts with existing resource 31 and must stop. Change it to technical. The valid map is /products/specs → /support/technical and /products/specs/install → /support/technical/install. Preview, acknowledge and apply as Publisher. MD84-M1 records two moved IDs and two redirect rules at revision 5; the remaining four resource paths are unchanged.
Ask providers to quote the same resource change.
Use their stated services to discuss staffing and delivery, then require the same receiving evidence for your project.
| Option | Published focus | Ask in your demo |
|---|---|---|
| Artjoker | Describes MODX website development, project stages and a meeting for project enquiries. | Will the scope include descendant URLs, redirect checks and the business release approver? |
| The Marat Company | Offers MODX developers, modules, templates and extras through a quotation process. | How will the team demonstrate collision refusal, the final path map and source handover? |
| Budget Coders | Offers MODX team enquiry, CMS customization, template work and migration services. | Which URL settings, migration responsibilities and post-release support are included? |
Send the same six-resource example, installed-version inventory and delivery boundary with each enquiry. Ask for the people and allocation assigned, the approval process and the evidence returned at handover. Confirm the quoted scope and availability directly; published provider descriptions do not settle your project terms.
Category reference: MODX primary reference: friendly URL configuration. Use these platform references to discuss the installed site. Include the exercise’s move checks and redirect handover as explicit development and acceptance requirements.
Commission software around a result your team can verify.
Explore Codeblix development services and define the records, responsibilities and release outcome your project needs.
Explore marketplace development servicesSettle the development engagement and the receiving evidence
Bring the installation details and a concrete change to the consultation.
What should we send to request a MODX development team?
Send the installed MODX release, environment, relevant extras and source access arrangements, together with the first change and its acceptance owner. Include the resources, current paths and desired result. Request a quotation covering implementation, review, source delivery, release assistance and support.
Can the engagement cover an existing website or a continuing backlog?
Bring the current site and the work you want to commission. A bounded change needs a defined result and delivery boundary; continuing work needs a named backlog owner, agreed allocation and review cadence. The assessment establishes the team arrangement, dependencies and commercial terms.
Why are two paths involved when we move one selected resource?
In MD84, Specs 21 contains Install 22. Moving that branch changes the parent path and its child path. The preview lists both resource IDs and their complete old and new addresses. This gives the developer and release approver a finite set of URLs to check.
What prevents the example from replacing an existing destination?
Support Specs 31 already occupies /support/specs. The initial move of 21 to Support with alias specs is refused. Changing the alias to technical produces distinct paths for 21 and 22. The installed implementation must check current destinations and authorization before committing the change.
Which move requires approval in the demonstration?
Observer can inspect the proposed move. Publisher must preview a valid plan and acknowledge its two redirect rules before applying it. Parent or alias edits clear the prepared plan. A simulated external edit changes the revision, so the operator must preview the current tree again.
Does the development quote include redirects and link updates?
Specify those deliverables in the request. The exercise retains two old-to-new rules with the accepted move. Agree how the team will implement the response codes, preserve the required query behavior, update relevant links and check the deployed URLs after cache refresh.
How do versions, extras and frozen URIs affect the scope?
They form part of the installation assessment. Provide existing contexts, URL settings, content-type suffixes, URI overrides and relevant extras. Quote any compatibility repair, upgrade, hosting migration or integration change explicitly, with its own checks and release responsibilities.
How are price, source delivery and support agreed?
The quotation should identify the people or allocation, included changes, review checkpoints and any required licences or hosting costs. Agree the source revision and configuration to hand over, the release approver, reversal steps and defect support period before the work begins.