Skip to main content

Using currentNode with design dialog

I'm doing a simple CQ include which includes my component.

<cq:include path="banner" resourceType="generic/components/content/banner" /> 
 
But instead of using a content dialog I am using a design dialog. I understand the design dialog properties are all stored under /etc/designs/default. So if I try to access the current node object I.E. use:

<%= currentNode.getName() %> 
 
I get a null pointer exception.

The currentNode object contains the resolved JCR Node for the request. Since you are using design dialog, you will be able to access the The design of the addressed resource using the currentDesign object. And in order to access the properties stored in the design dialog you can use the currentStyle object.
currentStyle.get("prop_name");  currentDesign.getId(); 
 
Refer to Style api and Design api for information on the methods available.

Since we have the currentStyle object, we can get the path of the style from that and then use the Session object to get the node from that path. After that you can perform all the node operations on it.

Session session = resourceResolver.adaptTo(Session.class); 
 if(session.nodeExists(currentStyle.getPath())) { 
 Node node = session.getNode(currentStyle.getPath()); 
 node.getIdentifier(); 
 }

Comments

Post a Comment

Popular posts from this blog

AEM 6.3 - How to extend Granite UI

Here in this article, I am going to explain how to extent Granite UI that is basically used to create AEM 6.x consoles. There can be various use cases where in you may need that. In our case, author wants to take all the page creation requests through AEM instead of email communication. Authors are basically looking for a form in AEM authoring console so that requestor can login and submit page creation/Asset upload request. Overall requirement is - Need a link in Navigation so that author can click on it and go to a Intake form. Author must be able to fill and save the intake requests. Author must be able to see the history of submitted intake requests Able to see the details of submitted intake requests. Solution - 1. Create a following structure - /apps/cq/core/content/nav/form and add the details given in below screenshot - You basically need to add - href, title and icon. Href is the path of page where user will land on clicking it.  Af...
Post a Comment
Read more

CQ Page Properties from Javascript

To get CQ page properties inside javascript you can use core CQ JS API. It can be convenient if you need to get this information inside your custom JS widgets.              var pageData = CQ.HTTP.get(CQ.HTTP.externalize(CQ.utils.WCM.getPagePath() + "/jcr:content.json")); After that you can retrieve any property you need (assuming it's present in JCR):              var resourceType = pageData ? CQ.Util.formatData(CQ.HTTP.eval(pageData))['sling:resourceType'] : null; Please do not overuse it because it invokes additional ajax call to server. It's OK to use it in edit mode on author instance. Copied from -  http://adobecms.blogspot.com/2014/04/cq-page-properties-in-javascript.html
Post a Comment
Read more

AEM 6.3 - Check if page is published or not

If you want to know if the page is published or not you can use the below utility method to know if the page is published or not. Steps - Take Resource Object. Adapt it to Page Adapt page to ReplicationStatus, you will get the status Here is the code - public static Boolean isPublished(Resource resource) { Boolean activated; ReplicationStatus status = null; activated = false; if (resource != null) { try { Page page = resource.adaptTo( Page.class ); status = page.adaptTo( ReplicationStatus.class ); } catch (Exception e) { LOG.debug(e.getMessage (), e); } if (status != null) { activated = status.isActivated(); } } return activated; }
Post a Comment
Read more