After uninstalling the Content Translation and Locale modules, the `language` columns for the nodes and fields tables remain at any language that was saved while supporting multiple languages via Locale. Nodes that were never saved with a language continue to work.

When these modules are uninstalled, the original "source" node should be reset to 'und' language to ensure the content is still working. Either this, or at least there should be an option or warning expressing this potential problem. If a user uninstalls these modules after using them for a while, any of that content is now unusable.

Comments

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented
Status: Active » Closed (duplicate)

#989540: Field content is no more accessible after disabling Locale module
#1073242: Disabling locale leaves field content missing

Not resetting the field language after uninstalling Locale is a design choice, as when multiple languages are available for each field this may cause unpredictable consequences, AAMOF other modules might exploit field's language support. The current solution is: don't disable Locale if you created multilingual content.

However this should not happen anymore once #1164852: Inconsistencies in field language handling is fixed.