b2evolution is a publishing application that can organise content into collections. This guide helps you check hosting compatibility, choose an appropriate installation method and verify the first usable site. The application, its extensions and any commercial license remain separate from the hosting account.
IN THIS ARTICLE
01 Check b2evolution and hosting requirements
Evaluate the maintained release available from the project and the build offered by the installer. A catalogue entry can lag the publisher, so verify its PHP compatibility and update path before a fresh public deployment.
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.
02 Install b2evolution in the correct location
- 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.
- 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.
- Find b2evolution 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.
- 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.
- 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.
03 Configure b2evolution for first use
Plan the collections and their URLs before adding content. Review member roles, registration and comment moderation for each public area. Configure email and any scheduled processing used by the selected release.
04 Worked example: test two publishing collections separately
Suppose you plan a public Company news collection and a restricted Partner updates collection. Record the intended URL and audience of each before importing content or enabling registrations.
| Collection | Check as a guest | Check as an authorised member |
|---|---|---|
| Company news | Published sample item, image and navigation work. | Only the intended authors can publish or change content. |
| Partner updates | Restricted content and direct item URLs are not exposed. | The approved partner role can reach the intended material. |
Verify collection-specific notifications and include both collections in the backup inventory. A successful export of Company news does not establish that restricted content, associated media or partner permissions can be recovered. Test that scope before relying on the export for a live upgrade.
Confirm the expected result
Publish a sample item in the intended collection, test navigation between collections, and check guest and member permissions. Verify media links and notification delivery.
05 Maintain and troubleshoot b2evolution
For an older installation, export or back up all collections and associated media before upgrading. Do not assume a single blog export contains every collection, user permission or extension setting.
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.
A common question
Does a successful installation mean the whole application is ready for customers?
No. Verify the public content, permissions, forms or notifications and the features you actually use. An installer success message confirms provisioning, not your complete business workflow.