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.
• The Hype5 app lists at most 500 productions (the most recently changed); 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.
• The plugin's production-scoped REST answers (/hype5-theater/v1/performances?production= and /hype5-theater/v1/credits) depend on the visitor's password cookie and are sent with no-cache headers (since 0.7.0), so an edge cache does not keep them. Core REST answers for productions never depend on the password cookie and stay cacheable.

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.
• Multilingual testing: the real Polylang 3.9.0 plugin was tested with 0.7.0. WPML was not tested with the real plugin — its interfaces were only simulated — so WPML is not a supported integration for 0.7.0. See Compatibility.

Password-protected and multilingual productions #

They matter only on sites with password-protected productions or with translations.

Resolved in Theater 0.7.0. The five issues found while testing Hype5 Stage 1.0.2 against the Phase 5K build are fixed in the plugin: pages whose content depends on an entered password (also for another language version, and a schedule filtered to one production by the address) are sent with no-cache headers; a production embedded in another page, and WordPress's feeds, archives, search and core REST answers, keep a protected production protected also after its password was entered; the productions list's next order and city filter, and schedule counts, use only productions public to everyone; a published translation of an unpublished original shows only its title, address and poster; and WordPress's search no longer finds, for visitors who are not logged in, any language version of a production with a password in its chain. See Security and content visibility and the changelog.

What remains:

• 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: each page opens only with its own password (since 0.7.0 including its dates and offers), not with the other's. Nothing is shown that should not be (it fails closed), but to avoid confusion we recommend the same password on every language version.
• Search plugins are not supported for protected content. Plugins that replace WordPress's search query (for example Relevanssi, SearchWP, ElasticPress) bypass the plugin's search rule; their own index decides what they show. Exclude password-protected and unpublished productions there.
• Caches other than a header-respecting page cache were not tested. A full-page cache that honours Cache-Control was tested. WordPress caching plugins, host caches, CDNs and edge caches, and persistent object caches (Redis, Memcached) were not: a cache must honour the plugin's no-cache headers and must not serve cached REST answers, and a CDN rule that caches HTML regardless of the origin's headers defeats the protection of password-dependent pages. With a persistent object cache, the plugin's entries for these rules expire after one hour; with WPML, linking translations without saving a post can leave them stale until then.

Updates and rollback #

• Only the stable update channel. The plugin's update client always asks the Hype5 update service for the stable channel; a pre-release (beta) version is never offered on the Plugins screen and is installed from its ZIP.
• Rolling back to 0.6.x gives capabilities back. A 0.6.x version re-adds the full Hype5 capability set to Administrator and Theater Manager on its first admin page, including capabilities you removed or denied, recreates a deleted Theater Manager role, and uses its access list for the Hype5 app again. Check the roles after such a rollback. See Rolling back.

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 (including the new 0.7.0 wording of Settings → Advanced → Access); some Estonian labels may change.
• Browsers other than Chromium have not been separately tested with the Hype5 app.
• Not tested with 0.7.0: WordPress 6.7 to 7.0, PHP 8.1 and 8.2, MySQL, multisite, the block editor's two Hype5 blocks (last checked in Phase 5K), page builders, and themes other than Hype5 Stage 1.0.2, Twenty Twenty-Five and Twenty Twenty-One. See Compatibility.

Hype5 Stage #

• Hype5 Theater build: the enhancements need Hype5 Theater 0.6.17 with the Phase 5K presentation contract, or Theater 0.7.0 (presentation API 1.0, tested); 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 and Theater 0.7.0 the home page, menus and lists are the same for every visitor. Since 0.7.0 the plugin itself sends the no-cache headers for the pages that depend on a password — a production's own page and a schedule that the page's address filters to one production; a production embedded in another page shows as protected to every visitor and needs no such header; Stage 1.0.2 also sends its own for production pages, which is a harmless duplicate. Only a header-respecting full-page cache was tested (see Password-protected and multilingual productions).
• Stage 1.0.1 is not supported with Theater 0.7.0 (whose minimum is Stage 1.0.2) and not recommended with the Phase 5K build: with that build, 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 versions — Hype5 Theater 0.7.0 (Beta — by invitation) and Hype5 Stage 1.0.2 (Pre-release) — and will change before a stable release.
• Support links will be added when that service exists.
• Product screenshots are being introduced: a first set of eight from the fictional Black Box Theater demo is published, and new or changed images are published only after the owner's approval. The images whose dates follow the site's date format show the demo's British format (22 October 2026).