If you enable Locale and Content Translation, you can set the Multilingual settings on the Content Type form. Strangly, this is hidden under the Publishing Options. I think this is very strange. What do Multilingual settings have to do with Publishing options?
My suggestion would be to place these settings in their own tab (Multilingual settings).
This could be achieved very easily without breaking other functionality.
Is there momentum for this?
Comment | File | Size | Author |
---|---|---|---|
#7 | locale-verticaltab.patch | 1.61 KB | pfrenssen |
#5 | locale-verticaltab.patch | 1.55 KB | pfrenssen |
#2 | locale-verticaltab.patch | 985 bytes | pfrenssen |
multilingual_settings.png | 18.63 KB | BarisW |
Comments
Comment #1
plachI would totally support this, but aren't we past UI-freeze?
Comment #2
pfrenssenGreat idea. Here's a patch :)
Comment #3
Bojhan CreditAttribution: Bojhan commentedYes, we are past UI freeze. Also the text is way too much. Its wierd to fall under publishing settings yes, but to make a tab for 1 setting?
Comment #4
plach@Bojhan:
If we talking about D8 you can bet there will be many other options ;)
And keep in mind i18n has a "multilingual" tab with its options. Having to set the main one under 'publishing options' and the rest in the 'multilingual' tab is pretty confusing also for one that knows the system well.
Comment #5
pfrenssenI agree, it just feels much more user friendly when the multilingual tab is there. BTW some of the other tabs do not have many options either, eg "Publishing Options" and "Display Settings".
The help text is too overwhelming indeed, I shortened it up a bit.
Comment #6
plachAt least the following information should be retained
as this behavior is not that intuitive.
Comment #7
pfrenssenYou're right. I put that line back in. Also changed the component for this issue to locale.module.
Comment #8
plachActually this feature request concerns the language system :)
Comment #9
Bojhan CreditAttribution: Bojhan commentedI am fine with adding it in, but it is UI freeze - understand if it will get declined by commiters. I dont see it being useful to have one extra tab for the sake of theoretical new options in D8. I hope you will clean up the text, that was a red flag for me.
Comment #10
plachI'll make myself a little more clear: almost surely this cannot go in for D7. OTOH, one of my goals for D8 is getting most of the options currently offered by i18n in core; hence we can defer this patch to the moment they will go in (if it will ever come) or "pave the way" for them.
Comment #11
sunAbsolutely one of the first steps to do for D8.
Comment #12
Bojhan CreditAttribution: Bojhan commentedMakes sense, it didn't got in D7 because the text sucked and there was only 1 option - plach assures me D8 will have more options and awesome text :)
Comment #13
Gábor HojtsyWell, i18n and content translation module in contrib both needs to have this reorganized for Drupal 7, so I think once you enable either, you should not see the core behavior anymore. Both make this more rich, put it more options, etc. I understand Drupal 7 is UI frozen, so we'll make it inconsistent with contrib instead then :) See #1031278: Move multilingual options into a dedicated fieldset
Comment #14
zirvap CreditAttribution: zirvap commentedI've marked #953722: Create/edit content type: Translation info missing in vertical tabs as duplicate of this.
Comment #15
klonos...subscribing.
Comment #16
Gábor HojtsyShould clean this up in Drupal 8 indeed. It is *very* confusing as-in in Drupal 7.
Comment #17
weakqueen99 CreditAttribution: weakqueen99 commentedI am working with it, I was fix again, and demo run in this time.
Comment #18
Gábor HojtsyTagging for the content handling leg of D8MI.
Comment #19
Gábor HojtsyThis is being resolved in #258785: Provide more flexible settings for initial language on content types. Marking as duplicate.