Multi-level localization fallback

[marklonquist]

Hi

Having a deeper fallback structure for localization can in some cases make the job of a content editor a lot easier.

Structure example:

• en
• de
  • fallback: en
• de-de
  • fallback: de
• de-at
  • fallback: de

so, in this case, if the value is not filled on de-de, we take the value from de.
If that's not filled, we fallback to en which - hopefully - is present.

[DanRibbens]

I like this idea and it would fit nicely into the config where we have extended the locales to be objects instead of an array of strings to support additional properties. That work is on the feat/rtl-support branch.

After that gets merged, we could add fallbackLocale and extend the fallback logic to work perfectly.

[marklonquist]

Any update on this feature? We can't really change to using payload before we have this :)

[DanRibbens]

The LTR PR is slated for our 2.0 changes which is complicating things a little as we work towards a larger release. I can't give an exact timeline, but you should know we are in the weeds with some very exciting changes coming!

[marklonquist]

Thank you for the update :)

[marklonquist]

We are not in a rush to change. Our current platform works, but payload is much faster :)

[marklonquist]

having installed 2.0 now, I can see this is still not available 😭

[marklonquist]

@DanRibbens any info to share? :)

[DanRibbens]

It didn't make it into 2.0 with all the other changes we had to prioritize. This is still high on my list after we clean up our issues.

[marklonquist]

Cool. Thanks for the update.

It’s a vital part on how we use a CMS so we need it before we can make the transition to payload. :-)

So really looking forward to this feature.

[marklonquist]

@DanRibbens any progress on this? :)

[marklonquist]

It seems this was PARTIALLY implemented.

It's now possible to set a localized fallback, but if that fallback does not have any data, it doesn't seem to use the fallbacks fallback langauage, eg.:

• en
• de
  • fallback: en
• de-de
  • fallback: de
• de-at
  • fallback: de

Let's say we have a tittle field. On de-de it's not set, so it fallbacks to de, but on de it's also not set, so the value currently returns as empty. But I would think it should return the value of en, as de fallbacks to that language.

[marklonquist]

@DanRibbens sorry to ping you again, but is this in your plans to make? :)

[DanRibbens]

Your understanding is correct on the current way fallbacks are working. I am unsure if we will be able to achieve fallbacks more than one extra language.

I would also be concerned with introducing circular dependency issues if we made this any more complex.

[marklonquist]

Your understanding is correct on the current way fallbacks are working. I am unsure if we will be able to achieve fallbacks more than one extra language.

I would also be concerned with introducing circular dependency issues if we made this any more complex.

That sounds weird though, as other CMS' support this.

Can you point me in the right direction if I were to make this change myself?

[marklonquist]

Nevermind - our ecom team do not need more than what is already provided. Closing this and thanks! 😄