Move multilingual options into a dedicated fieldset [#1031278]

When you edit a content type, you choose the multilingual support settings in the content type edit form, which provides "disabled", "enabled", "enabled with node translation" , and "enabled with content translation".

However, this setting should be reflected on the left side of the vertical tab after a selection is made. For example, the vertical tab summary might read "Published, Promoted to front page, Multilingual support: Content translation".

Separate issue: I don't really understand why this is a "publishing option". Perhaps it should have its own vertical tab.

Comments

Comment #1

plach

he/him

Italian

Venezia

commented 18 January 2011 at 15:44

Status:

Active

» Closed (works as designed)

This is a core issue: #895154: Give Multilingual Settings their own vertical tab on the Content Type form.

Comment #2

rfay

he,him

English

Palisade, CO, USA

commented 18 January 2011 at 16:50

Status:

Closed (works as designed)

» Active

I don't think it should probably wait to be resolved until D8 though... Setting this active. Feel free to set it back if you disagree (which I think you do).

Comment #3

plach

he/him

Italian

Venezia

commented 18 January 2011 at 16:53

At very least we need to make sure that i18n supports this, otherwise we will have multilingual options scattered into two vertical tabs.

Comment #4

sun

German

Karlsruhe

commented 18 January 2011 at 17:05

Agreed that we should improve this for D7, and yeah, coordination with i18n is a good idea.

People are going to expect to see that setting in the publishing options with just Locale module being enabled, but TBH, I think it would be sensible to at least add a #after_build or #pre_render to move the setting into a dedicated multilingual options tab, which might confuse users at the beginning, but in the end, better UX. We should not hi-jack the form structure though; i.e., move the existing setting of Locale module at the latest possible point in time (which might mean a #pre_render on the form itself, so we have access to all tabs and can move from one to another).

Comment #5

plach

he/him

Italian

Venezia

commented 20 January 2011 at 14:51

Title:

Publishing options fieldset does not report "multilingual support" status

» Move multilngual options into a dedicated fieldset

retitling

Comment #6

gábor hojtsy

he/him

Hungarian

Hungary

commented 31 January 2011 at 13:07

I think its not about publishing options, its a submission option to be able to specify a language :) I think "Multilingual options" would be a great vertical tab on the node type form. Not sure it should wait for Drupal 8, it is pretty darn ugly this way (in core).