Open jensens opened 6 years ago
What would be the solution here @jensens? The user needs to create a content and select in the controlpanel which content is shown in the disclaimer instead of writing in a richtext field? And the implementation would check if there's a translation to the content and properly show the translation when appropriate?
We also could have a dicts of richtext fields with key as the langauge code in the controlpanele. I just don't know a widget for this.
So, I don't see a possibility to create a disclaimer per language.
Just a quick shot: Having a multilingual disclaimer is easier if the disclaimer itself is a full content object. Thus, we don’t need to reinvent the wheel in registry. Also, we could then display the (optional) 'full' disclaimer text there. And, the problem is solved for subsites (collective.lineage et al) too.
Opinions?
We can do this as an own addon as well, if this one here is meant to keep simple and lean.