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 - 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

Forecasting EB-2/EB-3 Green Card Filing Dates - Machine Learning Model

In this blog post, we'll explore the process of forecasting Green Card filing dates using a simple linear regression model in Python. By analyzing historical data from the United States Citizenship and Immigration Services (USCIS), we can use basic machine learning techniques to predict future filing dates. I will walk you through the process step-by-step. Gathering Data:    To begin our journey, we need to gather relevant data. You can collect data from USCIS or other trustworthy sources. This dataset should include essential information such as the visa category, country of chargeability, and the final action date for each month. For this use case, I collected data manually from USCIS visa bulletin for India EB-2 and EB-3 categories. Data looks like this - Visa bulletin - Building the Linear Regression Model:    Using Python libraries like scikit-learn, we can construct our linear regression model. This simple yet powerful algorithm will help us forecast Green Card...
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