Catching the Bugs Nobody Reports
Einhorn Collaborative
On July 22, 2026, during a high-visibility announcement, first-time visitors to Einhorn Collaborative's site saw a stale version of two pages. Our security-log scan found the cause, and the fix was live the same day, within about an hour.
A busy site with several systems that update on their own
Einhorn Collaborative's site runs on WordPress with a caching plugin for speed and a security firewall in front. Each is built by a different company and updates on its own schedule.
When two of those layers conflict, the site rarely goes down. It just behaves differently for some visitors, which is why these problems tend to go unreported.
What ongoing care covers
Maintenance on this site goes beyond updates. It includes checks built to find conflicts that don't show up for returning visitors.
- Regular site scans for health, updates and security status
- A security-log scan that flags legitimate traffic being blocked
- A first-time-visitor check on key pages, especially before announcements
- A plain-language health and issue-prevention report written for the client team
Why returning visitors never saw it
The problem only affected people who had never visited the site before. Staff and regular readers saw the correct pages, so nobody would have reported it. That is why first-time-visitor checks are now part of maintenance.
How the July incident was handled
July 22, 2026
The security-log scan showed the firewall blocking a routine caching task, the one that decides which version of a page a new visitor gets.
Same day
We added that task to the firewall's allow-list and confirmed on the live site that new visitors got the current page. Done within about an hour.
July to August 2026
The same scan turned up two more false blocks of the same kind in the editing screens. In August we also let Facebook's link-preview tool through after the firewall blocked it 128 times in a week.