Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Web contents are not visible under control panel

Written By

Sivakumar Perumal

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • Exporting the site from one server to another server results in web contents are not visible with the below error in console. However, could see when searching through its article id.
     
    2020-06-03 13:24:20.490 ERROR [http-nio-9080-exec-2][IncludeTag:128] Current URL /en/group/missingassetentry/~/control_panel/manage?p_p_id=com_liferay_journal_web_portlet_JournalPortlet&p_p_lifecycle=0&p_p_state=m
aximized&p_p_mode=view&_com_liferay_journal_web_portlet_JournalPortlet_displayStyle=list&p_p_auth=ZAFlHnn5 generates exception: com.liferay.asset.kernel.exception.NoSuchEntryException: No AssetEntry exists with th
e key {classNameId=28801, classPK=47990}
com.liferay.asset.kernel.exception.NoSuchEntryException: No AssetEntry exists with the key {classNameId=28801, classPK=47990}
	at com.liferay.portlet.asset.service.persistence.impl.AssetEntryPersistenceImpl.findByC_C(AssetEntryPersistenceImpl.java:3654)
	at com.liferay.portlet.asset.service.impl.AssetEntryLocalServiceImpl.getEntry(AssetEntryLocalServiceImpl.java:297)
	at com.liferay.portal.kernel.bean.ClassLoaderBeanHandler.invoke(ClassLoaderBeanHandler.java:66)
	at com.liferay.asset.kernel.service.AssetEntryLocalServiceWrapper.getEntry(AssetEntryLocalServiceWrapper.java:604)
	at com.liferay.portal.kernel.bean.ClassLoaderBeanHandler.invoke(ClassLoaderBeanHandler.java:66)
	at com.liferay.portal.spring.aop.AopMethodInvocationImpl.proceed(AopMethodInvocationImpl.java:50)
	at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:69)
	at com.liferay.portal.spring.aop.AopMethodInvocationImpl.proceed(AopMethodInvocationImpl.java:57)
	at com.liferay.portal.spring.aop.AopInvocationHandler.invoke(AopInvocationHandler.java:49)
	at com.liferay.asset.kernel.service.AssetEntryLocalServiceUtil.getEntry(AssetEntryLocalServiceUtil.java:583)
	at com.liferay.asset.kernel.model.BaseAssetRendererFactory.getAssetEntry(BaseAssetRendererFactory.java:60)
	at com.liferay.depot.web.internal.asset.model.DepotAssetRendererFactoryWrapper.getAssetEntry(DepotAssetRendererFactoryWrapper.java:68)
	at com.liferay.journal.web.internal.servlet.taglib.util.JournalArticleActionDropdownItemsProvider._getPreviewURL(JournalArticleActionDropdownItemsProvider.java:518)
	at com.liferay.journal.web.internal.servlet.taglib.util.JournalArticleActionDropdownItemsProvider._getPreviewArticleActionUnsafeConsumer(JournalArticleActionDropdownItemsProvider.java:489)
	at com.liferay.journal.web.internal.servlet.taglib.util.JournalArticleActionDropdownItemsProvider.getActionDropdownItems(JournalArticleActionDropdownItemsProvider.java:115)
	at com.liferay.journal.web.internal.display.context.JournalDisplayContext.getArticleActionDropdownItems(JournalDisplayContext.java:204)
	at org.apache.jsp.view_005fentries_jsp._jspService(view_005fentries_jsp:1048)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:411)

Environment

  • Liferay DXP 7.2

Resolution

  •  The above issue is a known issue LPS-114855 in Liferay DXP 7.2.

Workaround: Changing the display style for the Web Content page to Cards would help to make web content visible.
CardsView.png

Resolution: The issue is resolved in fix pack dxp-6-7210. Please create a support ticket if a hotfix is required.
NOTE: This fix applies only to the newly importing lar files. For old site lar, it requires an additional step to make the web content visible in all views. i.e. Once the fix pack/hotfix is installed on the server where the site lar is going to be exported, do find and update the web contents that are found missing on the imported site. Then exporting the new site lar and importing it into another server should work.
 

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?