how to specify additional language home

[breizhwave]

Hi followed the procedure for converting a site to multi site

works perfectly for all pages

but how do I specify the root page ? home page for the new language ? internal pages url work but not the home, I see you specify home page with id home but I suppose you can't use 2 home id ?

thanks for the answers

[joshuablum]

Hey Erwan!

If you're using a multi-site setup and you have localized entries the "home" page just stays that one entry. But only its origin entry has the id home and the localized ones just use a UUID. With the origin value you reference the id of the, well, origin entry which in this case is home (usually a UUID but home is special). If you switched from a single-site to a multi-site setup you may have to update that entry manually.

The YAML front-matter of your home entry should something like this:
Origin entry (e.g. English)

---
id: home
blueprint: pages
title: Home
template: default
---

Localized entry (e.g. German)

---
id: c6212a03-19fe-45c3-84ea-5b803db6ae0a
origin: home
---

More on that in the docs

Hope that helps! :)

[breizhwave]

Thanks @joshuablum that clarifies the origin attribute, but even though my localised page has homeorigin, I still get 404 on the /fr page, would statamic autoamtically assign home page to a page with home origin ? in my case it doesn't
statamic1/creek/content/collections/pages/fr/home.md

---
id: f8516624-b1f9-4afa-9ca6-087c6f68fff8
origin: home
updated_by: 0a77e13f-b3a9-4263-9364-fdf9432b0601
updated_at: 1652263183
---

here is my site config

    'sites' => [

        'default' => [
            'name' => config('app.name'),
            'locale' => 'en_US',
            'url' => '/',
        ],

        'fr' => [
            'name' => 'fr',
            'locale' => 'fr_FR',
            'url' => '/fr/',
        ],



    ],
];

[joshuablum]

Mhm, your sites config looks correct 🤔

Can you also share the front-matter of the origin?

Just to make sure: Is your home entry's state for the fr locale published? Depending on the collection's configuration they don't get published by default. It's something I have overlooked myself a couple of times. Should look similar to this:

[breizhwave]

thnks, the issue here is that it is published but has a parent. When I unlink and save, parent comes back.. .this is weird behaviour, might start all from scratch. When I rename home slug to smthing else, does not alter home behaviour...