Per-Account Controls
PHP: The Version Setting That Decides Your Ticket Volume
Half your client list is on a current PHP version and you have no idea which half.
Straight answer first
PHP is the server-side language behind most of what your clients will ever host, and on a reseller platform the version is a per-account setting — which makes it the cheapest lever you have on their speed and on your own ticket volume.
Old releases are slower and unpatched at the same time. An account left on a version nobody supports is a compromise waiting for a date, and the cleanup lands on your desk rather than the client's.
The good news is that it is a dropdown, one account at a time, with a legacy site and a current one able to sit side by side under the same reseller plan.
Written by the Hosting Seller staff · Checked 4 August 2026
0
Terms we leave you to guess
100+
Entries, cross-referenced
Real
Examples from live client work
Free
No gate on any entry
Any page that differs from one visitor to the next — a login, a basket, a search result — is PHP assembling HTML on demand, usually pulling the pieces out of a database. The 8.x generation runs dramatically faster than the versions its dated reputation is built on, which means an upgrade is one of the few free performance wins in hosting.
For a reseller the interesting part is that this is per account rather than per server. You inherit client sites in whatever state their previous developer left them, and you can bring each one forward on its own timetable without forcing a platform-wide flag day on everybody at once.
A mixed client estate, and why that is fine
One client runs a six-year-old bespoke application that will break above a certain version. The next runs a current WordPress install that wants the newest one available. Both can sit under the same reseller plan because the version is chosen account by account from the panel.
That flexibility is worth saying out loud when you pitch. Agencies inheriting other people's work are used to being told a platform is 'on PHP 8' as though that were the whole answer, and per-account selection is the answer they actually need.
Running the upgrade conversation with a client
Frame it as maintenance with a date rather than as a warning. Take a copy, switch the version on a staging copy or a quiet morning, click through the parts of the site that handle money or forms, and switch back if anything objects. Fifteen minutes, and the client sees admin screens that respond faster afterwards.
When something does object, it is almost always a single ancient plugin or a bespoke module nobody has touched in years. That is a finding you can quote against, not a reason to abandon the upgrade for the whole account.
What an unpatched account costs you
Two bills, both yours. The slow one is support: a sluggish admin panel generates 'is your hosting slow?' messages that cost you an hour each to answer properly. The fast one is a compromise on an unsupported runtime, which costs you a cleanup, a restore and a conversation about whose fault it was.
Set a house standard for what a new account ships on, and audit the older accounts once a quarter. Twenty minutes with the account list open is cheaper than either bill.
Where the setting lives, and what to read next
Version selection sits in each client's own panel, alongside the extensions and per-site settings, so a technical client can manage their own without a ticket and a non-technical one can leave it to you.
Worth reading next: MySQL, WordPress, OPcache and CMS.
PHP is chosen per account from the panel, one client at a time, with no support ticket in the way.
The reseller desk's own reference, written down
We treat unexplained jargon as a margin problem rather than a style one. Each entry is written so you can forward it to a client instead of writing the answer yourself.
Every client account is copied daily, and the restore runs from your own panel rather than from our ticket queue.
- Definitions from the reseller's side of the panel
- The failure mode named, not implied
- Handover and hand-back covered in each entry
- Cross-linked, so one lookup builds a picture
Why Hosting Seller
On every plan, as standard
Costed per account
Every entry says what the term does to your resource pool and your ticket queue, not merely what the word means.
What the client actually sees
Each definition names the screen, the email or the error a customer meets, so you can answer before they open a ticket.
Written from the WHM side
Definitions from the reseller's panel rather than the end customer's: packages, limits, suspensions and handover.
Judged at forty accounts
Each term is tested against a long client list as well as a short one, because that is where reseller decisions actually bite.
Entries that point onwards
Related terms cross-link, so one lookup turns into a working grasp of the whole account stack rather than a single answer.
PHP, in one read
PHP defined, set per account and costed in tickets — enough to run the upgrade conversation without rehearsing.
First Steps
From choosing to live
- 1
Audit the account list first
Before you change anything, find out which of your accounts are on which version. The answer is usually worse than you expect and takes twenty minutes to establish.
- 2
Upgrade the quiet accounts first
Brochure sites give you the confidence and the process. Save the client with the bespoke module for the day you have a copy and an hour.
- 3
Read the neighbours
MySQL, WordPress and OPcache finish this one's picture, each a two-minute read from here.
In the Box
Packed with every plan
- Seven days' money back on reseller, thirty on hosting plans
- The renewal figure matches the figure you ordered at
- A free SSL certificate on every client site, reissued before it lapses
- Softaculous in every account you open, for one-click installs
- PHP chosen per account from the panel, one client at a time
- A 99.9% uptime target, watched by monitoring day and night
- Client accounts moved in by our staff, at no charge
- Every client account copied daily, with restores you run yourself
- NVMe SSD under the whole platform, LiteSpeed cache in front
- Step up a tier in place — the accounts you built come with you
Across the Counter
Things people ask us all the time
Can two of my clients run different PHP versions on the same reseller plan?
Yes. The version is set per account from the panel, so a legacy application and a current WordPress site sit side by side without either dictating to the other. That is the setting that lets an agency take on inherited work without first insisting every client modernises on the same day.
A client refuses to upgrade. What am I actually exposed to?
An unsupported runtime stops receiving security fixes, so the account becomes progressively easier to compromise, and the incident arrives as your emergency regardless of who chose the version. Put the recommendation in writing, record the date, keep the daily copies, and make sure your terms say who is responsible for keeping the application current.
A client's plugin broke after a version change. Whose problem is that?
Practically, yours to diagnose and theirs to fix or fund. Switch the account back to the previous version to restore service immediately, then identify the component that objected. Naming the single plugin turns an argument about hosting into a quotable piece of work on their site.
Can I set a default version for every new account I open?
Set your own house standard and apply it as part of your account-opening routine, so every client starts on a supported release rather than on whatever was default the year the package was written. Then audit the older accounts periodically, because the ones you opened first are the ones nobody has looked at since.
Read next
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and daily backups.
Domain Names
Register and transfer names for clients — year one free with annual hosting.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Sell hosting on your own terms.
You set the limits, the packages and the prices. We keep the machines running underneath, at any hour.
See WordPress Hosting plans