Hype5 Theater 0.6.17 · Pre-release
Venues
A venue (mängupaik) is a place where performances happen: its address, arrival information and accessibility defaults. Performances refer to a venue; the venue's accessibility values are defaults that each performance inherits unless it sets its own. This page describes Venues in the Hype5 app (permission: edit venues, edit_hype5t_venues); the WordPress editor of a venue edits the same fields and remains as a compatibility screen.
Venues list
Venues lists name, city and room, publication status, address, the wheelchair and hearing-loop defaults (unknown shown muted) and the number of upcoming performances, 50 per page.
- Search matches name, street address, city, room, region and country.
- Show: All, In use (upcoming performances), Not used (no performance and no premiere reference), Accessibility unknown.
- Filter by status and city; sort by name, city, upcoming performances, last changed or newest.
- Bulk (up to 100, by permission): publish, switch to draft, move to Trash. In the Trash view: restore or delete permanently.
Venue editor
One Save stores all changed fields; Publishing… works as for productions.
| Group | Fields |
|---|---|
| Location (Asukoht) | Name, street address, city, region, country, room or hall, website, description (WordPress editor), excerpt. |
| Arrival (Saabumine) | Arrival information. Line breaks are kept. |
| Accessibility (Ligipääsetavus) | Wheelchair access and hearing loop: Yes, No or Unknown; accessibility notes. Unknown is never treated as Yes or No. |
| Coordinates (Koordinaadid) | Optional latitude and longitude as decimals. They are stored only; Hype5 Theater shows no map. |
| Image | Featured image from the media library. |
| Usage (Kasutus) | Counts of upcoming and past performances and premieres, with links. |
A new venue is created on the first Save as draft.
Accessibility inheritance
A performance stores, per item, inherit, yes or no. Its effective value is computed when it is read: its own value, or else the venue's default. Saving a venue therefore changes no performance record: inheriting performances show the new default, and performances with their own value keep it. Before you save a changed default, the editor shows how many upcoming performances it affects. Public pages take accessibility defaults only from a published venue.
Usage
Usage (Kasutus) lists the productions that premiered at the venue and its upcoming or past performances, 50 per page. With the Schedule permission a performance opens in its panel over the venue editor. Without it the list is read-only and leaves out internal notes, attendance and performances of productions you may not read (they are counted).
Trash and deletion
| Action | Effect |
|---|---|
| Move to Trash | The venue page leaves the public site. Performances are not changed, but public schedules no longer name the venue or use its accessibility defaults. Production pages keep naming it as premiere venue until it is deleted permanently. Undo restores it. |
| Restore | Returns the previous status if you may publish venues, otherwise a draft. |
| Delete permanently | Every performance of the venue keeps its room, time and own accessibility values but no longer has a venue; accessibility it inherited becomes unknown. Productions keep the stored premiere reference, but their public page no longer shows a premiere venue. The dialog lists these consequences first. |
On multilingual sites, performances refer to the original-language venue; deleting or trashing a translation changes no performance.