Forums / Developer / Permimssions : content/translate Vs content/edit

Permimssions : content/translate Vs content/edit

Next topic

Author	Message
Nicolas Genty	Friday 19 January 2007 3:09:19 am Good morning, I might need some help: I seem to have a problem understanding the can_translate authorization My question is simple, but I really need to have it answered. How does the can_translate work ? I put it through a few tests, here they are : An user has the authorization content/edit but not content/translate : he may tedit the content in whichever language he feels like, hence he can translate I thought that content/translate was subsumed to the content/edit one, so I went on: An user has the authorization content/edit and content/translate upon a single class and a single language : but then again I have been able to edit the content in any language I then proceeded to remove the authorization and allowing the authorization to translate, so that I couldn't edit. But neither could I translate! So here is my question : what's the content/translate for? I must have been missing out on something. That leads us to a new problem (let's proceed step by step) How am I to grant the authorization to translate a content to a user without giving him the permission to edit the original content(the first translation) ? Thanks
Kristof Coomans	Monday 22 January 2007 2:25:01 am Hello Nicolas, welcome to the eZ community. Which version of eZ publish are you using? independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Sébastien Morel	Monday 22 January 2007 3:27:57 am Hi, Excuse, I create this topic with a different account ... So, I use the 3.9.0 ;) -- eZ c'est plus fort que toi ! http://www.ez-france.org http://blog.plopix.net @Novactive (http://www.novactive.com)
Kristof Coomans	Monday 22 January 2007 3:35:57 am I think the content/translate policy was used before eZ 3.8 to control access rights to the content/translate view. In 3.8 however improved multilingual features were introduced and you can now use content/edit to translate objects. Did you try not to use content/translate and only use content/edit with a limitation on the specific language(s) you want to allow translation to? independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Sébastien Morel	Monday 22 January 2007 3:50:33 am I want to allow translation on an objet which isn't mine. Ex: I'm french, I create a content in french. I have the content/edit permission in all languages. But, an another user, who's Italian wants to edit my content, he shouldn't edit the content in French because I am the author. But I wish that he can translate my content in another language (other than french)...He will be the traductor. This second user can too create his own content in french if he wants. I want to do a difference between the author, traductor and after moderator I havn't find a solution...excepts give at all all content/edit and manage the edit permission in the template (but isn't a good method I think, isn't is ?) PS: The content/translate is depreceated ? -- eZ c'est plus fort que toi ! http://www.ez-france.org http://blog.plopix.net @Novactive (http://www.novactive.com)
Kristof Coomans	Monday 22 January 2007 5:40:24 am Does it work when you use the following policies for the translator? content/edit, class(whatever), language(Italian) content/create, class(whatever) content/edit, class(whatever), owner(self) In case the language we allow to translate to has to be defined more dynamic (like: any other language than the original) then you have a problem. This is not possible at the moment. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Sébastien Morel	Monday 22 January 2007 6:28:09 am Ok, you confirm my thinks I must manage the permission in templates. I will give all permissions to edit; any langages on onwer and other. And I will manage in the template the permissions (with show/hide the edition button) Your solution is good and work but I havn't the choice, the permission must be more dynamic... :( eZpublish will be able to do that in the futur ? Thanks again -- eZ c'est plus fort que toi ! http://www.ez-france.org http://blog.plopix.net @Novactive (http://www.novactive.com)