Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
Change the portal's context to something other than ROOT (e.g. "cms"). On Tomcat this can be done by:
1. Add the following 2 lines to portal-ext.properties file:
2. Rename the /ROOT folder to /cms in TOMCAT_HOME/webapps
3. Rename "TOMCAT_HOME/conf/Catalina/localhost/ROOT.xml" to "TOMCAT_HOME/conf/Catalina/localhost/cms.xml"
4. Edit "TOMCAT_HOME/conf/Catalina/localhost/cms.xml" change <Context path="" crossContext="true"> to <Context path="/cms" crossContext="true">
5. Delete the content of the folders /temp and /work in TOMCAT_HOME (delete the tomcat cache)
Set up another Liferay Portal instance and set the context the same way as above to something different e.g. "cms_live". Then to reproduce:
6. Set up remote staging on "cms" instance to publish content to "cms_live".
7. Create a page on "cms" in staging and add Web Content Display portlet
8. Add new web content and insert a link within the content (with ckeditor feature)
9. Click Browse Server to open Resource Browser
10. Change Resource Type to Page
11. Select a page within the default community (e.g. liferay.com)
12. Click OK to create link and Publish web content
13. Now select Publish to Live Now and publish the page to remote live
14. On "cms_live" instance refresh the page. The link within the published web content will point to the staging site's context (e.g. /cms/web/guest-staging/test-1 instead of /cms_live/web/guest-staging/test-1)
Also: if the servlet mapping for public/private pages is different on remote live, the links within web contents are not updated accordingly during publishing. e.g. /web for public pages on staging and /web_live on live.