Installing MODX and checking the first setup

Choose a supported MODX release and check the Extras required by the project. Plan the document root, database and manager access before deployment.

Use the project's current supported release information and the requirements shown for the package you select. If Softaculous offers an older or unsuitable build, follow the current vendor installation process or ask us to confirm a suitable environment. Do not enable an unsupported PHP runtime simply to reproduce an old tutorial.

1. Back up any existing site at the destination. Choose an empty directory or a separate staging hostname for a new installation; never approve overwriting a working site without a migration plan.
2. Open Softaculous where your hosting service includes it. In cPanel, search for Softaculous Apps Installer. In SiteWorx, use Hosting Features > Softaculous where that integration is enabled.
3. Find MODX and review the package and requirements before selecting Install. Select the correct HTTPS domain. Leave In Directory empty only when the empty domain root is the intended destination.
4. Complete the application-specific fields and a strong administrator credential stored in a password manager. Supply a reachable administrative email where requested. Review database, backup and update choices instead of accepting unsuitable defaults.
5. Start installation once and wait for the completion result. Record the public and administration URLs. Where this application needs the publisher's own deployment process, complete that process instead of forcing an outdated installer package.

Set the site URL and review resource/template relationships. Configure friendly URLs using the project's current instructions. Install only trusted compatible Extras and limit manager permissions for editors.

Create a harmless resource titled Hosting guide, assign the intended template and publish it with the site's planned URL settings. Test as a guest and keep the resource identifier with the result.

1. Confirm the resource is published and the assigned template displays its content.
2. Open the intended friendly URL directly, then refresh it.
3. Check a different existing page so a broad routing rule has not captured unrelated requests.
4. Use a limited manager account to verify only the intended resource-editing rights.

If the resource renders through a supported direct route but its friendly URL fails, inspect the MODX URL configuration and web-server rewrite setup. If it renders without the expected body, inspect the template relationship first. Preserve current templates and configuration before changing shared presentation or routing logic.

Create and publish a resource, test its friendly URL, upload a file and check a limited manager user. Verify that private resources are not accidentally published.

A resource can exist but remain unpublished or use a template that does not display expected content. Diagnose resource state, permissions and URL rewriting before changing database records directly.

Keep files and data together in your recovery plan, test application updates in a copy when practical, and review logs after deployment. If installation fails, record the exact error, selected application/PHP versions and destination path before retrying.

• Choosing and managing applications with Softaculous
• Opening Softaculous and finding your installations in cPanel
• Changing PHP versions, extensions and application limits
• Creating Web Hosting backups and planning a restore
• Installing Microweber and checking the first setup

• Softaculous installation workflow
• Softaculous cms catalogue