Confirm the current release and required PHP features before use. Plan a full-file backup because the site's content and configuration are not protected by a database-only hosting backup.

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 Pluck 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 file-backup and update choices. This file-based CMS requires its content, media and configuration files in the recovery plan; a database-only export is not sufficient.
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 administrator access and the public site URL. Create a small page structure and review the selected theme and any modules. Keep upload permissions limited to documented writable paths.

Edit and publish a page, test an image and verify the result in a signed-out browser. Check that the administrator interface is protected and not cached publicly.

If content cannot be saved, inspect ownership and the project's writable directories. Do not use a recursive world-writable permission change as a shortcut.

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

• Softaculous installation workflow
• Softaculous cms catalogue