When i18n shortcuts (e.g. en_US, cs_CZ, sk_SK, ..) are used in URLs, changing language does not work (with virtualhosts)

Description

My i18n functionality with virtualhosts (e.g. www.domain.com/en_US/... or www.domain.com/sk_SK/...) works perfectly except "change language" functionality:

https://www.domain.com/home?p_p_id=82&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=%2Flanguage%2Fview&languageId=sk_SK

works OK

https://www.domain.com/home?p_p_id=82&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=%2Flanguage%2Fview&languageId=en_US

works OK

but :

https://www.domain.com/en_US/home?p_p_id=82&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=%2Flanguage%2Fview&languageId=en_US

changes URL to https://www.domain.com//www.domain.com/en_US/home and returns:

Status
Not Found
The requested resource was not found:

https://www.domain.com/www.domain.com/en_US/home

and the same for languageId=sk_SK

– www.domain.com is set as a public virtualhost

in other words - where i18n shortcuts (en_US, de_DE, etc.) are used in URLs, changing language does not work.

Environment

liferay-portal-5.2.3 + tomcat-6.0.18 + on ubuntu 9.10 with 2.6.28-15-server i have enabled i18n in web.xml: <servlet-mapping> <servlet-name>I18n Servlet</servlet-name> <url-pattern>/sk_SK/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>I18n Servlet</servlet-name> <url-pattern>/cs_CZ/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>I18n Servlet</servlet-name> <url-pattern>/en_US/*</url-pattern> </servlet-mapping> in in my_template/templates/portal_normal.vm : $taglibLiferay.language("fm", null, "languageId", 1) I use liferay virtualhost set in this way: public virtualhost: www.domain.com private virtualhost: core.domain.com/web/domain friendly URL: /domain

Activity

Show:

Cynthia WilburnJuly 23, 2010 at 9:08 PM

This ticket is being closed as inactive due to the date of the last activity on it and a need for a current affected version. If you believe this was done in error, please create a new issue and confirm that it is reproduceable in the current 6 CE GA release.

In recent months Liferay has received a significant number of anomaly reports many of which are really requests for help. Because of this fact, the real bug reports are no longer easily identifiable. To remedy this problem we need your assistance. We will working towards closing open tickets that meet specific criteria and ask you to create a new issue for those that that are truly bug reports. We'll be monitoring those tickets so that they are properly managed.

Thank you,
The Liferay Team
ICS120109

Inactive
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Affects versions

Priority

Zendesk Support

Created September 18, 2009 at 11:45 AM
Updated June 23, 2023 at 8:50 PM
Resolved July 23, 2010 at 9:08 PM