-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.1.20 EE GA2, 7.0.0 M3
-
Fix Version/s: 6.2.2 CE GA3 , 6.2.X EE, 7.0.0 M1
-
Branch Version/s:6.2.x
-
Backported to Branch:Committed
-
Story Points:14
-
Fix Priority:4
-
Git Pull Request:
Steps to reproduce:
- Create an arbitrary web content structure (Admin --> Content --> Manage --> Structures).
- Create a template using this structure (Admin --> Content --> Manage --> Templates).
- Create a web content with this structure.
- Change the default language of the portal (Admin --> Control Panel --> Portal Settings --> Display Settings).
- Export the pages of the portal (I tested with public pages, default settings) (Admin --> Pages --> Export)
- Delete the web content.
- Try to import it back with default settings (Admin --> Pages --> Import).
Result: com.liferay.portlet.dynamicdatamapping.TemplateNameException is obtained and importing fails.
- causes
-
LPS-52087 After upgrade from 6.0 publishing to live can result in LocaleException
- Closed
-
LPS-32694 TemplateName exception
- Closed
-
LPS-44731 TemplateName exception
- Closed
- duplicates
-
LPS-46924 Calendar - Unable to import LAR due to CalendarNameException
- Closed
-
LPS-53281 Error activating Staging: The available languages in the LAR file (<em>es_ES</em>) do not match the site's available languages (<em>en_US</em>).
- Closed
- is duplicated by
-
LPS-46763 Changing the default locale for a site (or portal) are causing several issues regarding localized web-contents and export/import
- Closed
-
LPS-34410 StructureNameException is thrown during LAR import if source and target systems' default Locale are not the same
- Closed
- relates
-
LPE-12162 Changing the available languages may prevent publishing to live
-
- Closed
-