PUBLIC - Liferay Portal Community Edition

Search results in web content administration could be confusing when match only applies to old version

Details

  • Branch Version/s:
    6.1.x, 6.0.x
  • Backported to Branch:
    Committed
  • Story Points:
    3
  • Similar Issues:
    Show 4 results 

Description

If a web content administrator searches for Web Content from the administration portlet, and the search terms are found in previous versions of the articles, that old version is shown in the list. In this scenario the preview action shows the specific version but all others affect the latest version. This is quite confusing for the user.

Steps to reproduce:

1. Go to Control Panel > Web Content.
2. Create a basic Web Content (WC1 v1.0) with name=test and content=hello.
3. Copy this content to create a new Web Content (WC2 v1.0 name=test content=hello)
4. Edit WC2 and set the name=other-content (WC2 v1.1 name=other-content content=hello)
5. Edit WC2 and set the name=final-version and content="bye" (WC2 v1.2 name=final-version content=bye)
6. From Control Panel > Web Content search by "hello".

Results:

  • The title shown is the one for the old version (which might not be the same as the latest version)
  • Returned one result for WC1 (v1.0 name=test) and only another one for WC2 (v1.0 name=test). In the case of WC2, the preview action shows the first version but all others apply to the latest version (1.2)

Expected result:

  • It should be more clear for the user when the text was found in an old version and it should be clear for the user to which version the actions apply.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. LPS-25859 Wrong information indexed for web content

  • 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.

Story - An user story LPS-32153 As a user I can search within the comments in all portlets where comments are allowed

  • 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
Ginson Ren added a comment -

PASSED Manual Testing following the steps in the description.

Reproduced on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: e782c1ebc63271a45ab85125a0cad0e1ce0c01ef.

There is no version information.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 344c39a2f03d8c78a1061c2218cb1204a5887988.

It will be more clear for user which version it display.

Show
Ginson Ren added a comment - PASSED Manual Testing following the steps in the description. Reproduced on: Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: e782c1ebc63271a45ab85125a0cad0e1ce0c01ef. There is no version information. Fixed on: Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 344c39a2f03d8c78a1061c2218cb1204a5887988. It will be more clear for user which version it display.
Hide
Permalink
Ginson Ren added a comment -

Fixed on:
Tomcat 6.0 + MySQL 5. Portal 6.0.x GIT ID: 23e4b185c8bdb2c40e438d392866a4b46404bd75.

It will be more clear for user which version it display.

Show
Ginson Ren added a comment - Fixed on: Tomcat 6.0 + MySQL 5. Portal 6.0.x GIT ID: 23e4b185c8bdb2c40e438d392866a4b46404bd75. It will be more clear for user which version it display.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    15 weeks ago