Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 6.1.0 CE GA1, 6.1.1 CE GA2, 6.1.10 EE GA1, 6.1.20 EE GA2
-
Fix Version/s: 6.1.10 EE GA1, 6.1.X EE, 6.2.0 CE M2
-
Component/s: WCM, WCM > Asset Publisher
-
Labels:
-
Branch Version/s:6.1.x
-
Backported to Branch:Committed
-
Fix Priority:3
-
Similar Issues:
Description
1. Setup Liferay portal with two pages:
1.1 one with "source" asset publisher and "Language" portlet
1.2 another page with asset publisher defined as "default for this page"
2. Congigure first asset publisher: Asset Link Behavior: "View in Specific Portlet"
3. Switch to non-english locale (in my case I've switched into Russian)
4. Add new webcontent to display in asset publisher. Then created - set Display Page property of created web-content to display on second page.
After creation web-content is displayed on first publisher. On click on this content it is expected what it will be displayed in second page. But browser displayed first page of group
In case we edit content with english (en_US) language - it is working as expected (web-content is opened in target page).
I'm expecting problem in searching for asset by title user in friendly url
This problem is not reproduced in Liferay 6.1.10 EE

Just tested additionaly - this problem also reproduced in 6.1.10 EE.
To reproduce problem - no needs to create web-content in specific language.
Issue in using language prefix in URL and using non-ascii symbols in web-content title.
If I'm navigating to:
http://localhost:8080/web/smartphones/-/%D1%8D%D1%82%D0%BE-%D0%BD%D0%BE%D0%B2%D0%BE%D1%81%D1%82%D1%8C-%D0%BD%D0%B0-%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%BE%D0%BC
jourtal article found well and it is displayed on related page
If I'm trying to navigate to
http://localhost:8080/ru/web/smartphones/-/%D1%8D%D1%82%D0%BE-%D0%BD%D0%BE%D0%B2%D0%BE%D1%81%D1%82%D1%8C-%D0%BD%D0%B0-%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%BE%D0%BC
journal article is not found and default site page is displayed.
It happens because in first (correct) case method PortalImpl.getJournalArticleActualURL received decoded friendlyURL, but in second case - not decoded - and as result cannot find specific journal article