PUBLIC - Liferay Portal Community Edition

Web Content/ LAR: after importing a LAR, the system will generate a new ID for the content articles even though there are no other articles

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 6.0.6 GA, 6.0.12 EE, 6.1.0 CE RC1, 6.1.1 CE GA2, 6.1.20 EE GA2
  • Fix Version/s: 6.2.X
  • Component/s: Frameworks, Frameworks > Export/Import, WCM, WCM > Web Content Administration
  • Labels:
    None
  • Environment:
    Tomcat 6.0.33 + MySQL 5. 6.0.x GIT ID: 7f1f81affc5c2cd6e6040a8b85ea87ef8175e93f.
    Tomcat 7.0 + MySQL 5. 6.1.x EE GIT ID: 351ed96fa6bb241f0f96f178b022d3b42ffd9fa3.
    Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 0ac7183f912f750000d7eabb5f2ef5ccd25ebe7a.
  • Fix Priority:
    4
  • Similar Issues:
    Show 5 results 

Description

When the user creates two web content articles then export/import as a LAR, there is a console warning that articles with that ID already exists and generates a new one.

22:12:01,293 WARN [JournalPortletDataHandlerImpl:1628] An article with the ID 10411 already exists. The new generated ID is 10422
22:12:01,339 WARN [JournalPortletDataHandlerImpl:1628] An article with the ID 10444 already exists. The new generated ID is 10431

Steps taken:
1. Add a page and the web content portlet
2. Add two web content articles.
3. Export as a LAR
4. Clear the database
5. Clear the browser cache
6. Delete the Liferay Home folder
7. Import as a LAR
8. When clicking Import, the system generates the above message.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Luyang Tan added a comment - - edited

Reproduced on:
Tomcat 7.0 + MySQL 5. 6.1.x EE GIT ID: ffcc2a0d84eb96e99224e8701470bf79361c723a.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 2a7f9953c779e76ba79dd1efa6fa34fb557bd245.

I can still see the warn message.

Show
Luyang Tan added a comment - - edited Reproduced on: Tomcat 7.0 + MySQL 5. 6.1.x EE GIT ID: ffcc2a0d84eb96e99224e8701470bf79361c723a. Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 2a7f9953c779e76ba79dd1efa6fa34fb557bd245. I can still see the warn message.
Hide
Permalink
Justin Choi added a comment -

Reproduced on:
Tomcat 6.0.33 + MySQL 5. 6.0.x GIT ID: 7f1f81affc5c2cd6e6040a8b85ea87ef8175e93f.
Tomcat 7.0 + MySQL 5. 6.1.x EE GIT ID: 351ed96fa6bb241f0f96f178b022d3b42ffd9fa3.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 0ac7183f912f750000d7eabb5f2ef5ccd25ebe7a.

Show
Justin Choi added a comment - Reproduced on: Tomcat 6.0.33 + MySQL 5. 6.0.x GIT ID: 7f1f81affc5c2cd6e6040a8b85ea87ef8175e93f. Tomcat 7.0 + MySQL 5. 6.1.x EE GIT ID: 351ed96fa6bb241f0f96f178b022d3b42ffd9fa3. Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 0ac7183f912f750000d7eabb5f2ef5ccd25ebe7a.
Hide
Permalink
Lawrence Lee added a comment -

PASSED Manual Testing following the steps in the description.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 5c2d61a7ff6b56e14d121483f9c444d2709ffa8d.
Error does not show up and the article displays correctly in the portal.

Show
Lawrence Lee added a comment - PASSED Manual Testing following the steps in the description. Fixed on: Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 5c2d61a7ff6b56e14d121483f9c444d2709ffa8d. Error does not show up and the article displays correctly in the portal.

People

Vote (0)
Watch (6)

Dates

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