PUBLIC - Liferay Portal Community Edition

When setting up portal context environment, remote staging is unable to "Publish to Remote Live"

Details

  • Branch Version/s:
    6.1.x
  • Backported to Branch:
    Committed
  • Similar Issues:
    Show 4 results 

Description

1. Add portal.ctx=/web to your portal-ext.properties on your source server and restart
2. Create a new site on your source server and add at least one page to it
3. Add portal.ctx=/web to your portal-ext.properties on your target server and restart
4. Create a new site on your target server
5. Go into Site Settings on your source server and configure remote publishing
6. Make a changing to your staging site on the source server.
7. Try to publish to remote live from the source server.

Observe:
23:51:24,573 ERROR [GroupServiceHttp:230] com.liferay.portal.kernel.exception.SystemException: java.io.FileNotFoundException: http://localhost:8080/api/secure/liferay/do

Issue Links

causes

Regression Bug - Used by Liferay QA to indicate an issue discovered during regression testing LPS-28408 Go to Remote Live link is broken.

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Shinn Lok added a comment -

Because we no longer use /tunnel-web for the tunnel servlet filter url, the remote staging needs to know what context path the target server is using.

Before /tunnel-web removed:

ROOT - localhost:8080/tunnel-web/secure/liferay/do
/liferay - localhost:8080/tunnel-web/secure/liferay/do

Current:

ROOT - localhost:8080/api/secure/liferay/do
/liferay - localhost:8080/api/secure/liferay/do <- invalid

After fix (configurable target server path context):

ROOT - localhost:8080/api/secure/liferay/do
/liferay - localhost:8080/liferay/api/secure/liferay/do
Show
Shinn Lok added a comment - Because we no longer use /tunnel-web for the tunnel servlet filter url, the remote staging needs to know what context path the target server is using. Before /tunnel-web removed: ROOT - localhost:8080/tunnel-web/secure/liferay/ do /liferay - localhost:8080/tunnel-web/secure/liferay/ do Current: ROOT - localhost:8080/api/secure/liferay/ do /liferay - localhost:8080/api/secure/liferay/ do <- invalid After fix (configurable target server path context): ROOT - localhost:8080/api/secure/liferay/ do /liferay - localhost:8080/liferay/api/secure/liferay/ do
Hide
Permalink
Michael Saechang added a comment -

Committed on:
Portal 6.2.x GIT ID: 64dac5b99d1bf7fc9d5bab6e5a8a96cd945882b4.

Show
Michael Saechang added a comment - Committed on: Portal 6.2.x GIT ID: 64dac5b99d1bf7fc9d5bab6e5a8a96cd945882b4.
Hide
Permalink
Pani Gui added a comment -

PASSED Manual Testing following the steps in the description.

Reproduced on:
Tomcat 7.0 + MySQL 5. 6.1.10 EE GA1.

Unable to publish to remote live when setting up portal context.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 54d7ed0f39b755b1667d62670204d83473c7e832.
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 74394859583b760c0f7bdec407ae46ac45815ef7.

Publishing to remote live successfully.

Show
Pani Gui added a comment - PASSED Manual Testing following the steps in the description. Reproduced on: Tomcat 7.0 + MySQL 5. 6.1.10 EE GA1. Unable to publish to remote live when setting up portal context. Fixed on: Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 54d7ed0f39b755b1667d62670204d83473c7e832. Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 74394859583b760c0f7bdec407ae46ac45815ef7. Publishing to remote live successfully.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    43 weeks, 4 days ago