PUBLIC - Liferay Portal Community Edition

It should be possible to publish the global scope from a remote staging to the live server

Details

  • Branch Version/s:
    6.1.x
  • Backported to Branch:
    Committed
  • Story Points:
    4
  • Fix Priority:
    4
  • Similar Issues:
    Show 5 results 

Description

Currently there is no way to publish the contents (including structures, categories, ...) in the global scope which is a problem when a site which references any of them is published to live.

Issue Links

causes

Bug - A problem which impairs or prevents the functions of the product. LPS-28626 New users cannot view Control Panel when trash.enabled=2

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Regression Bug - Used by Liferay QA to indicate an issue discovered during regression testing LPS-28294 Unable to select pages to publish to local live staging

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Regression Bug - Used by Liferay QA to indicate an issue discovered during regression testing LPS-28881 When remote staging enabled without versionning and branching enabled one cannot publish to remote live

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Regression Bug - Used by Liferay QA to indicate an issue discovered during regression testing LPS-28988 Canot activate remote staging

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates

Feature Request - LPS-25242 When publish the page which is not mark as ready for publication, it will throw a warning message that is confusing

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vivek Agarwal added a comment -

This is a big functional gap from my perspective - Liferay supports global content, and also supports the ability to publish from remote staging to the live server. Given these two assertions, it certainly should be possible (from a Liferay customer perspective) to be able to publish global content from remote staging to live. When I see a priority of "minor" that does not sound right to me. We have Liferay EE customers who are affected by this issue, as they assumed that they would be able to do this.

Show
Vivek Agarwal added a comment - This is a big functional gap from my perspective - Liferay supports global content, and also supports the ability to publish from remote staging to the live server. Given these two assertions, it certainly should be possible (from a Liferay customer perspective) to be able to publish global content from remote staging to live. When I see a priority of "minor" that does not sound right to me. We have Liferay EE customers who are affected by this issue, as they assumed that they would be able to do this.
Hide
Permalink
Mate Thurzo added a comment -

Hi Vivek,

First of all thank you for the comment. We know that this is a problem for those who use the global scope alongside with the remote staging. We have started working on this problem and we would like to address it as soon as possible.

Thank you for your understanding and patience,

Máté

Show
Mate Thurzo added a comment - Hi Vivek, First of all thank you for the comment. We know that this is a problem for those who use the global scope alongside with the remote staging. We have started working on this problem and we would like to address it as soon as possible. Thank you for your understanding and patience, Máté
Hide
Permalink
Michael Saechang added a comment -

Committed on:
Portal 6.2.x GIT ID: 9f6f24de1bd84709a0408198536b0276c025c33b.

Show
Michael Saechang added a comment - Committed on: Portal 6.2.x GIT ID: 9f6f24de1bd84709a0408198536b0276c025c33b.
Hide
Permalink
Ginson Ren added a comment -

Stuck by LPS-28988.

Show
Ginson Ren added a comment - Stuck by LPS-28988 .
Hide
Permalink
Ginson Ren added a comment - - edited

PASSED Manual Testing using the following steps:

1. Two liferay instances running on separate machines, a local machine (staged environment) and a remote machine (live environment).
2. Remote machine has tunnel.servlet.hosts.allowed=127.0.0.1,[IP Address of the staged environment] set in portal-ext.properties file.
3. On remote machine, create a new site and copy the Site ID.
4. On local machine, go to Control Panel > Site, create a new site.
5. Click Site Pages > Add Page, add a new page for the site.
6. Click Site Settings > Staging > Remote Live.
7. Remote Host/IP:

{remote_machine_ip_address}

/ Port: 8080/ Remote Site ID:

{copied from 'Create live environment'}

.
8. Click Save button.
9. Change the site scope to Global.

Reproduced on:
Tomcat 6.0 + MySQL 5. Portal 6.0.12 EE.

There is no way to publish the global scope from a remote staging to live.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: a587d43c74fade9e263c45db95ded2b29c87034e.
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: e7c06e84cd91f4481c5a977639eee64906b78c69.

There are a Staging button next to global and user can publish the global scope from a remote staging to live.(See attachment)

Show
Ginson Ren added a comment - - edited PASSED Manual Testing using the following steps: 1. Two liferay instances running on separate machines, a local machine (staged environment) and a remote machine (live environment). 2. Remote machine has tunnel.servlet.hosts.allowed=127.0.0.1, [IP Address of the staged environment] set in portal-ext.properties file. 3. On remote machine, create a new site and copy the Site ID. 4. On local machine, go to Control Panel > Site, create a new site. 5. Click Site Pages > Add Page, add a new page for the site. 6. Click Site Settings > Staging > Remote Live. 7. Remote Host/IP: {remote_machine_ip_address} / Port: 8080/ Remote Site ID: {copied from 'Create live environment'} . 8. Click Save button. 9. Change the site scope to Global. Reproduced on: Tomcat 6.0 + MySQL 5. Portal 6.0.12 EE. There is no way to publish the global scope from a remote staging to live. Fixed on: Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: a587d43c74fade9e263c45db95ded2b29c87034e. Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: e7c06e84cd91f4481c5a977639eee64906b78c69. There are a Staging button next to global and user can publish the global scope from a remote staging to live.(See attachment)

People

Vote (2)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    34 weeks, 3 days ago