When Sitefinity 5.3 was released, we introduced Multilingual for 5.3, so by default all new fields that are created in a custom module, built with the module builder, are localizable. However the old fields are not converted to LStrings, but you have the option to convert them to such type. In order to achieve this, you can go to the backend page, which lists all fields for the content type of your custom module. Then if you edit each one of the fields, you will see an option:
"Make localizable" which when clicked will convert your old data type to Lstring.
If one of your custom fields is localizable and the other one is not, it is normal that to get the first field you need to use
and to get the second one:
. Please review your custom fields in the backend of Sitefinity.
All the best,
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items