Patcherly

• A plugin update ships a broken function call on your PHP version. Checkout dies on Friday night. You're debugging at 11pm while your customers panic.
• A theme update changes something subtle and now 5% of your checkout flow errors. You're chasing your developer for days. Meanwhile, you're losing orders.
• A custom integration breaks and your customers can't access their accounts. Bad reviews roll in, your reputation takes the hit.

Think of it as giving yourself the superpower to fix production bugs safely and instantly, without waiting for someone else to notice or fix it for days, while the outage is costing you customers and reputation, giving you peace of mind back.

1. Detection - Install the plugin, pair your site in 2 minutes, and Patcherly starts monitoring.
2. Analysis - When an error happens, Patcherly analyzes it with full context about your site and proposes a focused fix.
3. Patching - You review and approve. We back up your files on your server. The patch applies. Tests run. If anything's off, automatic rollback.

1. Install Patcherly from Plugins → Add New, or upload the patcherly folder to /wp-content/plugins/.
2. Activate the plugin.
3. Go to Patcherly → Home.
4. Click Connect with Patcherly and finish pairing.
5. Done - your site is monitored.

• If the site hostname changes (for example after cloning to staging), Patcherly disconnects and shows a one-time notice so you can update Sites and Connect again.
• Deactivate and uninstall remove the optional wp-config rescue logging snippet and root uploads-hardening block when present.
• Home shows the latest 3 errors above the latest 3 audit events.

• Re-Connect Account on Home clears the old connection and starts pairing in one click.
• Home pairing and status no longer depend on the Settings script loading.

• When Dry-run is on for this site, Home and Errors show a clear notice; turn Dry-run off from the Home status bar (turn it on only from Sites in your Patcherly dashboard).
• The same status bar can turn Test Mode off when the dashboard test window is open.
• Connector Status shows Dry-run as Enabled only while it is on.
• Home Overview adds Bugs Pending for open errors on this site.
• Diagnostics no longer includes Send Sample Error - open Test Mode on Sites in your dashboard to send test events safely.

• Custom error log “found / added” notice shows once per path set: Home no longer repeats it on every visit for the same log.
• Admin top bar pending-error badge uses a red circle with a clear white numeral; Errors submenu matches; shield sits closer to the Patcherly label; submenu sits flush under the bar.
• When Cloudflare blocks automatic apply, Retry Patch tolerates small indentation differences between the proposed fix and the live file (avoids “context mismatch” on theme templates).

• Applying a fix after Cloudflare blocked automatic patching no longer fails when an older cached patch is still on disk - the connector refreshes the patch before apply.

• Admin top bar shield shows a visible Patcherly label and a clearer pending-error badge.
• Errors table actions are grouped into review/apply and cleanup rows; shorter messages when Cloudflare blocks automatic patching.
• You can approve a fix from WordPress even when Auto Apply is off - use the Approve icon on the Errors page.

• Error detail shows why a path was excluded from monitoring or patching, matching the dashboard.
• While analysis is retrying, clearer hints when an automatic retry is overdue - use Retry analysis to run now if you prefer.

• Patcherly shield in the WordPress admin top bar - quick links to Home, Errors, and Settings, plus dashboard Help and Support. Shows how many errors are still pending. Hide it anytime in Settings → Advanced.
• After a plugin update, old flat storage folders under uploads are cleaned up automatically; your backups and unified storage folder are kept.
• Settings → Advanced shows how much disk space pre-apply file backups use, with an option to delete them all (rollback will no longer be possible for those fixes).
• Optional site root .htaccess hardening blocks public HTTP access to uploads/patcherly when your host allows it.

• Connector Status shows “up to date” when your installed plugin already matches the latest release (no false “update available”).
• Emergency Rescue status badge is green when Rescue is active; red only when it is off or install failed.
• Approving a fix in the dashboard while analysis is still finishing no longer leaves the site stuck waiting - the connector continues and applies.
• PHP fatal errors with a stack trace are reported as one event (fewer duplicate rows).
• Dashboard-triggered rollbacks are honored even when the main plugin recently checked the logs.

• Emergency Rescue no longer writes Permission denied warnings into PHP error logs when the must-use file cannot be updated (common on managed hosts such as WP Engine).

• Home Overview “Errors found” card links to the plugin Errors page.
• Home account bar includes a Settings button next to Connect/Disconnect.

• Custom log discovery no longer shows a false upgrade prompt on Core and Pro plans; the notice on Home appears below Overview.
• Footer Sign up and pairing prompts link to registration with attribution parameters for analytics.

• After you connect the site, Get started can install Emergency Rescue and optionally apply the wp-config debug snippet (with your consent). Pairing itself still does not change those files.
• Errors list filters now include a Show only ignored toggle (matches the Patcherly dashboard).
• Hiding an error no longer surfaces a confusing HTTP 409 in the browser console when the error was already ignored.
• Stops PHP warnings when checking whether Python or Node is available on hosts that block exec.
• After activation, the “Plugin activated.” notice includes a bold link to pair the site from the Patcherly Home screen.
• Debug-log wp-config snippet also turns off on-screen PHP errors (display_errors) so admin deprecation notices stay in debug.log only - re-apply the snippet if an older block is already present.
• When Emergency Rescue cannot overwrite its must-use file (permissions), Patcherly stops retrying on every page load so PHP error logs are not flooded.
• Tested with WordPress 7.1.

• Maintenance release aligned with current Patcherly connector package.

• First public release on WP.org