A SiteWorx subdomain can use a custom document root and PHP version instead of its initial parent-derived settings. Prepare the new folder first because a path change does not replace a complete application migration plan.
IN THIS ARTICLE
Prepare for the change
Back up the site and database, record the existing root and PHP selection, and check whether other hostnames use the same files. Keep private application storage outside the public directory where required.
01 Change a SiteWorx subdomain’s document root
- Open Hosting Features > Domains > Subdomain and select the correct parent domain.
- Use the pencil/edit action beside the intended subdomain and record its current Document Root.
- Prepare the permitted destination directory and copy the necessary files, including hidden configuration. Update application absolute paths and related cron commands.
- Set the new Document Root. Review Use Parent PHP Version and choose an explicit supported runtime only if the application requires it. Save.
- Test HTTPS, application login, uploads and scheduled work using the subdomain hostname. Keep the old location intact until verification is complete.
Confirm the expected result
The subdomain should serve the intended new path with the correct runtime, while the parent website remains unchanged. Use a distinctive harmless asset to distinguish the new location from cached content.
If the change does not work
If the site breaks, restore the recorded path while correcting missing files, permissions or application paths. If the desired PHP version is absent, ask the provider about supported availability. Do not force an arbitrary server path outside the account’s permitted scope.
Does moving the root change the public URL?
No. It changes where the server reads the site’s files. DNS and the subdomain hostname remain separate configuration elements.