View more context

 

wmk

@tractorcow good to see! Thanks for improving fluent. I had a customer where I added fluent to an existing site and I thought it's not always clear for him if he's in the main language or in the translation.

tractorcow

Maybe we need to show the failovers "you are viewing the page in <locale> This page fails over from <locale1> if not localised This page fails over to <locale2, locale3> if they are not localised"

tractorcow

I'm thinking of pulling some of the advanced features into a separate tab; It might be easier to see a table that displays the status of the current record in each locale, along with some kind of batch action system

(2) (1)
taoceanz

It's not possible to translate SiteTree ParentID is it? Have just run into an issue of 2 pages using Translatable to be linked while in different Locale but, they have different parent pages. My guess is an Admin user created the translation page then dragged that translated page under a different parent page.

taoceanz

Looks like the pages that sit under a different parent page have been moved accidentally by someone so should just need to restore pages to the correct parent pages before running task to migrate from translatable to fluent.

nightjarnz

Fluent doesn't keep translations as separate pages, the ID should be the same for all translations for a page (and the the ParentID on any child).

nightjarnz

Translatable on the other hand was essentially subsites, but for languages.

nightjarnz

I'm not 100% sure, but I don't think that's possible with Fluent.

tractorcow

@taoceanz actually, you can add ParentID to the localised list of fields ; However, I have no idea what you would break, and I would strongly recommend you don't try it. 🙂

tractorcow

I would probably recommend subsites if you want separate trees