Eventually Ticketing
Troubleshooting

Event creation and editing issues

Problems creating or editing events are usually fixed with a few checks. This guide covers the most common issues: events not showing on your calendar widget, recurring events not generating correctly, image upload problems, capacity settings not working as expected, and custom registration fields not saving.

Event not appearing on the calendar widget

If you created an event but don't see it on your website's calendar widget, work through these checks.

Check 1: Is the event published?

Events must be published to appear on your calendar widget. Draft events remain hidden until you publish them.

  1. Open your event in the Eventually dashboard.

  2. Look at the event status near the title.

  3. If it says Draft, click Publish event to make it live.

Check 2: Is the event date within the widget's range?

By default, calendar widgets show events from the past 6 months through the future. If your event is outside this window, it won't appear.

To show past events or extend the date range, adjust your widget settings in Customization → Widgets. See Set up your calendar widget for details on configuring display filters.

Check 3: Is the event sold out or capacity full?

Widgets can filter out sold-out events. If you've enabled "show available only" in your widget settings, events with no remaining capacity won't display. See Set event capacity and ticket limits to check availability.

Check 4: Is a category filter blocking it?

If your widget is filtered to specific categories, events without matching categories won't show. Make sure your event has at least one category that matches the widget's filter.

Check 5: Refresh and cache

Squarespace caches embed blocks. If you just published an event or made changes, the widget may take a few minutes to update. Try:

  • Hard refresh your browser (Ctrl+Shift+R or Cmd+Shift+R)

  • Wait 5–10 minutes for the cache to clear

  • Check the event in the Eventually dashboard to confirm it's published

Recurring events not generating correctly

Recurring events must have an end condition — Eventually doesn't support open-ended series. If your recurring event isn't generating all the sessions you expect, check these settings.

Missing the end condition

Every recurring event requires one of these:

  • End after X occurrences — The series stops after a specific number of sessions.

  • End by date — The series stops after a specific calendar date.

If you don't set an end condition, the series won't save properly. Make sure your schedule includes either an occurrence count or an end date.

Excluded dates

If you excluded dates for holidays or breaks, those sessions won't appear. Check your recurring event's date exclusions in the Eventually dashboard to confirm the dates you expect are included.

Editing scope issues

When you edit a recurring event, you choose how far the changes apply: This event, This and following events, or All events. If you expected changes to apply to future sessions but they didn't, you may have chosen This event instead of a broader scope.

See Creating recurring events for more on edit scopes and managing recurring series.

Monthly recurring event fails to publish

Some monthly recurring events that repeat on a specific weekday position (for example, "the first Monday") may fail to publish with a server error if the stored schedule is missing its week position.

Cause: A small number of older or incomplete saved monthly rules were missing the week-position detail required to generate the series. This triggered an error at publish time.

Fix: Re-open the event and click Publish event. The system now derives the week position from the event's start date when the stored value is missing. Events that start on the fifth occurrence of a weekday in the month are treated as Last so the series does not drift into the next month. If you explicitly set a position in the editor, that choice still takes precedence. No data migration is needed.

Images not uploading or displaying

If you're having trouble adding images to your event, check these limits and error messages.

Upload limits

Event images have these constraints:

  • Maximum images: 10 per event

  • Maximum file size: 5 MB per image

  • Accepted formats: PNG, JPG, WebP, GIF

If you see an error like exceeds 5MB limit or Events can have at most 10 images, you've hit one of these caps.

File type rejected

The message unsupported type means the file isn't in an accepted format. Convert your image to PNG, JPG, WebP, or GIF before uploading.

Images not showing on the widget

If images uploaded successfully but don't appear on your calendar widget:

  • Make sure the images finished processing — large files take longer

  • Refresh the page where your widget is embedded

  • Check that the widget display settings include image previews

For step-by-step upload instructions, see Add multiple images to an event.

Capacity or ticket limits not working

If tickets aren't selling out when expected, or capacity numbers seem wrong, check these settings.

Unlimited vs. defined capacity

Leaving the capacity field blank means unlimited — not zero. If you meant to cap attendance, enter a number in the Total Event Capacity field.

  • Total Event Capacity: Sets an overall cap for the event across all ticket types

  • Ticket Limit: Caps a specific ticket type individually

For example: If Total Event Capacity is blank but VIP tickets have a limit of 20, General Admission sells unlimited — only VIP stops at 20.

Both limits can apply at once

If you set both Total Event Capacity and per-ticket limits, the more restrictive one wins. A 100-person event with VIP capped at 20 means VIP stops at 20, but General keeps selling until the combined total hits 100.

See Set event capacity and ticket limits for detailed examples.

Recurring events have per-session capacity

Each session in a recurring series has its own capacity. If you updated capacity for one session but expected it to change others, check your edit scope — you may have applied it to This event instead of All events or This and following events.

Custom registration fields not saving

Custom questions for attendees help you collect extra information at checkout. If they're not saving or appearing, check these issues.

Missing field label

Each custom field requires a label — the question or prompt shown to attendees. If you try to save without a label, the field won't persist.

Field types available

Custom fields support these data types:

  • Short text — One-line answer

  • Long text — Multi-line answer

  • Dropdown — Single selection from a list

  • Checkbox — Multiple selections from a list, or a single checkbox

  • Yes / No — Simple toggle

Make sure you selected the right type and added options for dropdown and checkbox fields. For detailed setup instructions, see Custom registration questions and fields.

Name and email are always collected

You don't need to add name or email fields — they're captured automatically for every attendee. The empty state message No custom questions yet. Name and email are always collected. confirms this.

Completed event returned to Upcoming after rescheduling

If you change a completed event date to the future, it may leave the Completed tab and reappear in Upcoming. This is expected for single, standalone events.

Cause

Eventually automatically marks published single events as Completed once their effective end time passes. When you reschedule a standalone event to a future date and save it, the system restores the event to published automatically so it shows in Upcoming again.

What to expect

The restore only runs if the event is ready to publish — for example, it has tickets, an external registration URL, or registration disabled. Recurring series events are excluded and keep their original status behavior.

If an event is already stuck in Completed with a future date, open it, adjust the date if needed, and click Save changes. The event will move to the correct tab on its own.

General event creation errors

If you see error messages during event creation, check these common issues.

"Event name is required"

Every event needs a title. Enter a name in the first step of the wizard before continuing.

"Date and time are required"

For single events, set Start at before leaving the details step. For multi-day events, add at least one event date. The wizard won't let you proceed without a date.

"Something went wrong saving. Please try again."

This generic error can mean a temporary connection issue or an unexpected validation failure. Try:

  1. Saving as a draft first, then publishing

  2. Refreshing the page and re-entering your changes

  3. Checking for browser console errors (open Developer Tools → Console)

When to contact support

If you've worked through these checks and still can't create or edit your event, reach out to Eventually support at [email protected]. Include:

  • The event name and status (draft/published)

  • What you were trying to do (create new, edit existing, add images, set capacity, etc.)

  • The exact error message you saw

  • Screenshots if possible

Was this helpful?