-
Type:
Bug
-
Status: Closed
-
Resolution: Duplicate
-
Affects Version/s: 6.1.20 EE GA2, 6.1.X EE
-
Fix Version/s: 6.2.0 CE GA1, 6.2.10 EE GA1
-
Component/s: Staging
-
Labels:
-
Environment:LIFERAY VERSION: 6.1 GA2
OPERATING SYSTEM: Windows Server 2008
APPLICATION SERVER: Tomcat 7.0
JAVA VIRTUAL MACHINE: Java 6
DATABASE: SQL Server 2008 R2
- Setup two Liferay nodes, 1 staging and 1 remote live
- Edit your hosts file to point 127.0.0.1 to me.com
- Start the remote live instance and login
- Create a new Liferay instance on the remote live instance: me.com
- Go to me.com:8080 and login
- Go to Control Panel > Site Settings and note the site ID.
- Start the staging site and login
- Add pages and content as desired
- Change your admin user to have the same exact Screen Name, Email Address, Password, and, First and Last name as the user in the remote live (me.com) instance
- Go to Control Panel > Site Settings > Staging
- Enable Remote Live staging pointing to your remote live (me.com) instance using the IP Address (in this case 127.0.0.1)
- Notice how Remote Live staging cannot be enabled
- Enable Remote Live staging just like step 11, but use the domain instead of the IP address (in this case me.com).
- Notice that Remote Live staging is enabled
- Now, go to the first instance of Liferay on the Remove Live instance and modify the admin user to match the publishing user on the Staging node
- Attempt to alter the staging setup on the staging node and use the IP address
- Notice that it now enables with the IP address
- duplicates
-
LPS-34035 Remote Staging can be activated with erroneous parameters causing the remote data corruption after publishing
- Closed