Affects Version/s: 7.0.X, 7.1.X, Master
Component/s: ~ [Archived] Frontend Infrastructure
Available translations/locale should be given by the scope/site in where the web content is created and not by other scope in where you can edit the web content.
Steps to reproduce.
- Create a WC named web-content1 in Global Scope, add some translations, as the English, Catalonian, and Portuguese (configure the title, description, content, and also the friendlyULR for the translations)
- Create a Site1, and only enable the Spanish as Default and Unique available language for this site.
- Create a page1 in the Site1, and add to the page the Asset Publisher and configure to display content from the Global Scope.
- Edit the web-content1 from the asset publisher.
Result You only can manage the spanish translation. If you save the content and you return to the Global site, the web content 1 has lost the other translations. it again from the Global site, the others translations are lost.
Expected You can edit the translation for the locales availables in Global