We are facing one more issue in our publish environment.We created runmodes for publish instance,  in one of my publish run modes my HTMLLibraryManagerImpl.config is coming as nt:file.How we can give permanent solution for this. Temporary fix : we copied from another publish instance.

Hi,Thanks for the reply.Is the same procedure for 5.6.1 version.Please let me know

We can rename the cq.jar, it will start to work.but in which file it will start to write the configuration and where can see the file.What is the path to see the file.Please help me to understand the background process

Try to get the property like thisTitle : <%=currentNode.getProperty("jcr:title").getString()%>

Hi Nishadh,Try to give entire path in resource typeEx : <cq:include path="mynode" resourceType="myapp/components/somecomponent" />

We are not using any DAM assets.We installed the package in QA environment and we seen this error. Package we have taken from our Int environment.

Yes, we missed this node(36a0dc54-c432-459c-bc7e-c353c25baca3) in jcr:version storage But how it missed that we are trying to find root cause for this problem.Any suggestion , how it may miss that node.We will open support ticket too.

16.05.2015 12:51:46.463 *WARN* [10.146.229.133 [1431795091288] POST /crx/packmgr/service.jsp HTTP/1.1] com.day.jcr.vault.fs.impl.io.DocViewSAXImporter error while checkout node (ignored) javax.jcr.ReferentialIntegrityException: Target node 36a0dc54-c432-459c-bc7e-c353c25baca3 of REFERENCE property d...

Thank you for the reply.I will read it.

I got the error as broken version history.i am not sure how to find why my version history got broken.