Translation - interface for translators

Next topic

Author	Message
Simon Phillips	Sunday 13 February 2005 4:47:14 am Hi, I've got my site running in three languages, using the siteaccess methods mentioned in the documentation. So far, I've posted the english (primary language) versions, and added the translations I have using the method described at http://www.ez.no/ez_publish/documentation/day_to_day_use/translate_content I'd like to be able to give certain users the ability to translate documents (and possibly only documents in certain sections), but that's all I want them to do - I don't want them to have access to the rest of the admin interface, or to create their own content (ideally). How can I do this? I presume I need to create some templates that identify if they're a translator or not, and then give them the 'manage translations' stuff if so. I've tried adding a translator user with the content/translate permissions, but since they don't have admin rights, they can't access the admin interface and do it that way. Is there an easy solution? I can't believe I'm the only one needing this. Apologies if I've missed something; I have been trawling the forums and documentation for the past few hours on this one! Thanks in advance, Simon
Simon Phillips	Sunday 13 February 2005 9:12:11 am OK, I can now get the translator user to log in (for some other reason, despite being configured in the site.ini file, the PolicyOmitList[] settings weren't effective. Having added the user permission explicitly to my Translator role, they can now log in to the admin section). PolicyOmitList[]=user/login PolicyOmitList[]=user/logout My question now is - what are the minimum permissions required to be able to translate? I can't find any documentation describing what the various permission levels and modules actually do from a user perspective. Having granted only content/read and content/translate, I can't get to the translate panel. I guess that means I have to grant content/edit as well? This is not exactly ideal - I'd rather they couldn't edit the original primary text. Any other suggestions? Thanks, Simon

Author

Message

Sunday 13 February 2005 4:47:14 am

Hi,

I've got my site running in three languages, using the siteaccess methods mentioned in the documentation. So far, I've posted the english (primary language) versions, and added the translations I have using the method described at http://www.ez.no/ez_publish/documentation/day_to_day_use/translate_content

I'd like to be able to give certain users the ability to translate documents (and possibly only documents in certain sections), but that's all I want them to do - I don't want them to have access to the rest of the admin interface, or to create their own content (ideally). How can I do this? I presume I need to create some templates that identify if they're a translator or not, and then give them the 'manage translations' stuff if so.

I've tried adding a translator user with the content/translate permissions, but since they don't have admin rights, they can't access the admin interface and do it that way.

Is there an easy solution? I can't believe I'm the only one needing this. Apologies if I've missed something; I have been trawling the forums and documentation for the past few hours on this one!

Thanks in advance,
Simon

Simon Phillips

Sunday 13 February 2005 9:12:11 am

OK,

I can now get the translator user to log in (for some other reason, despite being configured in the site.ini file, the PolicyOmitList[] settings weren't effective. Having added the user permission explicitly to my Translator role, they can now log in to the admin section).

PolicyOmitList[]=user/login
PolicyOmitList[]=user/logout

My question now is - what are the minimum permissions required to be able to translate? I can't find any documentation describing what the various permission levels and modules actually do from a user perspective. Having granted only content/read and content/translate, I can't get to the translate panel. I guess that means I have to grant content/edit as well? This is not exactly ideal - I'd rather they couldn't edit the original primary text.

Any other suggestions?

Thanks,
Simon