Skip to content
You are reading the docs for ShopClass 6.4.1, still in development. Read the stable docs.

Languages

ShopClass is multilingual throughout: categories, static pages, custom fields and e-mail templates all carry a value per active language.

Settings → Languages.

Add language installs from the official translations. What is available comes from mindstellar/shopclass-i18n, which is where translations are maintained and where you contribute a fix.

If the language you want is not offered (the screen says no official languages available when it cannot reach the list), you can upload a translation file directly.

Each language has two separate switches:

  • Enabled (website): visitors can see the site in this language.
  • Enabled (oc-admin): admins can use the admin panel in this language.

Turn one on without the other to prepare a language before showing it to visitors, or to give your team an admin language your visitors don’t have.

The default language is set in Settings → General. It is what visitors see before they choose, and what content falls back to.

Installing a language translates the interface. Your own content is not translated by anyone but you:

Content Where
Category names Listings → Categories: one name per active language
Static pages Pages: title and body per language
Field and form labels Forms: the admin requires a name for the default language
E-mail templates Settings → Email templates: per language

Each active language multiplies the content you maintain: every new category and every new page needs another translation, forever.

Two languages done properly beat five done half-way. On a local marketplace, one language done well usually beats both.

Translations live in shopclass-i18n. Fixing an awkward string in a language you speak takes minutes, and is one of the most useful contributions to the project: see contributing.