Texo Command is a console for the WordPress Max sites on your Texo hosting. What makes it different is Safe Update, Safe PHP Upgrade, and the Troubleshooter. You can also clone a site, change the copy, and put those changes back onto the original when you are happy with them.
Safe Update applies plugin, theme, and WordPress updates with a backup and a health check after each step.
Safe PHP Upgrade scans first, then moves PHP only when the site can take it, and flips back if it cannot.
The Troubleshooter finds why a site is down or why you cannot log in, and offers the next fix. Enrolled Sites is where those three tools live, one card per site.
Beta
Command is in beta. It is only available to a small group of Texo clients at this stage. Things will change as we learn from real sites.
We look forward to your feedback, suggestions, and anything that feels unclear. In Texo Command, click the salmon Feedback button, to the left of Exit Command. Choose something that broke, something you wish Command could do, or something that was confusing. That opens a Technical Support ticket from your account.
Open Command
- Log in to the Texo client area
- Open My Services
- If Command is not active yet, click Activate Texo Command
- Click Texo Command
There is no separate Command password. You enter from the client area, the same way you open cPanel.
You need at least two Active WordPress Max services, or one Active Reseller service. Command then adds the WordPress sites on those services, including accounts inside a Reseller.
Command shows Importing your websites until every new site has been added and scanned. The page refreshes on its own. Site buttons stay off until that finishes. Wait until the versions appear before you run Safe Update or Safe PHP Upgrade. A WordPress install in a folder under the account is included.
Exit Command in the header leaves the console and returns you to the client area. It does not log you out of the client area.
Clone a site
Cloning is the easy way to try a change. Command makes a full copy of a WordPress site. You change the copy. The original stays as it is, and that is still the site your visitors see. When the copy looks right, Put back brings those changes onto the original.
If you do not see Clone in the section menu, open Settings and turn Clone on.
Make the copy
- Open Clone
- Under cloning from, pick the WordPress site
- Pick where the copy goes. In a folder of the same site is the usual choice
- Type a short name, such as staging. The salmon address under to: updates as you type
- Read that address, then click Clone the site
Clone the site starts the copy. There is no second question. The salmon address is the copy you are making, so read it first.
Three places the copy can go:
- In a folder of the same site — for example
texotest.co.za/staging. The copy lives inside the site - On a subdomain of the same site — for example
staging.texotest.co.za. The copy sits outside the live folder. If the domain's nameservers are somewhere else, the subdomain opens from the public internet only after that DNS record points here - Onto another account — an account you already have in Command. Pick the account, then a folder, a subdomain, or that account's main address
At that account's main address replaces the site already at that address. Command says the existing site will be overwritten, and that its current files are saved first. The site you clone from stays as it is. Use a folder when you only want a place to try the changes.
The copy has its own database and its own configuration. The original database is left as it is. Mailboxes are not copied.
The copy does not send mail. Scheduled tasks on the copy do not run. Payment plugins stay off, so a test checkout cannot charge anyone. The shop itself stays.
A folder or subdomain on the same hosting account uses that account's PHP. A PHP change on one site on that account changes the other.
One copy runs at a time. A bar shows the progress. To stop it, tick Stop this clone and remove anything it has already made, then click Abort. Anything the copy has already made is removed. The original is not changed.
You can clone a WordPress site on your own account. You cannot clone another client's site.
Change the copy
When the copy is ready, it is listed under Existing clones of that site. Open it with View Website. Sign in with Login to WP. Change pages, plugins, or the design there.
Work only on the copy. The original stays as it is until you put the copy back.
Put the changes back
When the copy looks right, click Put back on that clone.
Command asks Put this clone back? The question names the copy and the original it goes back onto. The button is Put back.
Put back replaces the original with the whole copy, including the changes you made on the copy. The files that were on the original are saved first. Visitors then see what you built on the copy. Mail and scheduled tasks on the original stay available.
The copy itself stays until you click Delete. Delete asks Delete this clone? and then removes that copy and the database made for it. It does not remove the original. A copy that replaced another site's main address is that site. Delete is for a folder or a subdomain copy, not for that site.
If you keep changing the copy, Put back again replaces the original with that newer copy.
While Put back is running, the bar says Putting the clone back. To stop it, tick Stop putting the clone back. Anything not yet published will be removed. Then click Abort. If the original has already been replaced, Abort leaves the site as it is.
The site list
Enrolled Sites is the home list. Each row is one WordPress site Command found.
Refresh checks for new services in the client area, then new accounts inside a Reseller account. Each click reads those again. The button waits while a scan is already running.
Sites that do not use WordPress are listed under Sites that do not use WordPress. Each one is a card, like a WordPress site. Open it for a screenshot of the public address, where the site is hosted, where its email is hosted, and which nameservers it uses. Command may say the site is hosted at Texo, at Wix, at Shopify, at another named host, or not hosted at Texo. A site behind Cloudflare says so. View Website and cPanel are on the row. Command does not offer Safe Update or Login to WP on these sites. If there is nothing public to show, there is no screenshot.
To take a WordPress site off the list, open it and choose Remove from Command. Command asks you to confirm, and it names the domain. The site stays off when Command looks again. If you have removed any, a card at the bottom is titled Sites removed from Command. The line under it is These stay off until you add them back. Add to Command puts that site back on the list. WordPress content is not deleted. The card is hidden when nothing has been removed.
- Domain — the site. Click the row (or the chevron) to expand it
- WP — WordPress version
- PHP — PHP version. A mustard warning triangle means the version is aging or at end of life
- Plugins — how many plugins Command found
- Updates — how many updates are waiting. Use the All / Updates pills to hide sites that are already current
On the right of each row:
- View Website — opens the public site
- cPanel — opens that service in the client area so you can log in to cPanel
- Login to WP — a one-time sign-in as the first WordPress administrator. No password to remember
If you just added sites, a banner may say they are still initialising (finding the server path and scanning plugins). The page refreshes on its own. Wait until the versions and update counts appear before you run Safe Update or Safe PHP Upgrade.
Open a site
Expand a row to see the screenshot, hosting details, PHP, and the plugin table. The screenshot opens the site in a new tab.
The plugin table is WordPress, Theme and Plugins. WordPress is the first row, the active theme is next, then plugins. A WordPress logo means the package comes from wordpress.org. A $ means premium or custom. Command cannot always install that update itself.
On the card you can add notes, refresh the scan, refresh the screenshot, and assign a client. Remove from Command is there too.
Use All to see inactive plugins (and Activate / Delete all inactive when those apply). Use Updates to see only what still needs an update.
The next step
Command highlights one next click on the card. That button is salmon and pulses. Follow it. Do not hunt for a second salmon button — only one pulses at a time.
- PHP is aging or at end of life, and Command has not scanned yet. The pulse is Safe PHP Upgrade. That opens the version choice. It does not change PHP
- Scan says update first → pulse is Safe Update
- Scan says PHP can move → pulse is Upgrade now
- A premium or layout plugin must be updated in WordPress → pulse is Update them in WordPress
Paths to a fully updated site
There is no single button that always means "update everything." Command chooses a path from what is installed, what updates exist, and which PHP those updates need.
1. Safe Update (plugins, theme, then WordPress)
When updates can install on the current PHP, the next step is Safe Update.
Safe Update:
- Takes a database dump first
- Updates plugins one at a time (snapshot of that plugin's files, then the update, then a health check)
- Updates the active theme after plugins, unless you turn that off in Settings
- Updates WordPress core last, and only if the current PHP can run the new WordPress. You can turn this off in Settings
Health checks always include the homepage and wp-login. If WooCommerce is active, Command also checks the shop, a product, and a category.
If a plugin update knocks the site down, Command puts that plugin's files back. If the site comes back, it skips that plugin and continues.
If the site is still down and WordPress has not been updated yet, Command restores the database and the file snapshots, skips that plugin, and continues.
If the WordPress update itself breaks the site, Command restores the backup from just before that update. That is the WordPress files and the database. Plugin updates that already succeeded stay in place. Report issue to Texo Support sends Texo the log so we can investigate.
If a later plugin update leaves the site down after WordPress has already moved, Command puts that plugin's files back. It does not roll WordPress back. The backup stays on the account, and Report issue to Texo Support sends the log.
After a successful run, Command deletes that database backup from the hosting account. A run that cannot finish keeps the backup.
2. Safe PHP Upgrade first
If PHP is old (a warning triangle on the list, or Current next to Recommended on the card), the salmon button is Safe PHP Upgrade.
Click Safe PHP Upgrade to choose a version. That click does not change PHP. Choosing 8.3, 8.4, or 8.5 starts a scan of the plugins, the theme, and whether WordPress will boot on that PHP. A progress bar runs under the PHP row.
Only Upgrade now changes PHP. It changes PHP for the whole hosting account. Texo keeps one WordPress site on each account. Command asks before it switches. If the site fails the health check, PHP is switched back.
3. Run Safe Update first, then PHP
Sometimes the scan finds updates that should go on before PHP changes. The message is:
Run Safe Update first. Then I can switch PHP.
The pulsing button is Safe Update. After that run, Command looks again. The next pulse may be Upgrade now — or a WordPress login if something still cannot be installed from Command.
4. Bridge (turn a few plugins off, flip PHP, update, turn some back on)
A bridge is for plugins that cannot run on the new PHP and also cannot update on the current PHP. Command may deactivate those plugins, flip PHP, try their updates, and turn back on only the ones that actually updated and still run.
If an update does not install, that plugin stays off. You will find it on the All list as inactive — not on Updates.
Command will not auto-bridge WooCommerce or payments, security plugins, drop-ins, or page builders / sliders / theme engines (Elementor, WPBakery, Slider Revolution, Divi, and similar). Turning those off would break the shop or the look of the site.
Blockers
These stop Command from finishing the job on its own. The card will say so in plain language.
- After WordPress X — that plugin's update needs a newer WordPress first. Safe Update takes WordPress last when it can. Some rows stay parked until core moves
- After PHP X — that update needs a newer PHP. Safe Update will not install it on the current PHP. That is a PHP-first or bridge problem, not a failed Safe Update
- Premium / no key ($) — Command cannot fetch the zip from wordpress.org. After Safe Update, leftover layout or premium plugins become Update these blocking plugins in WordPress. The button Update them in WordPress opens a one-time login on WordPress's own update screen so you can use your licence
- Theme deadlock — the active theme will not run on the new PHP and there is no safe update. Command will not flip PHP and will not switch you to a default theme as if that were a real fix
- Won't run on PHP X — that plugin dies on the target PHP. Command names the plugin. Do not expect an Activate button next to that line
If Command cannot finish a Safe Update or Safe PHP Upgrade, click Report issue to Texo Support. You see the message before it is sent. Command opens a Technical Support ticket from your account. The ticket describes the problem and includes the run log and recent Command activity. You can reply to that ticket in the client area.
I can't log into WordPress
Open Troubleshooter, pick the site, then the first pill.
- Create a one-time login link — signs you in as the first administrator, same idea as Login to WP on the site list
- Reset the password — sets a new password for that first administrator and shows it once
Use this when you forgot the password or you are locked out. It does not change the public site.
The site shows an error
Use this when the homepage or wp-login is broken: a blank page, a critical error, a redirect loop, or a database error. You do not pick the cause. Command looks.
It checks the homepage and wp-login (and takes screenshots of both), reads the PHP log, and then names what it found. Typical fixes it can offer:
- A broken line in
wp-config.php(including a missing quote on adefine) - Leftover Wordfence
auto_prepend_filepointing at a missing file - A failing
object-cache.phpdrop-in - Memory limit too low for the package
- A plugin or theme fatal — it will name the plugin when this visit failed and a new fatal is in the log
Command will not turn off WooCommerce, payments, or security plugins by itself. It will not flip PHP down from Troubleshooter. If the real fix is "update this theme or plugin," it will say that rather than switch you to a default theme and call the site fixed.
If a fix is applied and the site still errors, Troubleshooter looks for the next problem instead of stopping at "still needs attention."
When it cannot finish, click Report issue to Texo Support. You see the message before it is sent. Command opens a Technical Support ticket from your account, with what it found and the error it read.
Links are not working
Use this when the site loads but permalinks, inner pages, or pretty URLs fail — not when the whole site is a PHP error. If the homepage itself is down, use The site shows an error instead.
Command checks for a missing or broken .htaccess and stale permalinks. The fix is to create or repair .htaccess and flush WordPress rewrite rules.
Settings
Settings is the third tab. Enrolled Sites and Troubleshooter are the daily work. Settings is where you choose the mailbox and what Safe Update is allowed to touch.
- Send from is the mailbox Command uses when it emails on your behalf. It must be an email account on your Texo hosting. Test sending sends a test to that same address
- Safe Update has two ticks, both on unless you turn them off: Update the active theme, and Update WordPress core
- Tabs: Enrolled Sites, Troubleshooter, and Settings stay on. Turn Clone on to copy a site, change the copy, and put it back. Turn Clients on if you assign a person to a site. Invoicing, Products/Services, and Templates are still being built. Turn a tab off if you do not use it
- Update report is on this page. Command does not email that report yet
- Deactivate is on the far right of the section menu, above Enrolled Sites, and again under Settings. Command asks you to confirm. It erases what Command stored: enrolled sites, sites that do not use WordPress, clients added here, screenshots, Safe Update and Safe PHP history, scan history, and sign-in links. Your websites and hosting are not deleted. You return to My Services and can turn Command on again from there
Feedback
This is a first user guide for a product that is still in beta. If a path on your site did not match this page, if a button was confusing, or if you have a better way to explain it, click the salmon Feedback button, to the left of Exit Command. Choose Something broke, I wish Command could..., or This was confusing, and say what happened. Command opens a Technical Support ticket from your account and includes the site you have open. You can reply to that ticket in the client area.
We look forward to hearing from you.