Installing ProcessWire and checking the first setup

Plan the content fields, templates and modules your project requires. Check the current release requirements and decide which users should edit each part of the content tree.

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 ProcessWire 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 template and associated page content using the supported project workflow. Review template access rules, upload restrictions and mail handling. Keep custom PHP template code under version control.

A useful first ProcessWire test is a Service template with fields for a title, summary, body and image. Create two pages using that same template, then give an ordinary editor access only to the intended content branch.

1. Enter different content on each page and verify that both use the expected presentation.
2. Upload an image, check its public URL and confirm the template escapes untrusted values appropriately.
3. Try opening a protected page while signed out, including its direct URL.
4. Confirm that the editor can change content without being able to edit PHP template files or unrelated system settings.

If one page fails and the other works, compare its field values and template logic before assuming that the whole database needs repair.

Test a published page, an asset upload and a non-administrator editor. Review the public response for unintended debug output and confirm protected pages stay private.

A template can contain custom application logic, so replacing core files will not diagnose every rendering problem. Check the relevant log and recent template/module changes before attempting a database repair.

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

• Softaculous installation workflow
• Softaculous cms catalogue