-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
-
Fix Version/s: 6.1.30 EE GA3, 6.2.0 CE M2
-
Component/s: Staging
-
Labels:
-
Branch Version/s:6.1.x
-
Backported to Branch:Committed
-
Git Pull Request:
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:
portal.ctx=/cms
portlet.virtual.path=/cms
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)
Then to reproduce:
6. Turn on staging
7. Create a page 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
14. On Live, the link within the published web content will still point to the page on Staging (e.g. /cms/web/guest-staging/test-1)