- 0:00–0:06
Identify the running site • Ask the host for runtime evidence. • WordPress maintainer • Host ticket • Requested • Site A • PHP / notice
An illustrated website with tools introduces Site A. The site identifier and a PHP / notice request move into the Host ticket. Requested remains visible; no patch confirmation is shown.
- 0:06–0:12
Protect the test copy • Agree email and payment test destinations. • Live site • Protected test copy • Test plan • Test email • Test payment
The live site stays separate while Test email and Test payment arrangements move from the test plan into the protected test copy. These are planned test destinations, not live messages or payments.
- 0:12–0:18
Check the enquiry destination • Compare the expected and observed delivery. • Test mailbox • Compare • Test enquiry • Expected • Observed
A Test enquiry moves into the Test mailbox. Expected and Observed records then enter Compare. No delivery result or pass mark is asserted.
- 0:18–0:24
Reconcile a test order • Match the order, payment and email records. • Compare records • Order · TEST-A • Payment · TEST-A • Email · TEST-A
Order, Payment and Email records each display the illustrative reference TEST-A and move into Compare records. The shared reference connects the records; no production payment route is verified.
- 0:24–0:30
Keep one completion record • Name owners and mark what remains untested. • Change record • Host evidence • Test results • Untested: owner
Host evidence and Test results enter the Change record, followed by Untested: owner. The untested item stays visible, preserving the remaining responsibility instead of implying that all checks passed.
A silent illustrative maintenance workflow follows hosting evidence, protected testing, enquiry delivery and test-order reconciliation into a documented handover.
Read the article: WordPress PHP security update: what owners need to fix