WP119

What we repair, what we don’t

Items found by the health check are scored by tier and summed, which places the case in a repair plan; the full list is below.

Automatic repairs (handled automatically when found by the health check)

FAULT	How it is repaired
WordPress core files corrupted/tamperedBasic tier	Checked against the official checksums; core files are reinstalled from the official originals.
Plugin/theme syntax error causing white screenAdvanced tier	Every file is scanned for PHP syntax errors and the broken plugin is isolated (deactivated, not deleted).
Broken themeAdvanced tier	Repair the broken fragment first, then reinstall the original from the official theme directory, and only as a last resort switch to a safe theme (the appearance may differ).
Stale cache files causing errorsBasic tier	Stuck cache files are removed.
File permission chaosBasic tier	Permissions are reset to a safe, working state.
.htaccess corruption (404/500)Basic tier	The URL rewrite rules are rebuilt.
Scheduled tasks piled up and not running (cleanup)Basic tier	Clear the backlog of overdue scheduled tasks (if your configuration disables automatic scheduling, the report notes that the backlog will build up again).
Table collation chaosBasic tier	Incompatible collations are converted; the table names go into the report.
URL settings chaos (redirect loops / all images broken)Advanced tier	The site URL settings are corrected and a site-wide search-and-replace (including serialized data) is run.
Insecure links left in content ("Not secure" warnings / broken images after moving to SSL)Advanced tier	Internal http links are replaced with https across the site.
Wrong upload path (broken media library images)Basic tier	The upload path is reset.
Database schema version behindBasic tier	The pending database schema upgrade is run.
Expired transients piling up and slowing the siteBasic tier	Expired transient data is cleared.
All inner pages 404 after migration (stale permalink rewrite table)Basic tier	The permalink rules table is rebuilt.
Bloated scheduler table slowing the whole site (duplicate/flood events; completed store jobs never purged)Basic tier	Duplicate and flooding schedules and completed shop schedules are cleared, in batches, in place on your host.
Leftover object-cache config crashing the siteBasic tier	When the cache backend is unreachable, the leftover configuration is removed.
Out-of-memory white screenBasic tier	Raise the memory limit.
White screen/500 fatal error (plugin conflicts, PHP incompatibility)Expert tier	Debug mode traces the fatal error to the plugin or theme at fault and isolates it.
Editor cannot save (REST API blocked or its response polluted)Advanced tier	The REST path is repaired and the editor is re-verified to save.

Items you confirm one by one before paying the repair fee

These items change site data directly: when the health check finds them they are included in the quote, and before paying you confirm each one by ticking it in the Repair Authorization Consent Form — payment is possible only once all are ticked.

FAULT	How it is repaired
Database bloat (revision pileup / spam comments)Advanced tier	Old post revisions (the most recent few are kept), spam comments and orphaned data are permanently deleted; the parts that touch protected tables run in place on your host.
Roles/permissions corrupted, can't enter adminAdvanced tier	Repair the serialization damage first (roles kept as they were); only if that fails, reset to the WordPress default roles (plugin-defined roles need to be re-enabled).
Locked out of login by a security pluginAdvanced tier	The security plugin that locked you out is deactivated; until you re-enable it, your site is not protected by that plugin.

Noted in the report, no extra charge

Maintenance flag left behind by an interrupted update (report only)：WordPress automatically ignores an expired maintenance flag; noted in the report.
autoload bloat (noted in report)：Noted in the report; not acted on.

Checks done on every case (no extra charge)

Whether the home page loads.
Inner page spot check: real published pages are verified one by one, and must pass again after the repair.
Layout resources: if a stylesheet cannot be loaded after the repair, the write-back is blocked.

Types that only show up after payment and are not accepted (the system refunds the health check fee in full automatically)

Physically corrupted database tables.

Declined before payment (no seat taken, no charge)

Sites that are not WordPress.
WordPress Multisite (a multisite network).
Outdated WordPress versions (cannot be rebuilt safely in the repair station).
Frameworks with a non-standard directory layout, such as Bedrock.
Sites beyond the accepted range.
Sites estimated to take too long to copy (based on measured bandwidth).
Hosts without enough free space for the pre-repair backup plus the write-back.
Site size could not be measured within the time limit.
The same site already has a case in progress.
WP admin mode: before packaging, the plugin checks whether your host can run the restore; if it cannot, it stops before packaging.
SSH private keys protected by a passphrase.

Out of scope

No virus, backdoor or malware removal: we repair faults; program files that cause the fault or are clearly abnormal may be moved out of their original location, not deleted.
Media files are left alone: images and uploads stay on your host — not copied, not repaired, not moved (program files found in the media folder are handled under the Connection and Service Scope Consent Form).
Protected tables are taken as structure only, never their contents: members, comments, orders, form submissions and the like; the scope actually accessed is stated in the Data Access Certificate.
No manual repair: no engineer logs in to your host.
Plugin functionality is not guaranteed: deactivated plugins are listed in the report, and whether to re-enable them is your decision.
No SEO, content, design, hosting migration, version upgrades or performance tuning.
We do not hold your data: the repair package, the uploaded package and the copies are deleted when the repair station is destroyed; the pre-repair backup stays on your host in your keeping.
After the case ends, this service does not connect to your host without your renewed authorization; in SSH/FTP mode the program placed on your host has an expiry and stops working once it passes, and in WP admin mode the plugin deactivates itself after you complete the restore in your admin.

Done only under conditions

Until you agree to the Terms of Service and the consent forms, we do not connect to your host or place any program on it.
The number of cases handled at the same time is limited; when full, you join the waitlist.
There is a payment deadline after the case opens and another after the quote (shown on the payment page); if missed, the case is automatically canceled or automatically closed, respectively.
SSH/FTP mode: your host must be able to run PHP and hold one agent file; if the host blocks it, you are told and we do not force our way in.
In WP admin mode, download the repaired package within the deadline stated in the delivery notice; when it passes, the package is destroyed with the repair station and cannot be regenerated.

Free assessment — start by entering your URL →

This page is subject to the Terms of Service.
Terms of Service · Contact & complaints: support@wp119.com