Softaculous Beyond WordPress: Joomla, Magento & PrestaShop
Most people only ever click the WordPress icon in Softaculous and never scroll past it. But the same installer ships Joomla, Magento, PrestaShop, and close to a hundred other apps - and each one has its own quirks that catch people off guard the first time. Here's what actually happens when you install the other three, and the fixes for the errors that show up right after.
Where Softaculous Lives and What It Actually Does
In cPanel, go to Software > Softaculous Apps Installer, or use the search box and type the app name directly - it's faster than browsing categories. Softaculous downloads the app, creates the MySQL database, writes the config file, and sets file ownership for you. What it does not do well is warn you about an app's real server requirements before you commit - that part's on you, and it's where most first installs go sideways.
Installing Joomla
Joomla is the closest to a WordPress-style install - pick a domain, set an admin user, choose a sample data set (Blog, Brochure, or none), and click Install. It usually finishes in under two minutes on shared hosting.
What breaks right after
- Blank front page, admin still works. Almost always a PHP version mismatch. Joomla 4.x needs PHP 7.4+ (5.x prefers 8.1+). Check Software > MultiPHP Manager and match the version Softaculous listed at install time.
- Pretty URLs (SEF) give a 404. Joomla writes its own
.htaccesstemplate but ships it disabled by default. In Global Configuration > SEO Settings, turn on "Search Engine Friendly URLs" and "Use URL Rewriting" - then confirmhtaccess.txtin the site root was actually renamed to.htaccess(Softaculous does this, but File Manager sometimes hides dotfiles, so toggle "Show Hidden Files" to check). - 500 error after installing a template or extension. Usually a PHP memory limit hit mid-install. Bump it in MultiPHP INI Editor to at least 256M before installing anything extension-heavy.
Installing Magento (Open Source)
Magento is where people get burned, because Softaculous will happily let you click Install on a stack it can't actually support. Before you start, know this: Magento 2.4+ requires Elasticsearch or OpenSearch for catalog search, plus a minimum of 2GB RAM and Composer access at the command line. Shared cPanel hosting almost never has Elasticsearch installed, and Magento's install will either fail outright or finish with a broken search/catalog page. If you're serious about a Magento store, this is a VPS job, not a shared-hosting one.
If your environment does meet requirements
- Confirm PHP is 8.1 or 8.2 (check Magento's current compatibility matrix - it changes with each release) in MultiPHP Manager first.
- In Softaculous, set the admin path to something other than
/admin- Magento's default admin URL is a common brute-force target. - After install, run the reindex and cache flush from cPanel Terminal or SSH:
bin/magento indexer:reindexandbin/magento cache:flush. Softaculous won't do this for you, and skipping it is the #1 reason a fresh Magento store shows old or missing product data.
Common post-install issues
- White screen after login. Almost always a permissions problem on
var/,generated/, orpub/static/. Set those to 755 (files 644) via File Manager orchmod -Rover SSH, then re-runsetup:upgrade. - Cron never runs, orders don't process emails. Magento needs three cron jobs (default, indexer, consumers) added manually in cPanel > Cron Jobs - Softaculous doesn't create them. Point them at
bin/magento cron:run.
Installing PrestaShop
PrestaShop's Softaculous install is close to Joomla's in effort, but it has one step people miss constantly.
Step-by-step
- Pick your domain/subdirectory, set store name, admin email, and default language/currency.
- Let Softaculous finish - it typically takes 3-5 minutes since PrestaShop ships more sample assets than Joomla.
- Delete the
/installfolder immediately after setup. PrestaShop leaves this folder live until you remove it, and anyone who finds it can re-run your store's installer and wipe the database. Softaculous sometimes handles this automatically depending on version - always verify it's gone in File Manager before you consider the install "done."
Common issues
- "Invalid security token" on login. Usually a cookie/session mismatch after moving the store to a different domain than it was installed on - clear the
var/cachefolder and re-check the shop URL under Preferences > SEO & URLs. - Product images 404 despite uploading fine. PrestaShop needs
mod_rewriteactive for its friendly-URL image paths. Confirm Apache has it enabled (it is by default on Getwebup, but check with your host if migrating in from elsewhere) and that.htaccessin the store root wasn't stripped during a manual file transfer. - Admin folder guessable. PrestaShop randomizes the admin folder name at install (e.g.
admin739fk2) - don't rename it back to/adminfor "convenience." That randomization is a real security layer.
Requirements at a Glance
| App | Min PHP | Extra requirement Softaculous won't set up | Best suited for |
|---|---|---|---|
| Joomla | 7.4+ (8.1+ for v5) | None major - works fine on shared hosting | Brochure sites, blogs, small CMS needs |
| Magento OS | 8.1/8.2 | Elasticsearch/OpenSearch, 2GB+ RAM, cron jobs | VPS-hosted stores only |
| PrestaShop | 7.4+ | mod_rewrite, manual install-folder deletion | Small-to-mid stores on shared or VPS hosting |
Gotchas That Apply to All Three
- PHP version drift over time. Softaculous doesn't auto-update your PHP version when the app needs a newer one - check MultiPHP Manager after every major app upgrade.
- Shared database prefixes. If you install more than one app into the same MySQL database (not recommended, but Softaculous allows it), mismatched or duplicate table prefixes will silently corrupt one of the installs. Give each app its own database.
- Auto-upgrade toggle. Softaculous can auto-update installed apps in the background. That's convenient for WordPress, risky for Magento and PrestaShop where a minor version bump can break custom themes or payment modules without warning. Turn it off for storefronts and update manually after testing on staging.
Prevention Checklist
- Check the app's real PHP and RAM requirements before installing, not after.
- Set the correct PHP version in MultiPHP Manager before you click Install, not after.
- Delete leftover installer folders (PrestaShop's
/install, and similar for other apps) the same day you finish setup. - Give every app its own database - never share one across installs.
- Turn off Softaculous auto-upgrade for storefronts; keep it on for low-risk brochure sites if you want.
Frequently asked questions
Can I run Magento on shared cPanel hosting?
Technically Softaculous will install it, but Magento 2.4+ needs Elasticsearch/OpenSearch for search and catalog pages, which shared hosting doesn't provide. You'll get a broken storefront. Use a VPS with at least 2GB RAM for a real Magento store.
Why does my new Joomla site show a blank homepage?
It's almost always a PHP version mismatch - Joomla 4.x needs PHP 7.4 or higher, and 5.x needs 8.1+. Check the version in MultiPHP Manager and match it to what Softaculous specified during install.
Do I need to delete anything after a PrestaShop install?
Yes - the /install folder must be removed right after setup. Leaving it live lets anyone re-run your store's installer and potentially wipe your database.
Can I install two apps into the same MySQL database?
Softaculous allows it, but don't. Mismatched table prefixes between two apps sharing one database will eventually corrupt one of the installs. Give each app its own database.
Should I leave Softaculous auto-upgrade turned on?
For a brochure site or blog, it's usually fine. For Magento or PrestaShop stores with custom themes or payment modules, turn it off and update manually after testing on a staging copy first.