PUBLIC - Liferay Portal Community Edition

GroupId error when using ADT in page-scoped portlets with staging

Details

  • Similar Issues:
    Show 5 results 

Description

Steps to reproduce:
Create a site and enable staging.
Create two pages (A & B)
In both pages add a blogs portlet
In page B configure the blogs portlet to have page scope to B

In portlet in page A, create a new Application Display Template: you'll see it appear both in the popup and in the dropdown menu
In portlet in page B, create a new Application Display Template: you'll see it appear both in the popup and in the dropdown menu

Publish to live

In portlet in page A you'll see it appear both in the popup and in the dropdown menu
In portlet in page B you'll see it appear ONLY in the dropdown menu and NOT in the popup

Issue Links

relates

Bug - A problem which impairs or prevents the functions of the product. LPS-31111 Methods in GroupImpl that check staging settings return wrong result when staging is enabled or group is a layout scope

  • 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
Juan Fernández added a comment -

I have merged both taglibs to avoid having different groupIds calculation. BUT doing this, I have discovered LPS-31111.

Show
Juan Fernández added a comment - I have merged both taglibs to avoid having different groupIds calculation. BUT doing this, I have discovered LPS-31111 .
Hide
Permalink
Jorge Ferrer added a comment -

In order to be 100% sure that this works as expected in all scenarios we created a table of all possible cases.

We tested ADT with the blogs portlet (any other portlet would behave the same way) and tested with the portlet setup to use the regular scope or the page scope. We also tested with all combinations of staging enabled or disabled for ADT and blogs.

The attached OpenDocument spreadsheet documents the 8 test cases identified and the expected result fo reach.

Show
Jorge Ferrer added a comment - In order to be 100% sure that this works as expected in all scenarios we created a table of all possible cases. We tested ADT with the blogs portlet (any other portlet would behave the same way) and tested with the portlet setup to use the regular scope or the page scope. We also tested with all combinations of staging enabled or disabled for ADT and blogs. The attached OpenDocument spreadsheet documents the 8 test cases identified and the expected result fo reach.
Hide
Permalink
Tammy Fong added a comment -

Committed on:
Portal 6.2.x GIT ID: 2408d645d9263306fdcf3ccf514230b6da3e2125.

Show
Tammy Fong added a comment - Committed on: Portal 6.2.x GIT ID: 2408d645d9263306fdcf3ccf514230b6da3e2125.
Hide
Permalink
Mark Jin added a comment -

PASSED Manual Testing following the steps in the description.

Reproduced on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 8761bcd7f2d455f959381298617cb891cb73eaa7.

Users can see the ADT appear ONLY in the dropdown menu and NOT in the popup

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 71213361b6c18d85c669facc1c2db7b168c9ad0f.

Users can see the ADT appear both in the popup and in the dropdown menu.

Show
Mark Jin added a comment - PASSED Manual Testing following the steps in the description. Reproduced on: Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 8761bcd7f2d455f959381298617cb891cb73eaa7. Users can see the ADT appear ONLY in the dropdown menu and NOT in the popup Fixed on: Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 71213361b6c18d85c669facc1c2db7b168c9ad0f. Users can see the ADT appear both in the popup and in the dropdown menu.
Hide
Permalink
Michael Saechang added a comment -

Thank you Mark for testing, closing as 'Fixed'.

Show
Michael Saechang added a comment - Thank you Mark for testing, closing as 'Fixed'.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    22 weeks, 6 days ago