Compatibility

For version-by-version details see the Compatibility matrix.

WordPress and PHP #

Hype5 does not depend on a particular host's behaviour such as specific caches or server modules. 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 #

• Hype5 Theater works with classic and block themes. Its public pages render through the plugin's own templates; a theme may override them. In pre-release testing the plugin was checked with Twenty Twenty-Five (a block theme), Twenty Twenty-One (a classic theme) and Hype5 Stage.
• Hype5 Stage is a classic theme with theme.json. It works without Hype5 Theater; with the plugin active (0.6.17, Phase 5K build, including the navigation build documented here) it adds the theatre templates. See Hype5 Theater integration.
• The plugin's 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.

Editors and page builders #

• 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. They work in the Classic Editor, in a Shortcode block, and in page builders that render WordPress shortcodes. 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 sites #

Hype5 Theater supports WPML and Polylang (its multilingual rules are covered by automated tests; a run on live installations of both plugins is not recorded for this build). 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.

Multisite #

Network activation of Hype5 Theater is refused; activate it on each site separately. On multisite only super admins have the capability to edit custom CSS.

Browsers #

• Hype5 Theater's public output is rendered on the server as HTML; scripts add features such as the image viewer and the gallery carousel. Hype5 Stage was tested without JavaScript: content, navigation and the default colour scheme keep working.
• 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.
• Automated pre-release tests used Chromium (desktop, tablet and phone widths). Testing with other browsers, real phones and screen readers is still to be done; see Known limitations.

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.