Installing CMS Made Simple and checking the first setup

Check the current CMS and module requirements and record any custom templates. Plan the page hierarchy and editor responsibilities before migrating content.

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 CMS Made Simple 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.

Create a small page tree and select the intended design. Configure the site URL and mail settings used by forms. Review module permissions and install only current trusted modules.

Test navigation, a form, an uploaded file and a limited editor account. Confirm a draft or restricted page is not visible to a guest.

When a module update changes output, compare its template and PHP requirements in staging. Keep both the database and custom design files so that a rollback can recover the complete site.

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 Kirby and checking the first setup
• Installing Quick.CMS and checking the first setup

• Softaculous installation workflow
• Softaculous cms catalogue