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

eZ debug

Timing:	Jan 31 2025 05:33:13
Script start
Timing:	Jan 31 2025 05:33:13
Module start 'layout'
Timing:	Jan 31 2025 05:33:13
Module start 'content'
Timing:	Jan 31 2025 05:33:14
Module end 'content'
Timing:	Jan 31 2025 05:33:14
Script end

Main resources:

Total runtime	0.9269 sec
Peak memory usage	4,096.0000 KB
Database Queries	52

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0053	588.2500	151.2266
Module start 'layout'	0.0053	0.0029	739.4766	36.6797
Module start 'content'	0.0082	0.9179	776.1563	852.2031
Module end 'content'	0.9262	0.0007	1,628.3594	7.8281
Script end	0.9269		1,636.1875

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.3692	16	0.0002
Check MTime	0.0014	0.1494	16	0.0001
Mysql Total
Database connection	0.0007	0.0725	1	0.0007
Mysqli_queries	0.8814	95.0981	52	0.0170
Looping result	0.0005	0.0535	50	0.0000
Template Total	0.8944	96.5	2	0.4472
Template load	0.0019	0.2080	2	0.0010
Template processing	0.8924	96.2820	2	0.4462
Template load and register function	0.0014	0.1462	1	0.0014
states
state_id_array	0.0011	0.1236	1	0.0011
state_identifier_array	0.0011	0.1177	2	0.0005
Override
Cache load	0.0016	0.1724	18	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0527	1	0.0005
Fetch class attribute name	0.0027	0.2962	2	0.0014
XML
Image XML parsing	0.0001	0.0108	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0010	2	0.0000
General
dbfile	0.0016	0.1743	10	0.0002
String conversion	0.0000	0.0008	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 12 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs