How to translate Tickera plugin?
you want to translate the Tickera plugin into your language using the standard WordPress i18n workflow — and need to know which tool to use, where translations should live, and how to handle add-ons and the Checkinera apps.
The quick path: Loco Translate
The simplest way is the free Loco Translate plugin. Install and activate it from the WordPress plugin directory, then:
- Go to Loco Translate → Plugins.
- Find Tickera in the list, click it.
- Click New language.
- Pick your locale (e.g. Croatian (hr_HR), Spanish (es_ES), French (fr_FR)).
- Choose location Custom (so updates don’t overwrite your work).
- Click Start translating.
You get a side-by-side editor with the English source on one side and your translation on the other. Each save compiles the .po source into the .mo binary WordPress reads at runtime.
The deeper path: POEdit
If you prefer a desktop editor (faster keyboard navigation, offline work), use POEdit. Download Tickera’s .pot template file from /wp-content/plugins/tickera/languages/ on your server, open it in POEdit, save as tickera-{locale}.po, translate, save, then upload the resulting .po and .mo to /wp-content/languages/plugins/ (the WordPress global translations directory — not inside the plugin folder, which would be overwritten on updates).
Translating add-ons
Each Tickera add-on ships its own .pot file separately from the core. So translating Seating Charts, Bridge for WooCommerce, Custom Forms, etc. means one Loco Translate entry per add-on. Same workflow, just repeated.
Translating the Checkinera apps
The Checkinera mobile and web check-in apps are separate from the plugin — Loco Translate doesn’t touch them. For those, use the dedicated Check-in App Translation add-on which provides an admin UI for swapping app-side strings.
Setting your site’s language
For your translations to actually appear, your WordPress site language must match the locale you translated to. Go to Settings → General → Site Language and pick your language. Save. Reload your site — Tickera’s strings should now appear in your language.
Multilingual setups (WPML, Polylang, TranslatePress)
If you’re running a multilingual site where buyers can switch between languages on the fly, additional setup is needed — Tickera’s strings need to be registered with the multilingual plugin separately. See the dedicated fix: multilingual website content translated except Tickera.
Sharing your translation back
If you’ve translated Tickera into a language we don’t already ship, send us the .po file via our contact form with your locale in the message. We add contributed translations to future releases and credit translators in the changelog.
Related
- Translating Tickera (core docs)
- Multilingual website with content translated except Tickera
- Check-in App Translation add-on
Was this article helpful?
Yes — great. No or partially? Tell us what was missing — we read every message and use it to improve these docs.