Updating and troubleshooting

Before any update #

1. Back up the database and the wp-content folder.
2. Read the product's entry in the changelogs and the compatibility matrix.
3. If you use both products, check that the new versions are listed as compatible with each other.

Updating Hype5 Theater #

The plugin declares the Hype5 update service as its update source. When a new version is published there, it appears on the WordPress Plugins and Dashboard → Updates screens like any other plugin update. The plugin asks the update service for the stable channel only, so a pre-release (beta) version is never offered automatically; it is installed by uploading its ZIP.

You can also update manually: upload the new ZIP in Plugins → Add New Plugin → Upload Plugin and confirm that WordPress should replace the installed version.

After an update:

• Database changes required by the new version run automatically on the next admin page load by a user with the manage_options capability (normally an administrator). A migration is marked complete only when every step has succeeded; otherwise administrators see Hype5 Theater database setup is incomplete and it is retried.
• Capabilities are checked in the same way: an update adds only capabilities that are new in that version (Theater 0.7.0 and later). Capabilities you removed from Administrator or Theater Manager, or denied, stay as you set them, and a deleted Theater Manager role is not recreated. See When the role is created.
• Open Hype5 Theater → Settings → Advanced (or Continue in WordPress: System status there): check the plugin and database versions, and that every table is Ready.
• If your theme overrides plugin templates, System Status reports each override as Current, Review recommended (outdated) or Missing or malformed version. Compare outdated overrides with the new plugin templates. See Template overrides.

From 0.6.17 to 0.7.0 #

Hype5 Theater 0.7.0 is a beta by invitation and has not been published: the update service does not offer it. What follows applies when you install its ZIP over 0.6.17 — today only on invited sites — and to later published versions.

• No data migration. The database schema stays at version 5; no table, post or setting is changed. The update writes one new option, hype5t_caps_granted (the record of the capabilities the plugin has granted), on the first admin page load by a user with manage_options, and gives no capability back that you removed.
• The Hype5 app opens for everyone with a Hype5 Theater administration permission. The 0.6 access list is no longer read (it stays stored, unused). Users who had the classic menu because they were not on the list — or because their only Hype5 permission was Settings or Vocabularies — now get the single Hype5 Theater entry that opens the app. As a technical fallback (for example while diagnosing a problem), define('HYPE5_THEATER_FUAJEE', false); in wp-config.php switches the app off for everyone. See The Hype5 app.
• Public pages of password-protected productions behave more strictly on pages other than the production's own page, in feeds, archives, search and REST answers. See Security and content visibility.
• Hype5 Stage needs version 1.0.2 with Theater 0.7.0 (see below).

Updating Hype5 Stage #

Hype5 Stage 1.0.2 has no automatic update channel. Update it manually:

1. Go to Appearance → Themes → Add New Theme → Upload Theme.
2. Upload the new ZIP and confirm that WordPress should replace the installed theme.
3. Your Stage settings are stored as theme modifications and are kept.

Moving both products to the documented versions #

Hype5 Stage 1.0.2 is the Stage version tested with Hype5 Theater 0.7.0, and the minimum Stage version for it; Stage 1.0.1 should not be used with Theater 0.7.0 or the 0.6.17 Phase 5K builds (see Known limitations). If you update both, we recommend updating Stage first, ideally in the same maintenance window. Stage 1.0.2 works with the plugin's Phase 5K builds and with 0.7.0; with an earlier 0.6.17 build of the plugin it switches its theatre templates off and runs as a plain theme (the theme's tests checked that pages still load without errors), so for that short time the plugin presents productions with its own templates. Once the plugin is updated, Stage's theatre templates switch on again. Updating the plugin first instead leaves Stage 1.0.1 running with Theater 0.7.0 until Stage is updated. This order is a recommendation; it has not been rehearsed as a combined procedure.

If a Hype5 Theater update changes a template contract to a new major version, Stage automatically uses the plugin's own template for that part instead of its override until Stage is updated. Other changes in the plugin are caught so that a failing home-page section is left out rather than breaking the page — but test Stage after every Theater update. See Hype5 Theater integration.

If something goes wrong #

More answers: Troubleshooting and Frequently asked questions.

Rolling back #

To return to an earlier version, restore your backup, or install the earlier ZIP over the current one (Upload Plugin, then Replace current with uploaded). Hype5 Theater's database changes are designed to keep existing data, but an older plugin version may not understand data written by a newer one — restoring the database backup taken before the update is the safe way back.

Hype5 Theater 0.7.0 has the same database schema (5) as 0.6.17, so installing the 0.6.17 ZIP over 0.7.0 changes no data. Two consequences to plan for:

• A 0.6.x version uses its access list for the Hype5 app again: users who are not on that list get the classic Hype5 Theater menu.