Steve Hanlon
8de7cad0de
Plugin skeleton, drop-in step registry, option-backed session, single-page checklist UI, downloadable Markdown report. Steps live as one file each under includes/steps/ — adding/removing one is a single file change. Step IDs are stable strings so renaming files preserves session data. Architecture (hc-5ix.3): WPH_Steps singleton globs includes/steps/*.php, natsort-orders by filename, requires each file (which returns a WPH_Step instance), then applies a 'wph_steps' filter so installs can drop steps. Session (hc-5ix.4): option-backed (per decision — plugin is installed per-engagement, so DB-resident history would be lost on uninstall). Single in-progress session per site; finished sessions render a report that the user downloads/copies. Recovery bootstrap (hc-5ix.1): detects whether wp-site-recovery is installed + active, surfaces state on the start panel and in every active session. Manual install for now; private update channel deferred to hc-5ix.27. Smoke-tested on testsite: registry discovery (13 steps in correct order), start → update_step → progress count → finish → 8KB Markdown report → discard cycle.
26 lines
1.5 KiB
PHP
26 lines
1.5 KiB
PHP
<?php
|
|
if (!defined('ABSPATH')) exit;
|
|
|
|
return new class extends WPH_Step {
|
|
public function id(): string { return 'plugins'; }
|
|
public function title(): string { return 'Step 4 — Plugin Updates'; }
|
|
public function sub_items(): array {
|
|
return [
|
|
'Go to Dashboard → Updates and review all pending plugin updates',
|
|
'Before updating, note which plugins have updates and what versions they are moving to',
|
|
'Update plugins one at a time if the site is complex or has many interdependencies; batch update is acceptable for straightforward sites',
|
|
'After each update (or after a batch), check the front-end and any key functional areas (forms, checkout, membership, etc.)',
|
|
'Check for any plugins that have been deactivated but not deleted — flag these to the client',
|
|
];
|
|
}
|
|
public function watch_outs(): array {
|
|
return [
|
|
'WooCommerce updates — always treat these as high-risk, test checkout flow afterwards',
|
|
'Page builder updates (Elementor, Divi, Beaver Builder) — can affect layout rendering',
|
|
'Security plugin updates — confirm they reactivate and are still reporting clean',
|
|
'Plugins that haven\'t been updated by their developer in over 12 months — flag as a risk',
|
|
'Plugins showing "Update unavailable" or removed from the WordPress repository — flag immediately, these can indicate abandoned or compromised plugins',
|
|
];
|
|
}
|
|
};
|