-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: Master
-
Fix Version/s: 7.0.0 DXP FP30, 7.0.X EE, 7.0.4 CE GA5, 7.1.X, Master
-
Component/s: Dynamic Data Mapping, Staging
-
Branch Version/s:7.0.x
-
Backported to Branch:Committed
-
Fix Priority:5
-
Git Pull Request:
Steps to Reproduce:
- Set up 2 liferay servers
- Configure properties for remote staging on both servers:
tunnel.servlet.hosts.allowed={IPs} tunneling.servlet.shared.secret={key} tunneling.servlet.shared.secret.hex=true auth.verifier.TunnelingServletAuthVerifier.hosts.allowed={IP} auth.verifier.pipeline=com.liferay.portal.security.auth.TunnelingServletAuthVerifier,com.liferay.portal.security.auth.BasicAuthHeaderAutoLogin,com.liferay.portal.security.auth.DigestAuthenticationAuthVerifier,com.liferay.portal.security.auth.ParameterAutoLogin,com.liferay.portal.security.auth.PortalSessionAuthVerifier
- Start servers
- Enable Remote Live staging between servers with all content types
- Go to staged site server
- Add form with text field
- Save form
- Publish to Live
Expected Result:
Form can be published remote live site.
Actual Result:
Publication fails.
The following error in Forms while importing its data has stopped the process: java.lang.RuntimeException: Unable to get class name from id 31507
Also reproducible with DDL Lists and Web Content Structures
Reproduced on:
Tomcat 8.0.32 + MySQL 5.7.17. Portal master GIT ID: f08886d834fd62d6422349a116834e6eef7a6708.
Not Reproducible on:
Tomcat 8.0.32 + MySQL 5.7.17. Portal ee-7.0.x GIT ID: 9496e46ec5a4c8d2e8656aebfb86e61e0723da8e.
- is caused by
-
LPS-71801 Optimize DDMTemplatePermission and DDMStructurePermission to avoid unnecessary class name id to class name string convertion
- Closed