7.1.X, 7.2.X, Master
Custom fields present in documents should have into account the available locales defined in the document type the document is based on. Currently, they include a list of all available locales of the site, making it confusing and breaking the functionality when defining a translation not available for the document type specific fields.
Steps to reproduce:
- Add a new Document (Input field) custom field, called 'custom-localizable-input' and make it localizable.
- Add a new Document Type, called 'Text-localized-doctype' and add a localizable Text field. Do not add any translations, just the default one (US English).
- Add a new 'Text-localized-doctype' document
- Check the custom field translations drop down list.
Expected result: as indicated in PTR-1530, the list includes the file entry type available languages (US English).
Current result: the list includes all available languages in the site