Multilanguage fallback revisited and a page footer with multilanguage links
Keep the translated title and slug in one place and mark them valid so they can be used even if the remainder of the item is not valid.
Before you read on, you may want to read my previous post about language fallback, see link below. Here you have an example of the complexity of multilanguage. The link should be shown in the language you are using at the moment ... another time.
I started with two tables and created a new part of the administrator to manage them:
Using the administrator I create a footer item and add one or more language records to it, for every language a translation record is added. My first thought was to specify the name and slug for a page here, I mean, a page may not be available in the selected language and we want to fallback to the fallback language. The translated link name (page title) and slug must be stored somewhere.
However, when building the query to select the pages I found this far too complex because now I not only had to query the content_item and content_item tables but also the footer_item and footer_item_translation table. Not exactly what I had in mind, I am a programmer and prefer KISS.
My solution to reduce complexity is to abuse the content_item_translation record again, the last time I added the 'do_not_fallback' flag and now I add another flag: 'can_use_slug'. The meaning is as follows:
- When the content_item_translation record does not exist, we fallback to the fallback language.
- When the content_item_translation record exists and is published, we use it.
- When the content_item_translation record exists but is not published we have two conditions:
- do_not_fallback, if True, the item is not available.
- can_use_slug, if do_not_fallback is False, and can_use_slug is True we can use the title and slug of the content_item_translation record.
The nice thing is that we now can build a true multilanguage footer, with multilanguage links even if the page is not published, only by translating and adding the page title and slug to the content_item_translation record and setting the can_use_slug flag. The title and slug of the page are only in one place.
Implementation is like the cache object and settings object described in previous posts and of course uses caching, no need to generate the footer every request. No code in this post, must do some cleanup first ...
Links / credits
Refining multilanguage: adding language fallback as an option
- Adding url_for() links to Jinja templates of a Flask multilanguage website
- Docker containers suddenly using 192.168.0.0/16 instead of 172.17.0.0/16: services lost
- Two Flask apps, frontend and admin, on one domain using DispatcherMiddleware
- ISPConfig: running a Python Flask Docker container as a jailed Shell User
- Developing Ubuntu Touch apps with Python using pyOtherSide
- Refining multilanguage: adding language fallback as an option