Known limitations

Hype5 Theater #

Scope #

• No ticket sales, seating, payments, maps, geocoding or routing. Ticket offers are links to external sellers; venue coordinates are stored but not shown.
• Access to the Hype5 app is still enabled per site — for the users in its access list, or for everyone with a constant. Opening it for every user with a Hype5 permission is pending; users without access keep the classic menu. Users whose only Hype5 permission is Settings or Vocabularies cannot open the app. The app lists at most the 500 most recently changed productions; bulk actions, Trash and Quick Edit for productions, author, comments and revisions stay on the WordPress screens. Public pages are not previewed with unsaved changes.
• No browser-side draft recovery in the app: closing the tab after confirming the warning discards unsaved changes.

Safeguards and their exact limits #

• Protection against overwriting newer changes (version checks, WordPress's edit lock, refused stale saves) covers the Hype5 app and the guarded classic forms rendered after the guard was installed. It does not cover the WordPress REST API, WP-CLI, importers, other plugins, native Bulk Edit, or classic editor tabs opened before an update. The app detects such writes and never overwrites them silently.
• Scheduled publication depends on WP-Cron, as in WordPress; on low-traffic sites without a system cron it can be late.
• Passwords are stored as WordPress stores them (plain text in the post), by WordPress's design. The app sends a password only to people who may publish.
• Core REST term routes bypass the vocabulary rule that a used term cannot be deleted.
• Public REST answers that depend on a visitor's password cookie carry no Cache-Control: private header, as in WordPress core.

Content and presentation #

• Paused vocabulary terms stay public on the records that have them.
• Changing a permalink base adds no redirects. Old addresses stop working. Choose bases before the site is public.
• A deleted starting vocabulary term is added again on the next database update; pause it instead.
• Collection counts can include rows that the multilingual visibility rule then hides.
• One password per visitor: WordPress remembers one entered post password per browser. If two language versions of a production have different passwords, entering one forgets the other, and the translation's own password does not open the dates and offers that belong to the original. Nothing is shown that should not be (it fails closed), but to avoid confusion we recommend the same password on every language version.
• Multilingual testing: the multilingual rules are covered by automated tests; a run on live WPML and Polylang installations is not recorded for this build.

Password-protected and multilingual productions #

Found while testing Hype5 Stage 1.0.2 against this build and reported to the Hype5 Theater project; they matter only on sites with password-protected productions or with translations:

• Page caches. Pages that depend on a password entered for another language version, a production embedded in another page with [hype5_production], and the schedule filtered to one protected production are sent without no-cache headers. After a visitor has entered the password, such a page can show the production's dates and offers; a page cache that does not bypass WordPress's password cookie could keep that version. Keep these pages out of page caches.
• Embedded productions ([hype5_production] or the block on another page) follow the production's own password rule. After a visitor has entered that password, the embedding page shows the production's schedule and offers too.
• Productions list order and city filter. The next performance order and the city filter of the productions list also consider performances of productions that are not public to everyone, so a locked card keeps its place among dated ones — which hints at when it plays and shows that it is playing — and the city filter can reveal that a protected production, or a translation of an unpublished one, plays in a city.
• A published translation of an unpublished original shows its own teaser and text through the production page's header, feeds, the REST API and search; nothing of the original's dates, offers or credits is shown.
• Search can match the text of a translation that is protected only through its original's password (with Hype5 Stage, such results show the title only).

Open checks before release #

• Screen readers and real devices: no screen-reader session (for example on the credits editor, the schedule composer and vocabularies) and no real phone or tablet check yet. The automated accessibility scan is clean except for WordPress core's classic-editor toolbar.
• Estonian terminology awaits a native-speaker review; some Estonian labels may change.
• Browsers other than Chromium have not been separately tested.

Hype5 Stage #

• Hype5 Theater build: the enhancements need Hype5 Theater 0.6.17 with the Phase 5K presentation contract; with an earlier 0.6.17 build Stage runs as a plain theme. A template whose contract moves to a new major version falls back to the plugin's template automatically; other plugin changes are caught and the affected home-page section is left out — test after every plugin update.
• Productions that are not public to everyone (for example password-protected ones) are left out of the home page Marquee, Next on stage, the poster wall and the count of performances ahead, also after a visitor has entered the password. They stay on the plugin's own lists as locked cards and on their own page with the password form.
• "N performances ahead" is not shown when more than 500 performances are upcoming, rather than risk counting hidden ones.
• Multilingual naming in the Marquee: the Marquee names a performance by its original-language production; the plugin's own schedule names the reader's-language version. Only multilingual sites are affected.
• Cast lists show the character: Stage's roles and cast lists show a performer's character (the profession only when there is no character). Two of the plugin's own visibility checks look for the profession label in the page and therefore report a difference under Stage; this is presentation only.
• Some home-page services are internal: Stage uses a few plugin services classified as Internal. If one changes, the home-page section that uses it is left out.
• Main menu depth: the header shows top-level menu items only; there are no drop-down menus.
• Logo format: WordPress does not accept SVG uploads and Stage does not enable them; use PNG. Blend suits single-colour dark logos only.
• Content Security Policy: Stage uses an inline <style>@import …</style> for the cascade layer and a small inline script for the colour scheme. A CSP that forbids inline styles or scripts must allow them, or switch the layering off with hype5_stage_layer_theater_styles.
• Not yet measured on a real phone or with a screen reader. Accessibility was checked with axe-core, keyboard tests, forced-colours emulation and contrast measurements.
• Performance: the main stylesheet (about 77 KB minified, 15 KB compressed) blocks rendering; production pages add the plugin's two stylesheets. The variable heading font is about 201 KB.
• Test content: Stage has no rule to exclude test or sample productions from the home page; unpublish them or move their dates.
• Translations: British English and Estonian; other languages fall back to English.
• Minor: the schedule page's heading and its first section heading can show the same word (for example Mängukava in Estonian).

Hype5 Theater and Hype5 Stage together #

• Page caches: with Stage 1.0.2 the home page, menus and lists are the same for every visitor, and production pages that depend on a password are sent with no-cache headers. Two of the plugin's cases listed under Password-protected and multilingual productions remain: a production embedded in another page with [hype5_production], and the schedule filtered to one protected production. Keep those pages out of page caches.
• Stage 1.0.1 with the Phase 5K build is not recommended: on multilingual sites its home page and menu can show the date of a production whose reader's-language version has a password, and after a visitor has entered a production's password its home page shows that production's time, venue, ticket price and cast. Update to Stage 1.0.2.

This documentation #

• These pages describe pre-release builds and will change before release.
• Support and licence-account links will be added when those services exist.
• Product screenshots are being introduced: a first set from the fictional Black Box Theater demo is in review and is published only after approval.