Documentation

Connect WordPress, understand repairs, and recover safely.

Customer documentation explains connector setup, monitoring, restore points, repair stages, emergency recovery, permissions, and support escalation.

Start Free Trial View Pricing

Setup

Connector

Repair

Playbooks

Recovery

Safe Mode

Security

Controls

wpfixagent.com/documentation

Recommended setup order

Create your workspaceRegister an account, select the organization that owns the website, and confirm team roles before inviting additional operators.

Install and pairActivate the connector, generate a one-time token, complete pairing, and wait for the first signed health sync.

Validate capabilitiesConfirm monitoring, safe repairs, advanced repairs, local backup, MU rescue, and CLI rescue status from the website dashboard.

Create the first restore pointCheck disk space, queue a backup, and confirm the archive timestamp before relying on repair rollback.

Test a low-risk workflowRun a fresh scan or supported cache action, then review the command result, verification state, and activity history.

Guide 1

1. Create an account and workspace

Register, create or select an organization, confirm your role, and keep each customer fleet inside the correct tenant workspace.

Create or select the correct organization

Confirm your team role

Keep client sites in the correct workspace

Guide 2

2. Install the connector

Upload the WPFixAgent Connector ZIP through Plugins > Add New, activate it, and open the WPFixAgent connection screen in WordPress.

Upload and activate the connector ZIP

Open WPFixAgent in WordPress

Confirm the site can reach the API over HTTPS

Guide 3

3. Pair a website

Generate a one-time token from Websites > Connect Site, paste the API URL and token into WordPress, and confirm that the site reports Connected.

Generate a fresh one-time token

Paste the API URL and token

Confirm Connected and the first heartbeat

Guide 4

4. Validate the first baseline

Check connector heartbeat, WordPress and PHP versions, active theme, plugin inventory, REST health, cron state, disk capacity, and available command capabilities.

Review software and health inventory

Confirm connector capabilities

Investigate missing or stale values

Guide 5

5. Use the Issue Center

Open the website dashboard and review severity, source, evidence, fix label, backup requirement, confidence, and auto-fix eligibility for each issue.

Read severity, evidence, and source

Check backup and auto-fix status

Use Review when the issue is uncertain

Guide 6

6. Run a protected repair

Start Fix or Repair, follow analysis and restore-point stages, wait for the connector result, and do not treat the run as complete until verification passes.

Follow all five repair stages

Wait for verification

Review failure or rollback evidence

Guide 7

7. Configure emergency recovery

Confirm the MU Safe Mode loader and CLI rescue bridge are installed, then schedule the exact displayed PHP command using a real hosting cron.

Confirm MU and CLI rescue components

Add a real hosting cron

Test rescue status before an outage

php /absolute/path/to/wp-content/wpfixagent-rescue/wpfixagent-rescue.php

Guide 8

8. Review alerts and history

Use account alerts for urgent fleet signals and the site dashboard for repair runs, commands, activity, verification, rollback, and escalation evidence.

Review high alerts promptly

Keep command and repair IDs

Escalate with evidence, never emailed passwords

Guide 9

9. Respond to a security finding correctly

Quarantine for a standalone suspicious file. Core-file repair for a modified WordPress core file. Reinstall from Official Source for a plugin or theme with a tampered or injected file, even when no update is showing.

Match the finding to the correct response

Quarantine standalone files, reinstall plugin/theme files

Use core-file repair for tampered WordPress core

Guide 10

10. Keep plugins, themes, core, and the database current

Update from the Plugins & Themes tab; each update snapshots the component first and restores it automatically if the post-update check fails. Core and database upgrades require a verified full restore point from the last 24 hours.

Review available plugin, theme, core, and database updates

Confirm the automatic pre-update snapshot

Verify a full restore point before core or database upgrades

Guide 11

11. Recover a site where the connector was never installed

For a site that's already white-screened or unreachable, use Emergency Recovery with FTP/SFTP credentials -- entered once, never stored -- instead of the normal pairing flow. Professional and Agency plans.

Choose Emergency Recovery instead of pairing

Provide FTP or SFTP credentials once

Hand off to normal pairing once the site responds

Guide 12

12. Manage and restore backups

Create full, database-only, or component-scoped restore points from the Backups tab, restore from any archive, and delete obsolete ones -- retention automatically prunes to three protected local copies.

Pick full, database-only, or component-scoped backups

Restore from any retained archive

Remember retention keeps three protected local copies

Recommended setup order

Step 1

Create your workspace

Register an account, select the organization that owns the website, and confirm team roles before inviting additional operators.

Step 2

Install and pair

Activate the connector, generate a one-time token, complete pairing, and wait for the first signed health sync.

Step 3

Validate capabilities

Confirm monitoring, safe repairs, advanced repairs, local backup, MU rescue, and CLI rescue status from the website dashboard.

Step 4

Create the first restore point

Check disk space, queue a backup, and confirm the archive timestamp before relying on repair rollback.

Step 5

Test a low-risk workflow

Run a fresh scan or supported cache action, then review the command result, verification state, and activity history.

Step 6

Configure recovery and alerts

Add the hosting cron for independent rescue polling and confirm high alerts appear in both SaaS and the WordPress dashboard.

Documentation principles

Customer workflows before internal implementation

Risk and rollback stated for each action

No unsupported automatic-fix claims

Support escalation included where automation ends

FAQ

Common questions

Do I need developer knowledge?

No for pairing, monitoring, and supported repairs. Complex PHP, database, or hosting failures may still need a qualified developer or host.

Where is the emergency cron command?

WordPress administrators can find the exact command under WPFixAgent Diagnostics after pairing.

Can support request my password?

Standard support uses connector and command context. Do not send passwords, private keys, or full payment-card details by email.

Where do I see a failed repair?

Open the connected website, choose Repairs, and review the failed stage, connector result, verification status, rollback outcome, and timestamps.

What should I configure first?

Complete pairing, validate the baseline, create a restore point, confirm emergency components, and test a low-risk scan before enabling broader workflows.

When do I quarantine a file versus reinstall a plugin?

Quarantine a file that doesn't belong to any real plugin at all -- a standalone dropper. Reinstall a plugin when the suspicious or modified file is genuinely part of that plugin's own code, since quarantine would remove a file the plugin actually needs to function.

My site is completely down and I never installed the connector -- what do I do?

Use Emergency Recovery from the dashboard's website-creation flow with FTP or SFTP credentials instead of a pairing token. It locates the WordPress install and deploys a standalone rescue file without needing working wp-admin, then hands off to normal pairing once the site is back.

Can I restore just my database, or just one plugin, instead of the whole site?

Yes. Restore points can be scoped to Database Only, All Files, Changed Files, Plugins Only, Themes Only, Core Only, or Configuration Only from the Backups tab, in addition to a Full restore.

Free 14-day trial · no card required

Give every WordPress site a safer path from incident to verified recovery.

Install the connector, pair with a one-time token, and start monitoring in minutes -- upgrade whenever you're ready.

Start Free Trial