everjust-website-i18n

Activate the res.lang record with a plain update setting active:true, then add it to the website's language_ids using the m2m command [[4, lang_id]]. Both steps are required: activation alone does not expose the language in the selector or create /<url_code>/ URLs.

Call update_field_translations with confirm:true on the page's view record. For arch_db pass {lang: {source_term: translated_term}} keyed by exact English terms; for meta fields like website_meta_title pass {lang: new_value}. Generic update tools only write the en_US source.

Either the language is not in website.language_ids, so /fr/ does not resolve, or the terms have no translation and fall back to the en_US source. Check language_ids first, then read get_field_translations to find untranslated terms and translate them.

No. The generic update, create, and website_edit_page tools run write() with no lang context, so every value lands in the en_US JSONB source slot. Non-English values can only be written through call update_field_translations with confirm:true.

Odoo raises a UserError when deactivating a res.lang still referenced by any website's language_ids. Remove it from language_ids first with the m2m unlink command [[3, id]], then set active:false on the res.lang record.

No. Odoo 19 stores translations as JSONB keyed by language code on each translatable field, with en_US as the source and fallback. You translate terms on the existing page or view record rather than creating per-language page copies.