Starting with Monday, July 13th, the behaviour of the localization feature changes as follows:

• When using the locale=* query parameter with unlocalized fields, the API endpoints for entries will no longer return field values related to locales different to the environment default one.

Note that the current behavior of returning all the locales for a non-localized field was a bug that emerged when the user modified a previously localized field to unlocalized.

Consider the following example comparing the two behaviors:

Given an entry with two fields, where the first is localized and the second was set to unlocalized after being initially localized, the API returns:

Before the fix:	After the fix:
{..., fields: { symbol: { 'en-US': 'us symbol', de: 'de symbol'}, notLocalized: { 'en-US': 'us notLocalized', de: 'de notlocalized' } } }	{..., fields: { symbol: { 'en-US': 'us symbol', de: 'de symbol' }, notLocalized: { 'en-US': 'us notLocalized' } } }