Hi,What do you mean by above statement. Do you want to show it on footer html ?If you are trying to read the last modified date of footer node. Just add the below code in your footer component:Last Updated on ${'dd-MM-yyyy' @ format=properties['jcr:lastModified']} (or)Last Updated on ${'dd-MM-yyyy H...
There is nothing much in the above code, it should have worked. We are just trying to read the attribute from properties and adding it to the html.Anyhow that's not right approach and I just tried to go through the coral code in detail and realized we can use as below:granite:class - String - classn...
Hi Sandhya,You can create the dialog as below to get the nearest as per your requirement.Dialog xml:<?xml version="1.0" encoding="UTF-8"?><jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www...
Hi Manju,Here it seems like you are trying to declare 3 variables are trying to use it later in the code.But this to work correctly all the three declarations should have true or some string values.Wherever a variable is evaluated to false, the flow will stop and next variable will not be intialized...
Hi Vishwanath,The below code is not present in coral UI components, whereas its present in granite ui components. May be there is a reason they removed it. I have not used coral UI yet.// Start of attrs compatibility; please use cmp.populateCommonAttrs(attrs).attrs.add("id", cfg.get("id", String.cla...
This is very basic question.Make a habit of looking into documentation before asking a question here. Check the documentation for other properties as well.Field — Granite UI 1.0 documentation
You need to include the Jquery in your component itself and dynamically pass the value to the jqueryYou need the write some back end service WcmUsePojo class to read the config.if you already have service where configuration is already read. You can use that service here.I hope you are taking about ...
Below are few of the things you might need to consider.You might have to clean up deprecated code from backend.Pom update and there might be chances that some code might not work completely. You might have to fix it.As you are coming 5.5, you will have classic dialog components and it will work fine...