As seen on "admin/content", new nodes are always language neutral when created. However, as soon as the locale module is activated, new nodes are suddenly saved language-specific. Multilingual support for content-types defaults to disabled though.
The "Multilingual support" setting describes this behaviour in its description, however
* it does not make much sense to me to save the node in a certain language if it is configured to have no multi-langual support.
* it is weird that enabling the "locale" module changes existing behaviour without any configuration changes. Why are new nodes not language-neutral any more just as the old ones?
Comments
Comment #1
fagoComment #2
fagoRelated issue for fields #1208856: Enabling locale module changes field default language
Comment #11
quietone CreditAttribution: quietone as a volunteer commentedI tested this on Drupal 7 and Drupal 8.9.13 on fresh installs of standard.
In D8, when a new node is created, the language is 'en' (I installed in English). Then enabled locale, create a new node and the new node has a language of 'en'. That seems perfectly reasonable even though translations are not enabled. I had installed in English and the all the new nodes must be in the install language. I installed in Italian and the new nodes were in Italian. That all seems correct. So a cannot reproduce for D8.
In D7, when a new node is created, the language is 'und'. Then enabled locale, create a new node and the new node has a language of 'en'. The IS suggests that is incorrect because translation has not been enabled. Considering that the description for locale states "Adds language handling functionality and enables the translation of the user interface to languages other than English." It seems that it is correct to make the language of the 'en' instead of 'und'. However, I really don't know enough about locale so will move this to the D7 issue queue.