Skip to main content

Languages

Fixed source defines Settings → All settings → Pro → Languages as a returned-language control surface distinct from Language manager; no current project state is claimed here.

Languages settings with Field, Default, and Status controls

Current source mechanics​

The current component maps the returned language list into three columns:

  • Field — the language name.
  • Default — an enabled row exposes a radio action. Selecting a different row immediately invokes the language-item save path with { default: true }, updates local language state, and reloads the page after the request path returns.
  • Status — its switch immediately invokes the language-item save path with { enabled: value }; the current UI language row disables this switch.

There is no page-level Save or batch transaction for these controls. No language record or translated content was read or changed and no reload was triggered for this guide.

The historical screenshot/project evidence showed English, German, Spanish, Danish, Dutch, Portuguese, French, Turkish, Arabic, Italian, Greek, Bulgarian, and Ukrainian. That list is fixture/runtime evidence, not a source-defined catalogue or a claim about a current project.

Language manager is a separate translation-record surface. This Pro category exposes enabled/default language record controls; fixed source does not establish that changing them translates Business, menu, product, or storefront content.

Immediate writes

Both controls cross an authenticated write boundary immediately. Route/controller presence does not prove deployed authorization, persistence, reload outcome, translated-content availability, or storefront effect.

Source-only boundaries​

  • The literal route is /all-settings?category=languages, exposed in the Pro menu only when the Pro group is available.
  • Fixed API source declares language collection/item routes, including update, but no API or runtime call ran; GET/HEAD are not presumed safe.
  • Language values, translations, enabled/default state, writes, reloads, and downstream localized content remain excluded.
  • Re-entry requires an immutable serving receipt and a synthetic language fixture with item writes and reload behavior intercepted.

Related guides: Language manager · Pro settings