Translation and localisation

Administration language #

The plugin's source language is English, and it includes a complete Estonian translation (text domain hype5-theater). Each user sees the administration — the classic screens and the Hype5 app — in their own WordPress language (Users → Profile → Language). Languages other than English and Estonian fall back to English. There is no separate British or American translation: a site or user set to English (UK) or English (United States) sees the plugin's English source texts, while WordPress's own screens follow that variant. The product name is always written Hype5 Theater.

The Estonian terminology is still awaiting a native-speaker review before release, so some Estonian labels may change.

Public texts (labels) #

Headings, button texts, filter names, status words and the names of built-in option-list entries on the public site are labels. Each has a translated default, and you can override it per language:

• Hype5 app: Appearance → Text (Tekst) edits the texts of the site language. Empty fields use the default text.
• Where the app is switched off: the classic Appearance → Text & Labels screen.

For example, change Cast to Dancers for a dance company. Overrides are limited to 500 characters each. Content you enter — production texts, ticket-offer names, your own option-list names, article titles — is never a label; translate it as content. See Labels.

Dates, times and time zones #

• Performance dates and times in the plugin's public output and in the Hype5 app's schedule and lists use WordPress's date format, time format, first day of the week and the user's month and weekday names (Settings → General). For example, with the date format j F Y and the time format H:i a performance reads 22 October 2026 19:30; with d.m.Y the same performance reads 22.10.2026 19:30. The stored performance does not change.
• Exceptions: date fields in the Hype5 app's forms (premiere, birth date, article date, scheduled publishing) are the browser's own date inputs and show the browser's date format; the Overview's short dates and the Schedule's day headings use fixed short forms of the user's language (for example 22.10. and October 22 in English — there is no separate British form); the Appearance studio's schedule sample has a fixed example date; and a theme can use its own formats — Hype5 Stage, for example, writes dates such as Thu 22 Oct.
• The site time zone decides which day a performance falls on in lists and filters, and is the default time zone of new performances.
• Each performance stores its start as a fixed instant with its own time zone, so tours can cross time zones. Lists show each performance's own local time, and its zone when it differs from the site's.
• A time that does not exist because clocks go forward is refused; a time that occurs twice when clocks go back is explained before saving.

See Schedule and performances.

Multilingual sites (Polylang, WPML) #

Hype5 Theater reads translations from Polylang and WPML. For 0.7.0 the real Polylang 3.9.0 plugin was tested; WPML was not installed in testing (its interfaces were only simulated), so WPML is not a supported integration for 0.7.0. See Compatibility. The original-language post of a production, person or venue owns the facts that are the same in every language; translations carry their own texts.

In the editors, shared data is read-only on a translation, with a link to the original. Edit credits, performances and rows on the original-language production.

On the website:

• names and links are shown in the reader's language when that translation is published; otherwise the original is shown;
• a draft, pending, scheduled or private translation is never shown to visitors;
• a password on any language version protects the shared data shown on that version, and a production appears on other pages (lists, profiles, the general schedule, productions embedded in another page) only while no version shown carries a password, also after a visitor has entered it;
• each version's own password opens its own page, including its dates and offers (Theater 0.7.0); a draft version's password never opens the original. WordPress remembers one entered password per visitor, so use the same password on every language version;
• a published translation of an unpublished original shows only its title, address and poster to visitors, also in feeds, REST answers and search;
• visitors who are not logged in do not find any version of a password-protected production in WordPress's search;
• the productions list's next order and city filter, and schedule counts, use only productions public to everyone.

See Security and content visibility.

Permalink bases are registered once per type. For separate bases per language, use a translation plugin that translates the registered slugs (Polylang Pro or WPML; neither was tested with 0.7.0). Settings → Language and time in the Hype5 app shows the detected translation plugin.

Developer details, including what the plugin's wpml-config.xml copies to new translations: Multilingual sites.