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?

Comments

plach’s picture

I would totally support this, but aren't we past UI-freeze?

pfrenssen’s picture

FileSize
985 bytes

Great idea. Here's a patch :)

Bojhan’s picture

Version: 7.x-dev » 8.x-dev

Yes, 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?

plach’s picture

@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.

pfrenssen’s picture

FileSize
1.55 KB

I 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.

plach’s picture

At least the following information should be retained

"If disabled, new posts are saved with the default language."

as this behavior is not that intuitive.

pfrenssen’s picture

Component: translation.module » locale.module
FileSize
1.61 KB

You're right. I put that line back in. Also changed the component for this issue to locale.module.

plach’s picture

Component: locale.module » language system

Actually this feature request concerns the language system :)

Bojhan’s picture

I 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.

plach’s picture

I'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.

sun’s picture

Category: feature » task

Absolutely one of the first steps to do for D8.

Bojhan’s picture

Makes 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 :)

Gábor Hojtsy’s picture

Well, 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

zirvap’s picture

klonos’s picture

...subscribing.

Gábor Hojtsy’s picture

Issue tags: +D8MI

Should clean this up in Drupal 8 indeed. It is *very* confusing as-in in Drupal 7.

weakqueen99’s picture

I am working with it, I was fix again, and demo run in this time.

Gábor Hojtsy’s picture

Issue tags: +language-content

Tagging for the content handling leg of D8MI.

Gábor Hojtsy’s picture

Status: Active » Closed (duplicate)