WordPress event missing from the public calendar? Trace the listing before changing settings

Capture one missing event

Download the missing-calendar event comparison worksheet (Markdown, English)

Record the event title, editor URL, direct public URL, intended date and time, calendar-view URL and the time you checked. Open the calendar signed out, select the correct month or list date range, and repeat on a phone. Does the direct event page work while only the listing is absent? Is the entire view empty? Keep a direct event link available on the public site while you investigate, once you confirm it leads to the current event.

Use the English worksheet to compare one missing event with one event that appears in the same view. Record observations; change one setting at a time. A signed-in editor preview cannot establish what a visitor receives.

Check the event record before the calendar system

In the WordPress editor, confirm the missing event is published, has the intended start and end dates, and is meant for the selected calendar range. The Events Calendar has a “Hide from Event Listings” option that can leave a direct event page available while hiding it from list-style views (Month View can still show it); check that option against the organizer’s intent. Also check any visibility restriction used by this particular site. Change only an incorrectly set field, then inspect the public view again.[1][2][5]

If several records are missing, compare what they share: category, recurrence, date range or template. Do not assume that a working direct URL proves the record qualifies for every calendar view. Confirm the date and visibility with the content owner first.

Compare the public view and delivery layer

When the record looks right, compare the same calendar URL signed out in two browsers or networks. If only one copy is stale, identify the browser, page-cache or CDN layer before refreshing it. A blanket purge may briefly mask a wrong event setting, template or update rule. If all visitors see the same omission, inspect the selected calendar view and site-specific template settings rather than repeating cache clears.[1]

If the event URL itself returns a 404 after a move, treat it as a route problem, separate from a missing listing. WordPress documents that visiting Settings → Permalinks flushes rewrite rules; do not change the permalink structure casually. Record the exact URL and hand the route issue to the WordPress maintainer.[4]

Repair in staging and verify the visitor path

Reproduce the symptom on a staging copy before testing a theme, plugin or template conflict. Preserve a recovery point, then isolate one variable and retest the same event and view. The provider recommends staging for conflict tests; disabling themes or plugins on the live site can disrupt the public event and ticket journey. Document the evidence and have the site owner approve the smallest supported change.[3]

After release, visit the published calendar signed out on desktop and phone. Find the event in the intended date range, open its page, and follow the current ticket or registration link if present. Repeat for a previously visible event so the repair has not hidden another listing. Log the changed setting, release time, URLs, devices and owner. If the event remains absent, restore the tested baseline and send the comparison record to the plugin or hosting maintainer.