If users forget to unlock the pages and you want other users to be able to edit those pages then you can consider the following solution- Implement a scheduled background job which will scan the content paths for the locked pages and send reminders by email to the users to unlock the page if the pag...

May be while testing you might have added the contactform node directly under cq:Page node rather than under cq:PageContent node - /content/geometrixx-outdoors/en/TestPage/contactform 

Also, It will be good to fire this query on cq:PageContent node type to limit the number of results returned- SELECT parent.* FROM [cq:PageContent] AS parent INNER JOIN [nt:unstructured] AS child ON isdescendantnode(child,parent) where isdescendantnode(parent, [/content/geometrixx-outdoors]) AND  LO...

You can add a condition in your JS function to not to execute if the path is not specific to the project. CQ.WCM.getPagePath() will give you the path of the page in the javascript function. 

You shouldn't be including javascript on the pages for dialog or any authoring related customizations. Rather you should create a JS client library and define category property of the client library node to "cq.widgets" for classic UI and "cq.authoring.dialog" for touch UI. Examples-For touch UI - /...

One more point to add IS NULL check returns true only if the property does not exists on that node. So if the property does exist on the node and we need to check the value as blank then following condition should be used-child.[id] IS NULL OR child.[id]=''

If the property is stored as string in JCR then why are you reading it as date in the JCR API-Calendar cal = Calendar.getInstance(); String date = node.getProperty("date").getString() SimpleDateFormat formatter = new SimpleDateFormat("yyyy-MMM-dd"); Date dateObj = formatter.parse(date); cal.setTime(...

Sh1ju wrote... @ Jitendera ,Its already versionable.please check the screen shot    The versionable mixin is applied on jcr:content node whereas in your code you are trying to do the operation on mm1 node which may not have the mixin. 

I would go with option 1 as in principle you use maven to build the artifacts only once when you deploy on DEV and then for higher environments you should deploy the same built artifacts. Building the artifacts again is not recommended as you only want the verified and tested artifacts to be deploye...

Here is the JCR SQL2 query for this use case- SELECT parent.* FROM [cq:Page] AS parent INNER JOIN [nt:unstructured] AS child ON ISDESCENDANTNODE(child,parent) WHERE ISDESCENDANTNODE(parent, [/content/xxx]) AND  LOCALNAME(child) = 'contactform' AND  child.[id] IS NULL