Event statuses
Every event on TimbaTicket has a status. There are four real values stored in the database, plus one derived state that is calculated at display time.
The four database statuses
Draft
The event is still being built. It is not visible to the public and tickets cannot be purchased. This is the starting state for every new event.
Pending Approval
The organiser has asked to publish the event, but it has not gone public yet. This status exists for events that go through an approval step. The event is still not visible to buyers.
Published
The event is live on its public page. Buyers can see the event and purchase tickets. This is the normal operating state for an active event.
Sales Closed
The event is still visible on its public page, but tickets can no longer be purchased. This
happens when the sales window closes (past the ticket's available_until date) or when the
organiser manually closes sales. The event page still shows the event details, but there is
no buy button.
The derived "Ended" state
"Ended" is not a value stored in the database. It is calculated at display time:
An event is "Ended" when its status is Published or Sales Closed, AND its end date (or start date, if no end date is set) is in the past.
Draft and Pending Approval events are never shown as Ended — even if their dates have passed.
This distinction matters: the status column in the database only holds the four values
above. "Ended" is a display label, not a database value.
Summary
| Status | In the database | Visible to buyers | Can buy tickets |
|---|---|---|---|
| Draft | yes | no | no |
| Pending Approval | yes | no | no |
| Published | yes | yes | yes |
| Sales Closed | yes | yes | no |
| Ended (derived) | no | yes (read-only) | no |