Restricting editors to a specific translation?

Next topic

Author	Message
Luis Cruz	Friday 25 August 2006 10:11:15 am Greetings; I am running a multi-lingual setup of eZ consisting of English (US), English (UK), German, and Japanese. Each language is bound to a particular siteaccess by domain name (e.g., foo.de = German, foo.co.jp = Japanese) with English (US) being the default/fall-back language. Is it possible to limit editors in the CMS interface to be able to edit only a specific translation for a content object? For example, I setup a login for a German translator. I do want him to be able to alter the contents of the German translation but not be able to directly edit the other translations. The one problem I see is if the German translator needs to create a new object that has yet to be translated into English (US). For the record, I am running 3.6. Cheers.
Jeroen Sangers	Friday 25 August 2006 10:15:31 am You cannot limit your translators to only one language. If they have the right to edit content, they can do so in all languages. What you can do is create three different admin interfaces, each with another default language, but this does not block your translatord from editing other languages.
Kristof Coomans	Friday 25 August 2006 10:00:12 pm It's not possible with eZ 3.6, but it is possible with 3.8. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org

Author

Message

Friday 25 August 2006 10:11:15 am

Greetings; I am running a multi-lingual setup of eZ consisting of English (US), English (UK), German, and Japanese. Each language is bound to a particular siteaccess by domain name (e.g., foo.de = German, foo.co.jp = Japanese) with English (US) being the default/fall-back language.

Is it possible to limit editors in the CMS interface to be able to edit only a specific translation for a content object? For example, I setup a login for a German translator. I do want him to be able to alter the contents of the German translation but not be able to directly edit the other translations.

The one problem I see is if the German translator needs to create a new object that has yet to be translated into English (US). For the record, I am running 3.6.

Cheers.

Jeroen Sangers

Friday 25 August 2006 10:15:31 am

You cannot limit your translators to only one language. If they have the right to edit content, they can do so in all languages.

What you can do is create three different admin interfaces, each with another default language, but this does not block your translatord from editing other languages.

Kristof Coomans

Friday 25 August 2006 10:00:12 pm

It's not possible with eZ 3.6, but it is possible with 3.8.

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

eZ debug

Timing:	Jan 18 2025 20:56:35
Script start
Timing:	Jan 18 2025 20:56:35
Module start 'layout'
Timing:	Jan 18 2025 20:56:35
Module start 'content'
Timing:	Jan 18 2025 20:56:36
Module end 'content'
Timing:	Jan 18 2025 20:56:36
Script end

Main resources:

Total runtime	1.1101 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0078	588.0391	152.6406
Module start 'layout'	0.0078	0.0069	740.6797	39.4766
Module start 'content'	0.0147	1.0940	780.1563	570.8047
Module end 'content'	1.1087	0.0013	1,350.9609	12.1250
Script end	1.1100		1,363.0859

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0037	0.3330	16	0.0002
Check MTime	0.0015	0.1389	16	0.0001
Mysql Total
Database connection	0.0011	0.0978	1	0.0011
Mysqli_queries	1.0525	94.8171	59	0.0178
Looping result	0.0008	0.0727	57	0.0000
Template Total	1.0619	95.7	2	0.5309
Template load	0.0023	0.2044	2	0.0011
Template processing	1.0596	95.4543	2	0.5298
Template load and register function	0.0002	0.0188	1	0.0002
states
state_id_array	0.0015	0.1325	1	0.0015
state_identifier_array	0.0008	0.0695	2	0.0004
Override
Cache load	0.0018	0.1661	14	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0016	0.1485	3	0.0005
Fetch class attribute name	0.0012	0.1101	5	0.0002
XML
Image XML parsing	0.0035	0.3175	3	0.0012
class_abstraction
Instantiating content class attribute	0.0000	0.0010	5	0.0000
General
dbfile	0.0029	0.2618	22	0.0001
String conversion	0.0000	0.0010	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
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 10 Number of unique templates used: 5

Time used to render debug report: 0.0004 secs