Allow global enabling of one mode of translation or another [#1455638]

I think it's likely that sites will choose to use entirely one mode of translation or another (though some sites may actually require both). An administrative option (perhaps on the content type form or on the webform settings at admin/config/content/webform) would be helpful to shift that decision to the administrator rather than troubling editors and content creators with it. Or do you think that using both at the same time is common enough that users should always be presented with both options?

Comments

Comment #1

GDrupal commented 28 February 2012 at 22:00

Assigned:	Unassigned	» GDrupal
Status:	Active	» Needs review

mmmm this is hard to tell right now... my first thought is to let people to guide the development on this subjects, i will prefer to wait until them begin to use and the common scenario emerges. What you do think about wait for a while?

Comment #2

rv0 commented 13 March 2012 at 09:25

Ideally:
For each webform enabled content type, you could have the option to make a global setting or allow per-node setting

Comment #3

GDrupal commented 13 March 2012 at 14:42

@rv0: Right now you have per webform settings so you can choose a different way of translation for each webform that I think is very interesting. In fact, right now you can mix the both methods if you need it. I do not see right now a scenario when you will need both features at the same time but is allowed.

Comment #4

star-szr

he/him

English

commented 14 January 2013 at 18:29

Version:

» 7.x-1.x-dev

I would really like to see this, I may work on a patch for this if time permits. @GDrupal, can you please explain the 7.x-1.x and 7.x-4.x branches? So far I've only used 7.x-1.x. Is 7.x-4.x for Webform 4.x?

Comment #5

GDrupal commented 14 January 2013 at 18:45

@Cottser 7.x-1.x. vs 7.x-4.x is only changing the way some field are pulled from the form structure.. not big differences from now.. so if you write a patch could apply for both branches.