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 — not a plugin list you have to manage by hand.
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 felt unclear or wrong. Tell us — that is how this product gets better.
Open Command
- Log in to the Texo client area
- If you have not activated Command yet, open Services → Texo Command (or Activate Texo Command on My Services)
- On My Services, use the salmon + next to each WordPress Max site you want in Command. The chip turns green ✓ when that site is enrolled. Stay on My Services until you have added every site you want
- Click Open 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. Command is a fleet tool — it is not offered on a single site.
The site list
Enrolled Sites is the home list. Each row is one WordPress site you added.
- 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 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.
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 → pulse is Safe PHP Upgrade (that starts a scan, not a flip)
- 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
- Updates WordPress core last, and only if the current PHP can run the new WordPress
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 restores that plugin's files first. If the site comes back, it skips that plugin and continues. If the site is still down, it restores the database and the snapshots for that attempt, then skips and carries on.
After a successful run, Command deletes the SQL dump from the hosting account. A failed run keeps the dump so it can recover.
2. Safe PHP Upgrade first
If PHP is old (warning triangle on the list, or Current vs Recommended on the card), the first click is usually Safe PHP Upgrade.
That first click does not change PHP. It scans plugins, the theme, and whether WordPress will boot on the target PHP (8.3, 8.4, or 8.5). A progress bar runs under the PHP row.
Only Upgrade now flips PHP. Command then checks the site. If the site is down, it flips 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, use Report issue to Texo Support? You will see the subject and body first. In beta, tickets may still be in dry-run — we still want you to use the form so we see the report.
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, use Report issue to Texo Support?
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.
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 — please tell us. Open a support ticket and mention Texo Command.
We look forward to hearing from you.