[LRA-256]  The application does not allows to re-add an "Automatic Translation" language after it was removed from the list of translations available for the web content. Created: 26/Jul/17  Updated: 04/Aug/17  Resolved: 04/Aug/17

Status: Closed
Project: Liferay Apps
Component/s: Content Translator
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Juan Camacho [X] (Inactive) Assignee: Juan Camacho [X] (Inactive)
Resolution: Fixed Votes: 0
Labels: Content_Translator
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Device: MacBook Pro
Google Chrome Version 54.0.2840.98 (64-bit)


 Description   
The application does not allow to re-add an "Automatic Translation" language after it was removed from the list of translations available for the web content.

1.Open the Liferay APP with the configurations to use the Content Translator .
2. Click on the + icon.
3. Add a “Web Content Display”
4. In the “Web Content Display” click on the (+) icon and select Basic Web Content.
5. Fill out all the fields
6. Click on the “Publish” button.
7. Click on the Edit Web Content button.
8. Click on the Automatic Translation Button.
9. Select 2 languages (Chinese and Dutch) and click on the continue button.
10. Click on the “Publish” button.
11. Click on the Edit Web Content button.
12. Click on the (X) button of the (Chinese and Dutch) languages.
13. Click on the Automatic Translation Button.
14. Review the available languages.

CURRENT RESULT:
====================
The application does not allows to re-add an "Automatic Translation" language after it was removed from the list of translations available for the web content, languages are not available to be selected.
https://www.screencast.com/t/B09o0EQD

EXPECTED RESULT:
====================
The application should allow to re-add an "Automatic Translation" language after it was removed from the list of translations available for the web content.




 Comments   
Comment by Juan Camacho [X] (Inactive) [ 04/Aug/17 ]
Bug verified and closed as fixed in build dc3c1e1.
Generated at Sat Feb 10 05:49:45 GMT 2024 using Jira 8.1.3#801003-sha1:6b6f07cffadda9a0d6efe24639daed8ce94dcdd6.