Asset Publisher portlet does not display web content, When the content publish again.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.0.5 GA, 6.0.12 EE, 6.1.0 CE RC1, 5.2.X EE
• Fix Version/s: --Sprint 12/11, 6.1.0 CE RC1
• Component/s: WCM > Asset Publisher
• Labels:
  • QA-R
• Environment: Tomcat 6 + MySQL 5. 6.1.x Revision 74678.; Tomcat 6 + MySQL 5. 6.0.x Revision 74642.; Tomcat 6 + MySQL 5. 5.2.x Revision 74676.
• Liferay Contributor's Agreement:
  Accept
• Similar Issues: Show 4 results ; ;

  LPS-31753	Display Page for web content does not work in Asset Publisher
  LPS-20947	Web Content Display portlet shows v1.0 version of Web Content if v1.1 got expired, Asset Publisher does not show anything
  LPS-26779	Web Content Display portlet shows v1.0 version of Web Content if v1.1 got expired, Asset Publisher does not show anything
  LPS-13700	Asset Publisher - Substitute Web Content Display

Asset Publisher portlet does not display web content, When the content publish again.

Steps to reproduced :

1. Start liferay and login.
2. Add a page and add Asset Publisher portlet.
3. Then click Add New button add a web content.
4. Then go to Control Panel >> Web Content expire the content.
5. Now you can not see the web content in Asset Publisher portlet.
6. Go to Control Panel >> Web Content edit the content and publish button.
7. Then back to liferay check Asset Publisher portlet.

[Michael Saechang]

This issue may not be a bug. This may be the expected behavior of the portal. When expiring the article the asset publisher probably removes it, so even after publishing it again, it is no longer in the asset publisher. Will keep the ticket open and have an engineer decide.

[Henri Koskenranta]

I can confirm this too. You don't even need to edit the content, just expire and re-publish and it's not showing in the asset publisher.

Asset publishers are there to show content based on filters and selections. They show content dynamically. Whether an article was expired and is now published again should have no meaning for asset publisher. It should show an article if it matches the filters, a publisher article is a publisher article, no matter it's history.

[Tagnaouti Boubker]

"This issue is being addressed as part of the 100 PaperCuts program. Please see http://liferay.com/community/100-papercut"

I can confirm this too... this behavior still persist on the trunk version.

[Tagnaouti Boubker]

Draft asset entry object seems to be never created :

boolean addDraftAssetEntry = false;

if (!article.isApproved() &&
(article.getVersion() != JournalArticleConstants.DEFAULT_VERSION)) {

int approvedArticlesCount =
journalArticlePersistence.countByG_A_ST(
article.getGroupId(), article.getArticleId(),
WorkflowConstants.STATUS_APPROVED);

if (approvedArticlesCount > 0)

{ addDraftAssetEntry = true; }

}

[Tagnaouti Boubker]

Here is a patch to solve this issue.

Hi Mark can you try this patch and let us know if it fixes the issue for you?

Thank to click on the link "Accept Contribution" if it's ok!

[Mark Jin]

Hi! Tagnaouti I tested the problem in 61x(76373). It fixed.

[James Falkner]

Hi Mark,

Please click the "Accept Contribution" button at the top to ensure this fix is incorporated in a future version of Liferay. Thanks!

[Peter Shin]

Thank you for your contribution.

Reviewed the patch and fixed it in a different way. Fix is to sync the AssetEntry expiration date with JournalArticle expiration date in JournalArticleLocalServiceImpl#updateStatus.

[Mark Jin]

PASSED Manual Testing following steps in description.

Reproduced on:
Tomcat 6.0 + MySQL 5. Firefox 5.0. 6.0.12 EE.
Tomcat 6.0 + MySQL 5. Firefox 5.0. 6.1.x Revision 86357.

Fixed on:
Tomcat 6.0 + MySQL 5. Firefox 5.0. 6.1.x Revision 86401.