Use languageId to determine Content Locale in JournalTransformer

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.0.0 DXP FP60, 7.0.0 DXP SP9, 7.0.X, 7.1.10 DXP FP3, 7.1.1 CE GA2, 7.1.10.1 SP1, 7.1.X, Master
• Component/s: ~[Archived] WCM
• Labels:
  • ee-ts
  • liferay-dxp-70-sp9
  • liferay-dxp-71-sp1
  • liferay-fixpack-de-60-7010
  • liferay-fixpack-dxp-3-7110
  • no_predic
• Branch Version/s:
  7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Epic/Theme:
  • Technical_Task
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/62761

Given that getArticleContent can be called through the JSON WS where themeDisplay is very hard to set, I think it would be better to use languageId first when translating the template.

 

 

Steps to reproduce:

1. Create a structure with a Select field (and a template for it). Create a web content from this structure.
2. Access the /api/jsonws page, select "journal" for Context Name, and then select the get-article-content method that accepts groupId, articleId, languageId and themeDisplay parameters.
3. Fill in the groupId and articleId of the web content, en_US for languageId, and leave themeDisplay empty. Click Invoke.

Result: The content is not shown and in the Tomcat console you see

2018-08-22 15:06:43.413 ERROR [http-apr-8080-exec-3][JSONWebServiceServiceAction:97] com.liferay.portal.kernel.templateparser.TransformException: Unhandled exception