Translatable Site.name

James Pic

unread,

Jul 19, 2016, 6:43:35 PM7/19/16

to django-d...@googlegroups.com

Hi all,

Are there any plans to make Site.name translatable ?

Would that be something we want to offer as a feature ?

Thanks

Shai Berger

unread,

Jul 19, 2016, 7:11:03 PM7/19/16

to django-d...@googlegroups.com

On Wednesday 20 July 2016 01:43:05 James Pic wrote:
> Hi all,
>
> Are there any plans to make Site.name translatable ?
>

Site.name is a model field.

Translatable models are a big hairy issue. Several solutions have been
suggested, each with its own pros and cons. Last time I looked (several years
ago), we were not at the stage where we could bless one of them.

> Would that be something we want to offer as a feature ?
>

Site.name as a single, special-cased translatable field? I don't believe so.

Shai.

Tim Graham

unread,

Jul 19, 2016, 10:06:24 PM7/19/16

to Django developers (Contributions to Django itself)

If we were able to switch to declaring sites as settings rather than as models as described in https://groups.google.com/d/topic/django-developers/OGOf1TfSBBs/discussion, I believe it would be more feasible.

James Pic

unread,

Jul 20, 2016, 3:59:06 AM7/20/16

to django-d...@googlegroups.com

Thanks, I'm really looking for a way to use the models as this is for the django CMS light project which makes dynamic multi site a central requirement.

Perhaps we could make this model swappable ?

For now I'm just going to rely on the translatable site level yaml metadata we already have in place for the page title and that'll fix the problem for me.