Tickera
Get Tickera

I am using multilingual website and all the content is translated except Tickera

FAQ & Troubleshooting · 2 min read · Updated May 21, 2026

you run a multilingual WordPress site (WPML, Polylang, TranslatePress, qTranslate) and every plugin’s content is translated except Tickera — and you want to know why and how to fix it.

The honest answer

Tickera doesn’t have native support for displaying multiple languages on the same WordPress installation. The plugin can be translated to any one language at a time via the standard WordPress i18n workflow, but it isn’t built to switch languages on the fly per visitor like multilingual plugins do.

So when a buyer flips your site to French via WPML, Tickera’s strings still appear in whatever language you set as the site default.

Two paths forward

Option 1: pick a single language for Tickera

For the vast majority of organizers, the simplest answer: translate Tickera once into your dominant audience’s language using Loco Translate or POEdit. Set your WordPress Site Language to match. The rest of your site can still be multilingual via WPML/Polylang — only Tickera’s specific strings stay in your dominant language.

Option 2: run separate WordPress installations per language

If you need full multilingual Tickera (each language with its own properly-translated Tickera strings, ticket templates, etc.), use WordPress Multisite — one subsite per language, each with Tickera installed in that language. More work but clean separation. See the multi-organizer / Multisite guide for the architecture.

What you CAN do with WPML / Polylang / TranslatePress

Even though Tickera doesn’t multilingual-switch its own strings, multilingual plugins CAN still translate:

  • The event post content (title, description) — these are normal WordPress posts.
  • Custom Forms field labels (if you set them up multilingual-aware).
  • Your theme’s surrounding content (header, footer, sidebar).

So a buyer flipping to French will see your event title, description and surrounding site in French — but the Tickera-specific UI strings (cart, checkout button, ticket-type labels) stay in your site default language.

What you CAN’T currently do

  • Switch Tickera UI labels per-visitor based on language preference.
  • Have separate ticket templates per language on the same site.
  • Send order confirmation emails in different languages based on buyer locale (without significant custom code).

Checkinera app translations are separate

The mobile and web check-in apps are translated via the dedicated Check-in App Translation add-on — independent of WPML/Polylang on the website. You pick the language for each Checkinera install.

Related

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.

Keep going

More from the
Tickera docs.

Browse all docs Every article, organized by topic The add-on catalog 25 official add-ons, all included with Bundle See Tickera pricing 0% commission, forever. Three plans. Talk to support Real humans, business-day response