Appearance
Multi-language events
Run one event, reach attendees in their own language. BagEvent does this with language versions: additional copies of your event that share its tickets, inventory, dates, and schedule but carry their own translated text. Attendees see the public page — and receive their transactional emails — in the matching language, while you keep managing a single set of tickets and stock behind the scenes.
How language versions work
Every event is either a main event or a language version of one.
- The main event (the parent) owns the real commerce: the ticket types, their prices and inventory, the sale windows, the schedule, and the dates.
- A language version is a child of that main event. It exists to present the same event in another language. It reuses the main event's tickets, inventory, and schedule and lets you translate the text that attendees read.
Because a version is a child, it is not something you run independently. Its tickets and inventory are read-only — you edit them once, on the main event, and every language version reflects the change. What you edit on the version is translation: the event title and content, and the display names of tickets and form fields.
Why not just copy the event?
A separate copy would have its own stock, so selling three seats on the English page and three on the Chinese page could oversell a six-seat room. Language versions share one inventory pool, so the seat count is always correct no matter which language a buyer used.
Each language version has its own public URL and its own draft/published status. Translating the text does not publish it — you publish each version when its translation is ready, just as you publish the main event.
Supported languages
BagEvent supports three languages platform-wide. English is always the default.
| Language | Code | Notes |
|---|---|---|
| English | en_US | Platform default. Any unmatched locale falls back to English. |
| Simplified Chinese (简体中文) | zh_CN | Used for mainland China and other Simplified locales. |
| Traditional Chinese (繁體中文) | zh_TW | Used for Taiwan, Hong Kong, and Macau (any Traditional / Hant locale). |
Locale strings are normalized, so regional variants map to the right language automatically: zh, zh-CN, and zh_CN all become Simplified; zh-TW, zh-HK, zh-MO, and anything marked Hant become Traditional; anything else, including any English variant, resolves to English.
Adding a language version
You add a language version from the main event, and you pick a language different from the main event's own.
- Open the main event (the one whose language you want to translate from). You can only add versions to a main event — a language version cannot itself have children.
- Find the languages / language versions section of the event.
- Choose Add language version and pick a target language. It must differ from the main event's language, and you can have only one version per language.
- Optionally set a title for the new version now; if you leave it blank, it starts as a copy of the main event's title for you to translate.
- Save. BagEvent creates the version as a draft and seeds it from the main event so you have a complete starting point to translate.
When the version is created it inherits the main event's dates, time zone, currency, location, logo, page content, registration settings, and a translatable copy of every ticket and form field. At first those copies simply repeat the main event's text — that is your starting point, not the finished translation.
WARNING
Two things are enforced when you add a version:
- Pick a different language. You can't add a version in the same language as the main event.
- One version per language. If a version already exists for that language, add your translation to the existing one instead of creating another.
Translating the content
After the version exists, work through its text:
- Event details — translate the title, summary, and page content on the version.
- Ticket labels — translate each ticket's name and description. The price, inventory, sale window, and identity come from the main event and can't be changed here.
- Form fields — translate each field's label, help text, and any option choices. The field's key, type, and whether it's required are shared from the main event.
Keep translating on the main event's terms
If you add a new ticket or a new form field later, add it on the main event. BagEvent automatically creates a matching translatable entry in every existing language version, so nothing silently goes missing — you just fill in the translation.
What is shared vs. translated
| Aspect | Where it's managed | On a language version |
|---|---|---|
| Ticket types | Main event | Read-only |
| Prices & currency | Main event | Read-only |
| Inventory / stock | Main event (one shared pool) | Read-only |
| Sale windows | Main event | Read-only |
| Schedule / agenda | Main event | Read-only |
| Event dates & time zone | Main event | Read-only |
| Registration settings (mode, per-attendee, TTLs) | Main event | Inherited |
| Ticket name & description | Per version | Translated |
| Form field label, help text, options | Per version | Translated |
| Event title, summary, page content | Per version | Translated |
| Public URL & publish status | Per version | Independent |
The rule of thumb: anything that involves money, stock, or timing lives on the main event; anything an attendee reads is translated per version. If you try to edit commerce on a version, BagEvent will stop you and point you back to the main event.
Edit tickets on the main event, not the language version
To change a price, add stock, open or close a sale window, or add a ticket type, go to the main event. Those edits apply to every language at once. On a language version you can only translate the ticket's display text.
The public page and emails per language
Once a language version is published, it has its own public event page, shown entirely in that language — the layout comes from the main event, the words come from your translation, and prices and dates render using that locale's formatting.
Transactional emails follow the same rule. When someone registers through a given language version, the confirmation and other attendee-facing emails are sent in that version's language. Buyers who register on the English page get English mail; buyers on the 繁體中文 page get Traditional Chinese mail. You maintain one event and one inventory, and each attendee's experience — page and inbox — stays in the language they chose.
TIP
Because inventory is shared, your Attendees and Orders lists show everyone together regardless of which language page they used. There is one guest list, one stock pool, one event — just several front doors.
Related
- Key concepts — main event vs. language version, and the object model.
- Creating events — set up the main event first.
- Tickets & inventory — where prices and stock are managed.
- Registration forms — the fields you translate per version.
- Quick start
- FAQ