Save, preview, publish and manage event versions

Choose the right save action

Save

Stores the current form and content after validation. Wait for the saved confirmation and resolve errors. Saving a draft is separate from publishing it.

Save & Preview

Saves the event, then stages it for preview. Use this when you want to review a version before putting it in front of the public.

Save & Publish

Saves the event, then applies the publish action. Check the published version and any configured publication dates afterwards.

Save Copy

Creates a separate copy and opens it. If the original has unsaved changes, those changes are saved to the original first. To duplicate without changing the original, copy first and edit the new record.

Back

Returns from the editor. Save intended changes first; navigating away is not a substitute for saving.

Delete

Removes the record through a confirmation and dependency checks. It is not an archive button, an order cancellation or a refund. Review associated bookings and shared content before deleting an event.

The status and updated information near the actions help identify the saved state. If an action fails, read the message, correct the affected field or access issue, and try again. Do not assume a staged or published version exists after a failed save.

Use an existing event as a starting point

1. Open the original and choose Save Copy before making the next event’s edits.
2. Confirm that the editor has opened a different record.
3. Update the title, dates, doors-open time, venue, description and page address.
4. Inspect all attached tickets, options, performers, sponsors and agenda records. Do not assume every relationship or allocation has been duplicated as an independent record.
5. Review sale windows, capacity, source IDs, external links and publication settings inherited from the original.
6. Save & Preview, test the new booking journey, then publish the new event when ready.

Review publication and expiry dates

Choose Schedule… to reveal Publish date and Expiry date. Hide schedule collapses the controls; it is not a command to clear their values. These dates concern publication, not the performance start, recurrence or ticket sale window.

Publish date

The intended publication date and time supplied with a staging or publishing action. Confirm the website’s time zone and how its configured delivery layer applies future publication dates before relying on an automatic launch.

Expiry date

The intended expiry date and time supplied with the action. Confirm how your website hides expired content and what visitors see at the existing link. It does not cancel the event, remove sold tickets or notify attendees.

Set the intended values and use the appropriate Save & Preview or Save & Publish action. A schedule value by itself does not prove a timed release is active. Check the resulting state and the public site; existing publication dates can be retained when updating a previously published record.

Compare Staged and Published

1. Save & Preview when you want the latest edits included in the staged version.
2. Open Preview and select Staged to inspect that version in the embedded website.
3. Select Published to compare with the public version.
4. Use Refresh after changes, or Open in new tab when available for a larger view.
5. Test the title, banner, content, venue, supporting records and ticket links. Check a narrow screen as well.

Opening Preview does not save unsaved form values. The top-level website Preview and Live links can help inspect the broader website, but check that you are looking at the intended event and version.

When a preview is missing or looks old

Save the event first

A new or unsaved record may not have enough information for a preview address. Complete the required fields and save.

Missing File Name

Check Details → Page and set or confirm the page address. Then stage the event again.

Missing domain

The website needs the appropriate domain or preview configuration. Ask support to check the website setup rather than inventing a domain value.

No preview version

Use Save & Preview to create a staged version, or publish when the public version is ready.

Old content

Check whether you are viewing Staged or Published, refresh, and confirm the last save or publish succeeded. Related records may also need their own publication step.

Review authoring history and roll back

Use the authoring-history control or History tab to inspect the available version information. The history table can show Title, Status, Updated, Updated by, Published by and Current. A newly created event may have only one version.

1. Identify the version you need using its title, status, timestamp and author information.
2. Where Roll back is available for an earlier version, read the confirmation and confirm only the intended recovery.
3. Review the recovered fields and content. Check related records separately; restoring an event version is not an undo for all orders, relationships or messages.
4. Stage and inspect the result, then publish through the normal workflow if that version should become public.

If Roll back is absent, the selected version may be current, the table may not support the operation, or your access may not permit it. Ask support about the available recovery path instead of deleting and recreating the event.

Final publication checklist

• The public address is correct and any established links still work.
• Dates, location, tickets, prices, capacity and sale windows agree.
• The page and related content show the intended published version.
• A customer can complete the agreed test journey and receive the expected confirmation.
• Someone is responsible for monitoring the first bookings and handling attendee questions.