Compatibility
Hype5 is meant for many different sites, themes and hosts. This page separates what was tested for Hype5 Theater 0.7.0 from what is only declared by its requirements and what is not supported. Only the combinations marked Tested are supported; everything else may work but carries no claim.
On this page
For version-by-version details see the Compatibility matrix. The minimum versions each product declares are on Requirements.
Status values
- Tested — exercised by the automated suites or scenario runs of the Hype5 Theater 0.7.0 release gate.
- Tested (limited) — exercised only by the checks named in the row.
- Simulated — the integration's interfaces were imitated in tests; the real product was not installed.
- Not tested — no 0.7.0 run; no support claim.
- Not supported — known behaviour that does not meet the plugin's rules (see the row).
WordPress, PHP and database
Hype5 Theater 0.7.0 declares WordPress 6.6 and PHP 8.1 as its minimum (Requires at least, Requires PHP); its release metadata names WordPress 7.1 as tested up to.
| Component | Version | Status | What was run |
|---|---|---|---|
| WordPress | 7.1.3 | Tested | WordPress runtime suites (1,807 checks), browser suites (18), native suites (67), clean install, upgrade through the updater, rollback; a live staging site |
| WordPress | 6.6.2 (the declared minimum) | Tested (limited) | clean install, upgrade from 0.6.17 through the updater, rollback and re-upgrade; the Hype5 app opened (Overview, Productions, Schedule, Settings, the Story editor) without errors |
| WordPress | 6.7 – 7.0 | Not tested | within the declared requirement (Requires at least: 6.6) |
| PHP | 8.3 | Tested | every disposable test run above |
| PHP | 8.4 | Tested (limited) | live staging site: public pages, the Hype5 app pages and REST answers, non-destructive checks |
| PHP | 8.1, 8.2 | Not tested | declared minimum (Requires PHP: 8.1) |
| MariaDB | 10.11 | Tested | every disposable test run |
| MariaDB | 11.8 | Tested (limited) | live staging site, read-only checks |
| MySQL | any | Not tested | the plugin uses InnoDB, transactions and GET_LOCK (see Requirements) |
| Multisite | — | Not tested | network activation is refused by the plugin; per-site activation is untested |
Hype5 Stage 1.0.2 declares WordPress 6.6 or later (tested up to 7.1 in its theme header) and PHP 8.1 or later; its own pre-release tests used WordPress 7.1.3 with PHP 8.3; the demo site (PHP 8.4) received read-only checks.
Hype5 does not depend on a particular host's behaviour such as specific caches or server modules, but any page cache or CDN in front of the site must honour the plugin's no-cache headers (see Caches). Hype5 Theater does need a database that supports InnoDB tables, transactions and named locks, and a database user that may create tables. See Requirements.
Themes
| Theme | Status with Hype5 Theater 0.7.0 | What was run |
|---|---|---|
| Hype5 Stage 1.0.2 | Tested | public pages including the home page (in the cache scenarios and the anonymous exposure scan), Stage's production hero agreeing with the schedule, all 21 template overrides Current, real Polylang, a staging site; Stage's own contract suite ran against the Phase 5K build |
| Hype5 Stage older than 1.0.2 | Not supported with 0.7.0 | the release metadata names Stage 1.0.2 as the minimum |
| Twenty Twenty-Five (block theme) | Tested | the runtime and browser suites run under it; cache scenarios; exposure scan |
| Twenty Twenty-One (classic theme) | Tested (limited) | cache scenarios and the anonymous exposure scan only |
| Other themes | Not tested | the plugin's templates and shortcodes are theme-independent by design; a theme that prints production details itself must use Visibility::presentable() (see Presentation services) |
- Hype5 Theater's public pages render through the plugin's own templates; a theme may override them. The optional clean single templates setting uses the plugin's own single-page template for productions, people and venues instead of the theme's single-post layout. See Settings.
- Hype5 Stage is a classic theme with
theme.json. It works without Hype5 Theater; with the plugin active it adds the theatre templates — tested with Theater 0.7.0, and its own check also accepts the 0.6.17 Phase 5K builds. See Hype5 Theater integration.
Editors and page builders
| Editor | Status with Hype5 Theater 0.7.0 | Notes |
|---|---|---|
| Classic editor of Hype5 productions, people and venues (the compatibility screens) | Tested | native suites (67) and the browser suites' native-editor checks |
| Block editor (the two Hype5 blocks in pages and posts) | Not tested in 0.7.0 | last checked in Phase 5K (editor preview) |
| Page builders (Elementor, Divi, Beaver Builder, WPBakery) | Not tested |
- Productions, people and venues are edited in the Hype5 app. When one is opened in WordPress's own editor (a compatibility screen), Hype5 Theater always uses the Classic Editor for it, and leaves the editor of every other post type unchanged. No Classic Editor plugin is needed.
- Shortcodes are the main way to place Hype5 content in pages and posts. WordPress renders them in the Classic Editor and in a Shortcode block, and page builders that render WordPress shortcodes can show them too. Hype5 does not depend on any page builder. See Shortcodes.
- Two optional blocks are available when the block editor is used on pages or posts. See Blocks.
- Hype5 Stage supports both Classic Editor and block content in pages and posts.
Multilingual plugins
| Plugin | Status with Hype5 Theater 0.7.0 | What was run |
|---|---|---|
| Polylang 3.9.0 | Tested | the real plugin, Estonian as the default language and English in a directory (/en/): 23 in-process and 19 HTTP checks of translation lookups, passwords per version, no-cache headers, search and counts |
| Polylang, language set from the content (no language in the address) | Not tested | the plugin's headers cover it by design |
| WPML | Simulated | its filters (wpml_object_id, language, translation-group interface) imitated in the runtime suites; the real WPML plugin was not installed — WPML is not a supported integration for 0.7.0 |
| TranslatePress, Weglot, MultilingualPress, others | Not tested |
Translations carry their own texts; performances, credits, galleries and other shared rows are stored once, on the original-language post. See Translation and localisation and Multilingual sites.
Caches
| Kind | Status with Hype5 Theater 0.7.0 | What was run, or what is required |
|---|---|---|
Full-page cache that honours Cache-Control (keyed by address, no cookie bypass; and one that bypasses only WordPress's login cookies) |
Tested | 11 password scenarios, each with an authorised and an anonymous visitor first, under three themes: no leak, no stale page |
| WordPress caching plugins (WP Super Cache, W3 Total Cache, WP Rocket, LiteSpeed Cache, host caches) | Not tested | they must honour the plugin's Cache-Control: no-cache, must-revalidate, max-age=0, no-store, private and must not serve cached REST answers |
| CDNs and edge caches (Cloudflare, Fastly, Varnish) | Not tested | a rule that caches HTML regardless of the origin's Cache-Control (for example Cache Everything with an edge lifetime) defeats the protection of password-dependent pages |
| Persistent object cache (Redis, Memcached) | Not tested | the plugin's cache entries are keyed by WordPress's last_changed and expire after one hour; WPML translation linking without a post save can be stale until then |
The tested full-page cache was nginx's proxy_cache. Pages whose content depends on an entered password are sent with the headers above; see Security and content visibility.
Search
| Search | Status with Hype5 Theater 0.7.0 | Notes |
|---|---|---|
WordPress's own search (site search, /wp/v2/search, REST ?search=) |
Tested | productions with a password in their chain and translations of unpublished originals are left out for visitors |
| Relevanssi, SearchWP, ElasticPress and other plugins that replace WordPress's search query | Not supported for protected content | they bypass the plugin's posts_search rule; their own index decides what they show — exclude password-protected and unpublished productions there |
Browsers and devices
| Item | Status | Notes |
|---|---|---|
| Hype5 app in Chromium | Tested | headless Chromium (Playwright): 18 browser suites |
| Hype5 app in Firefox, Safari, Edge | Not tested in 0.7.0 |
- Hype5 Theater's public output is rendered on the server as HTML; scripts add features such as the image viewer and the gallery carousel.
- The Hype5 app needs JavaScript. Without it, the app shows links to the WordPress list of productions and (for users who may change settings) to System Status, which keep working.
- Hype5 Stage was tested without JavaScript (content, navigation and the default colour scheme keep working) and with automated tests in Chromium at desktop, tablet and phone widths.
- Testing with real phones and screen readers is still to be done; see Known limitations.
Updates
| Item | Status | Notes |
|---|---|---|
| Hype5 Theater updates from the Hype5 update service (stable channel) | Tested | the plugin's own update client and WordPress's upgrader against a test copy of the update service: 0.6.17 → 0.7.0, rollback, re-upgrade |
| Beta channel of the update service | Not usable by the update client | the client always asks for the stable channel; a pre-release version (for example 0.7.0-beta.1) is never offered automatically |
Hype5 Stage has no automatic update channel; it is updated by uploading its ZIP. See Updating and troubleshooting.
Multisite
Network activation of Hype5 Theater is refused; activate it on each site separately (per-site activation was not tested with 0.7.0). On multisite only super admins have the capability to edit custom CSS.
Other plugins
Hype5 Theater registers its own post types, taxonomies, capabilities, REST routes and database tables with the hype5t_ prefix. Other plugins can extend it through the documented hooks and add-on interface. The application's protection against conflicting saves covers its own screens and the guarded classic forms, not other plugins, REST clients or WP-CLI writing the same data. See Known limitations.