[support] Domain Access + i18n

David T david.hart at gmail.com
Sat Mar 20 01:43:30 UTC 2010


Does anybody have any suggestions for my problem. I have a website
translated into a number of languages, which exists on separate
websites using Domain Access. So:

example.co.uk is the "original" in English
example.de has the German translation
example.fr the French translation etc.

To translate a page, you can either click on the Translate tab on
example.co.uk/foo or use the translation table on
admin/content/translation_overview. This, however ONLY works if you
have the "administer nodes" permission. Without it, if you're on
example.co.uk you can't see the existing German translation nor on
example.de can you see that example.de/foo is a translation of
example.co.uk/foo. This is presumably because without this permission,
the user on example.co.uk is unable to see that the translated node on
example.de exists as it's not been published on example.co.uk.

This has utterly kippered me, as now my translators would need a high
level of permission to successfully translate any new pages. Any
suggestions?

I had thought to see if I could use Rules to add an additional role to
translators only when on specific pages (either translation_overview
or a custom view) and remove it on all other pages but this doesn't
seem to work as Rules doesn't appear to trigger actions when you're on
an admin page - or at least I can't work out a condition that would
trigger an action on either admin/content/translation_overview or on a
page that is a view. This way also seems a bit of an insane solution,
but I'm pulling my hair out trying to work this out.

The only other solution I can think of is to publish all English
content to the subsites, but that also has a number of major problems,
not least of which it enables people to edit the original English
translation.


More information about the support mailing list