# Missing WordPress calendar event: comparison and release worksheet

This editable worksheet is in English. Use it for a WordPress site running **The Events Calendar**. Keep the organizer's approved event facts as the source of truth. Make one evidence-led change at a time, preferably in staging.

Before sharing this sheet, remove admin tokens or private query values from editor URLs and redact attendee details from screenshots.

## 1. Reproduce the public symptom

| Field | Missing event | Visible comparison event |
| --- | --- | --- |
| Event title and editor URL |  |  |
| Direct public event URL |  |  |
| Public calendar/list URL and selected date range |  |  |
| Approved start/end date and time |  |  |
| Published status and intended visibility |  |  |
| Category/recurrence/template, if relevant |  |  |
| “Hide from Event Listings” setting |  |  |
| Signed-out desktop result, browser and time |  |  |
| Signed-out phone result, browser and time |  |  |

**Which symptom is true?** [ ] one event is absent from a working view  [ ] several events are absent  [ ] the whole view is empty  [ ] the direct event URL returns an error

## 2. Trace the evidence

| Possible layer | What the comparison shows | Owner and next controlled check | Result |
| --- | --- | --- | --- |
| Event record or visibility |  | Confirm approved facts; correct only a wrong field |  |
| Selected date range or view |  | Compare the same month/list range and filter |  |
| Browser/page/CDN cache |  | Compare signed-out clients; identify affected layer |  |
| Calendar template or plugin/theme conflict |  | Reproduce in staging; isolate one change |  |
| Direct URL or route issue |  | Record exact error; send to WordPress maintainer |  |

Direct event link available during investigation: ________  Verified by: ________  Time: ________

## 3. Approve and verify the smallest repair

**Evidence-backed diagnosis:** ________

**Proposed change and responsible owner:** ________

**Staging reproduction and backup/recovery point:** ________

**Rollback action if the test fails:** ________

**Approval and release time:** ________

| Public visitor check after release | URL / device / browser / time | Pass, fail or not tested |
| --- | --- | --- |
| Missing event appears in the intended range |  |  |
| Event page shows approved date and venue |  |  |
| Current ticket/registration link works, if present |  |  |
| Previously visible comparison event remains visible |  |  |
| Phone and desktop signed-out views agree |  |  |

If the event is still absent, restore the tested baseline and give this record to the plugin or hosting maintainer. Do not label a cache refresh as a permanent fix without identifying why the view went stale.