Type: Feature Request
Affects Version/s: 6.1.20 EE GA2
Fix Version/s: None
Environment:LIFERAY VERSION: 6.1 GA 2
OPERATING SYSTEM: Linux
APPLICATION SERVER: Tomcat 7.0.x
JAVA VIRTUAL MACHINE: Java 6
DATABASE: DB2 9.7
Similar Issues:Show 5 results
LPS-13303 Localization of WebContent in editor might loose content in some languages LPS-30464 Would like to have a specific permission for Staging LPS-900 There are a lot of missing language keys in the language files for various "minor" languages LPS-39255 Create a feature where one could utilize locales more easily when staging/lar export and import LPS-27335 Solr not indexing and searching for different translations for web content correctly
Currently, based on:
one must have en_US listed in the locales portion of the language property in order for Liferay languages/translations to work properly. When performing local staging, one must have both the English (United States) language translation and the other language in order for the web content to be staged correctly. Please see attached. Not doing so will result in an error.
Can we implement an improvement so that the English (United States) is not needed in the Web Content to local stage?