-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.0.X EE, 6.1.X EE, 6.2.X EE, 7.0.0 M3
-
Fix Version/s: 6.0.X EE, 6.1.X EE, 6.2.2 CE GA3 , 6.2.X EE, 7.0.0 M1
-
Component/s: ~[Archived] WCM
-
Branch Version/s:6.2.x, 6.1.x, 6.0.x
-
Backported to Branch:Committed
-
Story Points:10
-
Fix Priority:3
-
Git Pull Request:
Upgrading from 5.2 to 6.0 or above leaves friendlyURL column untouched.
This behavior could cause problems during the import process
1. Set up a clean portal version 6.0 or above
2. Create a page with a long (more than 100 characters) friendlyURL
3. Export the pages
4. Create another environment: upgrade from 5.2 to 6.0-
5. Try to import the lar file
Result: The import process fails.
16:10:41,644 ERROR [http-bio-9090-exec-21][JDBCExceptionReporter:76] Data truncation: Data too long for column 'friendlyURL' at row 1 16:10:47,333 ERROR [http-bio-9090-exec-21][ImportLayoutsAction:92] com.liferay.portal.kernel.exception.SystemException: com.liferay.portal.kernel.dao.orm.ORMException: org.hibernate.exception.DataException: Could not execute JDBC batch update com.liferay.portal.kernel.exception.SystemException: com.liferay.portal.kernel.dao.orm.ORMException: org.hibernate.exception.DataException: Could not execute JDBC batch update
- relates
-
LPE-12484 Upgrade process does not update friendlyURL column when upgrading from 5.2
-
- Closed
-