Installing Concrete CMS and checking the first setup

Check the selected release, PHP requirements and compatibility of marketplace add-ons and themes. Plan editor roles and the content approval process before opening access to a team.

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 Concrete 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. 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 test page and add the intended content blocks. Configure user permissions and publishing behavior, then review cache and scheduled tasks recommended for the selected version.

Create a temporary page titled Service information and add a text block, image and the form you intend to use. Work as a limited editor after initial configuration so administrator permissions do not mask a restriction.

1. Save an unpublished change and check the guest view follows the intended publishing policy.
2. Complete the authorised publication or approval step for the selected configuration.
3. Open the public page in a fresh browser session and verify the approved text and image.
4. Submit a harmless form message and confirm receipt at the monitored destination.

If the editor sees new text while the guest sees old text, inspect page version, publication state and the relevant cache. Do not replace the database because one cached page is stale. Remove temporary data after the complete workflow succeeds.

View the page as a visitor and as a limited editor. Test a form, file upload and a cache purge after editing so that changes appear correctly.

If a page edit is visible only to administrators, inspect draft/publication state, permissions and cache before reinstalling. Back up uploaded files and application data before upgrading an add-on.

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

• Softaculous installation workflow
• Softaculous cms catalogue