Installing WordPress via Softaculous
The easiest way to install WordPress is through Softaculous, available in cPanel on all ZevsHost plans. It picks the PHP version, creates the database, and writes the configuration itself — doing the same thing by hand through File Manager and phpMyAdmin takes longer and is easier to get wrong, especially on a first install before you know your way around the WordPress file layout.
Step-by-Step Guide
- Log in to your hosting cPanel
- Under Softaculous Apps Installer, click the WordPress icon
- Click Install Now
- Enter the domain and installation directory
- Fill in admin credentials: username, password, email
- Select the interface language
- Click Install
Installation takes about 60 seconds. You'll receive links to your site and admin panel at the email address entered in the form, along with an entry under Softaculous → Installations that you can later use to update or remove the site.
Real Errors During Installation and First Launch
If the site shows a blank page after installation, error_log usually contains an entry like:
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted
in /home/user/public_html/wp-includes/plugin.php on line 205
That is the default PHP memory limit (128 MB), which is not enough for a heavy theme or conflicting plugins, especially when a page builder and a caching plugin are both active at once. Raise memory_limit to 256M through MultiPHP INI Editor. The second common problem happens when a Softaculous-installed site is moved to another domain:
Error establishing a database connection
It means the settings in wp-config.php (database name, user, password, or host) no longer match the real MySQL credentials — Softaculous writes them automatically, so this error almost never happens on a fresh install but is typical after manually cloning a site.
Softaculous vs Manual Installation
| Method | Time | Control over settings | Risk of error |
|---|---|---|---|
| Softaculous | ~1 minute | Basic (domain, language, admin) | Low |
| Manual install via File Manager + phpMyAdmin | 10–20 minutes | Full | Medium |
| WP-CLI over SSH | ~2 minutes | Full, scriptable | Low with experience |
When Softaculous Is Not the Right Fit
- You need a WordPress Multisite network of sites on subdomains or separate domains — Softaculous only deploys a single site
- You need an exact WordPress version different from the one Softaculous offers by default, or a staging copy with a configuration identical to production
- The site is deployed through CI/CD or automation scripts — WP-CLI fits better here than a one-off install through the web interface
- You need non-standard database table prefixes or a custom directory structure that Softaculous does not let you set during installation
- You are migrating an already-built site from another host — in that case Softaculous is not needed at all; the files and database are transferred directly
Installing via WP-CLI (an SSH Alternative)
If you need automation or an install without a web interface, WordPress can be deployed with three commands over SSH:
wp core download --path=/home/user/public_html
wp config create --dbname=DBNAME --dbuser=DBUSER --dbpass=DBPASS
wp core install --url=yourdomain.com --title="My Site" --admin_user=admin --admin_password=PASSWORD --admin_email=you@yourdomain.com
This approach is convenient when moving a configuration between environments or deploying from a CI/CD script, where every step needs to be predictable instead of a series of clicks in an interface.
Configuring PHP for WordPress
- WordPress 6.x officially supports PHP from 7.4, but the recommended version for new sites is PHP 8.2 — see the article on changing the PHP version in cPanel
- To upload large media files to the library, raise upload_max_filesize and post_max_size through MultiPHP INI Editor — the default 2 MB is too small for modern images
After Installation
- Log in to /wp-admin and change the theme
- Install a security plugin (Wordfence) — see the detailed protection checklist in the article on diagnosing the white screen and 500 error
- Configure permalinks (Settings → Permalinks)
Verifying the Result
- Open the site's homepage in an incognito browser window — it should load with no PHP errors and no installation notice
- Log in to /wp-admin and confirm the admin login works
- Check Settings → General — the site address should use https:// if SSL is already enabled
Speeding up a fresh install with caching and image optimization is covered in the article WordPress speed: 10 ways to make your site faster.
Frequently asked questions
Can WordPress be installed on a subdomain instead of the main domain through Softaculous?
Yes, at the step where the domain and directory are chosen, simply pick the subdomain from the dropdown list instead of the main domain — Softaculous deploys WordPress right there, creating a separate database and configuration for that install. The rest of the installation wizard stays the same.
Do the site files and database get removed if the install is deleted through the Installations section in Softaculous?
Yes, removing an install through the Installations section deletes both the site files and its linked database entirely, not just the install record. Simply deleting the site's folder through File Manager without using that section can leave the database untouched, and it keeps taking up space on the server.
Does a database need to be created manually before installing through Softaculous?
No, Softaculous creates the database and its user itself during installation — there's no need to go into phpMyAdmin and set one up beforehand. It writes all the connection details into the configuration file automatically, which is exactly what makes this method faster than a manual install.
Can the PHP version be changed for a site after WordPress is already installed?
Yes, the PHP version for a site can be changed at any point after installation through MultiPHP Manager in cPanel, with no need to reinstall WordPress and no data loss. It's worth checking that the active theme and plugins are compatible with the new version before switching, to avoid errors afterward.