Fórum
Urgent Issue: Knowledge base EE portlet
Frank Wang, modificado 6 Anos atrás.
Urgent Issue: Knowledge base EE portlet
New Member Postagens: 7 Data de Entrada: 12/02/16 Postagens Recentes
Hi, everyone:
We have published thousands of articles into Knowledge base porltet. However, there are issues when we want to import the lar file into another Liferay region.
Version Liferay: 6.2 EE.
Knowledge base portlet: 6.2.10.5
Issue #1: If I manually import the lar file with all the articles into another region, I have to clear up the same folder, even though I have tried all the importing options. I think it should overwrite or merge the same article into the same folder.
Issue #2: Usually, if I import the web content into another region, the media url should be also changed. for example, <img src="/documents/205455/263737/logo.png/58a0bf29-0ca4-49f7-aa2f-bb2f14e8d15b?t=1490026450347"> will be changed to <img src="/documents/142040/269164/logo.png/58a0bf29-0ca4-49f7-aa2f-bb2f14e8d15b?t=1490026450347"> , which means, the group Id will be changed to the current region automatically. But, after I import, the group Id doesn't changed. This really matters, because the link would be 404. The reference of the source can not be updated.
Thanks everyone in advance. Our project is going to prod, if this is a bug by liferay knowledge base, it could be a disaster for us.
We have published thousands of articles into Knowledge base porltet. However, there are issues when we want to import the lar file into another Liferay region.
Version Liferay: 6.2 EE.
Knowledge base portlet: 6.2.10.5
Issue #1: If I manually import the lar file with all the articles into another region, I have to clear up the same folder, even though I have tried all the importing options. I think it should overwrite or merge the same article into the same folder.
22:15:17,875 ERROR [liferay/background_task-1][BackgroundTaskMessageListener:133] Unable to execute background task
com.liferay.portal.kernel.lar.PortletDataException: com.liferay.knowledgebase.DuplicateKBFolderNameException: A KB folder with name drivers already exists
at com.liferay.portal.kernel.lar.BaseStagedModelDataHandler.importStagedModel(BaseStagedModelDataHandler.java:175)
at sun.reflect.GeneratedMethodAccessor1114.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.liferay.portal.kernel.bean.ClassLoaderBeanHandler.invoke(ClassLoaderBeanHandler.java:67)
at com.sun.proxy.$Proxy605.importStagedModel(Unknown Source)
at com.liferay.portal.kernel.lar.StagedModelDataHandlerUtil.importStagedModel(StagedModelDataHandlerUtil.java:340)
at com.liferay.portal.kernel.lar.StagedModelDataHandlerUtil.importStagedModel(StagedModelDataHandlerUtil.java:330)
at com.liferay.portal.kernel.lar.StagedModelDataHandlerUtil.importReferenceStagedModel(StagedModelDataHandlerUtil.java:230)
at com.liferay.portal.kernel.lar.StagedModelDataHandlerUtil.importReferenceStagedModels(StagedModelDataHandlerUtil.java:318)
at com.liferay.knowledgebase.admin.lar.KBArticleStagedModelDataHandler.doImportStagedModel(KBArticleStagedModelDataHandler.java:185)
at com.liferay.knowledgebase.admin.lar.KBArticleStagedModelDataHandler.doImportStagedModel(KBArticleStagedModelDataHandler.java:1)
at com.liferay.portal.kernel.lar.BaseStagedModelDataHandler.importStagedModel(BaseStagedModelDataHandler.java:164)
at sun.reflect.GeneratedMethodAccessor1114.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.liferay.portal.kernel.bean.ClassLoaderBeanHandler.invoke(ClassLoaderBeanHandler.java:67)
at com.sun.proxy.$Proxy605.importStagedModel(Unknown Source)
at com.liferay.portal.kernel.lar.StagedModelDataHandlerUtil.importStagedModel(StagedModelDataHandlerUtil.java:340)
at com.liferay.portal.kernel.lar.StagedModelDataHandlerUtil.importStagedModel(StagedModelDataHandlerUtil.java:330)
at com.liferay.knowledgebase.admin.lar.AdminPortletDataHandler.doImportData(AdminPortletDataHandler.java:137)
at com.liferay.portal.kernel.lar.BasePortletDataHandler.importData(BasePortletDataHandler.java:327)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.liferay.portal.kernel.bean.ClassLoaderBeanHandler.invoke(ClassLoaderBeanHandler.java:67)
at com.sun.proxy.$Proxy602.importData(Unknown Source)
at com.liferay.portal.lar.PortletImporter.importPortletData(PortletImporter.java:191)
at com.liferay.portal.lar.PortletImporter.importPortletData(PortletImporter.java:1018)
at com.liferay.portal.lar.PortletImporter.doImportPortletInfo(PortletImporter.java:533)
at com.liferay.portal.lar.PortletImporter.importPortletInfo(PortletImporter.java:210)
at com.liferay.portal.service.impl.LayoutLocalServiceImpl.importPortletInfo(LayoutLocalServiceImpl.java:1895)
at com.liferay.portal.service.impl.LayoutLocalServiceImpl.importPortletInfo(LayoutLocalServiceImpl.java:1963)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:115)
at com.liferay.portal.service.impl.LayoutLocalServiceVirtualLayoutsAdvice.invoke(LayoutLocalServiceVirtualLayoutsAdvice.java:183)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.service.impl.LayoutLocalServiceStagingAdvice.invoke(LayoutLocalServiceStagingAdvice.java:141)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.transaction.DefaultTransactionExecutor.execute(DefaultTransactionExecutor.java:62)
at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:51)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:175)
at com.sun.proxy.$Proxy35.importPortletInfo(Unknown Source)
at com.liferay.portal.service.LayoutLocalServiceUtil.importPortletInfo(LayoutLocalServiceUtil.java:1385)
at com.liferay.portal.lar.backgroundtask.PortletImportBackgroundTaskExecutor.execute(PortletImportBackgroundTaskExecutor.java:61)
at com.liferay.portal.kernel.backgroundtask.SerialBackgroundTaskExecutor.execute(SerialBackgroundTaskExecutor.java:56)
at com.liferay.portal.backgroundtask.messaging.BackgroundTaskMessageListener.doReceive(BackgroundTaskMessageListener.java:108)
at com.liferay.portal.kernel.messaging.BaseMessageListener.receive(BaseMessageListener.java:26)
at com.liferay.portal.kernel.messaging.InvokerMessageListener.receive(InvokerMessageListener.java:72)
at com.liferay.portal.kernel.messaging.ParallelDestination$1.run(ParallelDestination.java:71)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask._runTask(ThreadPoolExecutor.java:682)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask.run(ThreadPoolExecutor.java:593)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.liferay.knowledgebase.DuplicateKBFolderNameException: A KB folder with name drivers already exists
at com.liferay.knowledgebase.service.impl.KBFolderLocalServiceImpl.validateName(KBFolderLocalServiceImpl.java:267)
at com.liferay.knowledgebase.service.impl.KBFolderLocalServiceImpl.addKBFolder(KBFolderLocalServiceImpl.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:115)
at com.liferay.portal.spring.transaction.DefaultTransactionExecutor.execute(DefaultTransactionExecutor.java:62)
at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:51)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:175)
at com.sun.proxy.$Proxy592.addKBFolder(Unknown Source)
at com.liferay.knowledgebase.service.KBFolderLocalServiceUtil.addKBFolder(KBFolderLocalServiceUtil.java:346)
at com.liferay.knowledgebase.admin.lar.KBFolderStagedModelDataHandler.doImportStagedModel(KBFolderStagedModelDataHandler.java:108)
at com.liferay.knowledgebase.admin.lar.KBFolderStagedModelDataHandler.doImportStagedModel(KBFolderStagedModelDataHandler.java:1)
at com.liferay.portal.kernel.lar.BaseStagedModelDataHandler.importStagedModel(BaseStagedModelDataHandler.java:164)
... 57 more
Issue #2: Usually, if I import the web content into another region, the media url should be also changed. for example, <img src="/documents/205455/263737/logo.png/58a0bf29-0ca4-49f7-aa2f-bb2f14e8d15b?t=1490026450347"> will be changed to <img src="/documents/142040/269164/logo.png/58a0bf29-0ca4-49f7-aa2f-bb2f14e8d15b?t=1490026450347"> , which means, the group Id will be changed to the current region automatically. But, after I import, the group Id doesn't changed. This really matters, because the link would be 404. The reference of the source can not be updated.
Thanks everyone in advance. Our project is going to prod, if this is a bug by liferay knowledge base, it could be a disaster for us.
David H Nebinger, modificado 6 Anos atrás.
RE: Urgent Issue: Knowledge base EE portlet
Liferay Legend Postagens: 14916 Data de Entrada: 02/09/06 Postagens RecentesFrank Wang:
We have published thousands of articles into Knowledge base porltet. However, there are issues when we want to import the lar file into another Liferay region.
As an EE customer, have you opened a corresponding LESA ticket?
Frank Wang, modificado 6 Anos atrás.
RE: Urgent Issue: Knowledge base EE portlet
New Member Postagens: 7 Data de Entrada: 12/02/16 Postagens Recentes
Not yet. I am wondering if I can get help by here quickly.
Frank Wang, modificado 6 Anos atrás.
RE: Urgent Issue: Knowledge base EE portlet
New Member Postagens: 7 Data de Entrada: 12/02/16 Postagens Recentes
Thanks David. Aren't my issues common?
David H Nebinger, modificado 6 Anos atrás.
RE: Urgent Issue: Knowledge base EE portlet
Liferay Legend Postagens: 14916 Data de Entrada: 02/09/06 Postagens Recentes
Well, I'm not sure how many folks actually use the knowledge base. I know that lar export/import in general can be a pain, but I would not be surprised if few have actually encountered this issue.
At least if you get a LESA ticket opened, Liferay support can start looking at the issue and may be able to provide a fix if another client has already reported this or would work on it otherwise.
At least if you get a LESA ticket opened, Liferay support can start looking at the issue and may be able to provide a fix if another client has already reported this or would work on it otherwise.
Frank Wang, modificado 6 Anos atrás.
RE: Urgent Issue: Knowledge base EE portlet
New Member Postagens: 7 Data de Entrada: 12/02/16 Postagens Recentes
Ok. gotcha. Thank you very much.