Loyalist Business Association

The Loyalist Business Association runs a directory of 286 local businesses. Its paying members are meant to appear at the top, with richer listings and renewal reminders. For a volunteer-run non-profit, that member tier is a large part of what it offers.

After the directory plugin and its paid add-ons were upgraded in August 2026, that stopped working. The association's admin would mark a member as Featured and save it. It held, and then a few minutes later it was gone. Renewal dates were overwritten, listing details stopped displaying, search on the home page broke, and the site stopped sending email, so the contact form had to come down.

Behind the symptoms was a bigger problem: nobody knew what had actually gone wrong, and the association couldn't afford a fix that guessed.

Diagnosis before repair

We started by measuring, not changing anything. The directory's public data feed showed every one of the 286 listings being rewritten in a single batch, set off by the first visitor after a quiet spell. That's the signature of a background task overwriting the admin's changes. Only listings enrolled in a membership plan lost their settings: the upgrade had switched on a plan-enforcement system the directory had never been set up for. Three full-site backups we found in the admin panel told the rest of the story. 40 members were featured on 11 August, 41 just after the upgrade, and only 11 by 11 September. The damage was gradual, which is why the site looked fine when the upgrade finished.

Foundations first

A rollback would have restored member placement, but none of the backup's 30 checkable renewal dates matched the association's records, and it carried older faults with it. So we fixed the foundations first. The site's email depended on an account nobody at the association could reauthorize, which also left 31 member accounts stuck waiting for verification emails. We moved it to a transactional email service in the association's own name, rebuilt the contact form with nothing left to expire, and set up every new account in the association's name, not ours.

Rehearsed on staging

The site had no host-level backups, so we took and checked our own before every change, and blocked email on the staging copy so no member received a test renewal notice. The rehearsal paid off. The vendor's recommended upgrade moved 245 of the 286 listings to the trash on the test copy. We caught it, restored the copy, reported the fault to the vendor and reworked the sequence until it ran cleanly.

Proving it held

The original fault took about three weeks to show, so a site that looked fixed on day one proved nothing. We forced the background task to run on demand and compared a full snapshot of the directory every morning for three days. Only after 72 hours with zero unexplained changes did we replay the proven steps on the live site, with click paths, expected numbers and a rollback plan written down beforehand. The real renewal dates came from the association's own records.

The live directory is whole again, and the association knows exactly why it broke and how to keep it working.

• Members correctly featured: 3 → 39 of 39
• Renewal dates matching records: 0 → 39 of 39
• Listings preserved: 286 of 286, including 245 saved from a faulty upgrade caught in testing
• Unexplained changes in the 72-hour watch: 0
• Production incidents: 0

We also connected the association's newsletter to its own domain so fewer issues land in spam, and left a plain-language care guide that explains what's safe to edit and the one action that can quietly undo the repair. We wrote up the fix step by step in When a WordPress Plugin Update Breaks Your Site.

Rocket 5 Studios is a member of the association, and we did the directory repair as volunteer time. See more of our websites for non-profits and community groups.

WordPress, Divi, Directorist (Pricing Plans, Claim a Listing), WP Mail SMTP, Resend, MailerLite, Google reCAPTCHA, WP Crontrol, phpMyAdmin, Python