Installing Quick.CMS and checking the first setup

Check the edition and supported release you intend to use. Confirm any commercial add-on rights and the PHP requirements before publishing a site from an installer package.

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 Quick.CMS 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. Check how your selected edition stores content and configuration, then review the corresponding backup and update choices. Do not assume a database-only backup covers the site.
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 website identity and administrator credentials, create the page structure and review media permissions. Use the application's current supported process to change templates and navigation.

Test a page, menu link, image and any enabled contact form. Check the result as a visitor and confirm editing controls require authentication.

Keep content and configuration files in the backup scope appropriate for the selected edition. A hosting database backup may not contain all data for a file-based application.

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 Concrete CMS and checking the first setup

• Softaculous installation workflow
• Softaculous cms catalogue