A translation is missing

On a multilingual site, every menu item exists once per language. A missing translation is almost always a record that was never created, rather than text that was lost.

First: is the language actually enabled?

1. Confirm a translation layer is active on the site. Without one, Fenómenus publishes in the site language only and no translation controls appear.
2. Confirm the language itself is enabled. Languages are switched on during the setup assistant and can be managed afterwards in the translation layer's own settings.
3. Confirm the language appears in the public language switcher.

If the language is not enabled, nothing on the menu side will help.

The item exists in one language and not another

Open the source item. The translation panel lists each additional language with a title field and the translatable fields for that menu type.

• A language whose title field is empty has no translated item. Fenómenus only creates the translated record when a title is supplied — this is deliberate, so an accidental save does not fill the site with empty items.
• Fill in the title, complete the fields, and update the item. The translated record is created, linked to the source, and put in that language.

Some fields translate and others do not

This is by design. Two groups behave differently:

Translated per language — the title and the text fields the menu type declares: subtitle, description, long description, the recommended-wine description on the à la carte menu, and, on tasting and set menus, the block titles, block contents and the footer note.

Shared across languages — prices, allergens, categories, images and the menu order. A price or an allergen is a fact about the dish, not a piece of copy, so it is kept identical in every language rather than translated.

If you are trying to give one language a different price or a different order, that is not a missing translation: it is a deliberate limit.

The translated item exists but shows the source language

The record was created without its text being filled in — commonly because only the title was entered.

1. Open the source item.
2. Select the language in the translation panel.
3. Complete each field.
4. Update.

Where AI translation is available, the panel offers a translate action per language that fills those fields for review. Read the result before publishing; see Review a translation.

A category name is untranslated

Category names are separate records too. Translating the items does not translate their sections.

When an item is saved with translations, Fenómenus keeps the translated item pointing at the matching translated category, creating the link where it can. But the name a guest reads in that language still has to be written.

The menu is missing entirely in one language

1. Check whether the items were ever translated at all, or only some of them.
2. Check the item statuses. Publishing or unpublishing from All items applies to an item and all of its translations, so an unpublished source hides every language at once.
3. Check the language switcher configuration for that archive: the Language toggler is a per-menu-type setting under Content settings → Content settings.

The admin list only shows one language

That is intended. The All items and All categories screens work in the main language so the menu is maintained once, from one place. Translations are edited from inside the item, not as extra rows in the list.

The QR code opens the wrong language

The QR generator produces one code per language and labels each group. Regenerate the code group after confirming that the language is enabled and that its public menu URL resolves correctly.

Before asking for help

Note which language, which item, whether the translated title exists, and whether the source item is published. Those four facts identify the cause in nearly every case.