A quick and fast way is to perform search in CRX Content Explorer:

- Login to Content Explorer
- Click on search and select type as XPath
- Specify query that match the required information. Example:

/jcr:root/content/mysite//*[@cq:template = ‘/apps/mysite/templates/mypage’

And you can retrieve all the information .

In JSP 1

<%
request.setAttribute("title", "column1title");
request.setAttribute("links", "column1links");
%>
< cq:include script="columnlinks.jsp"/>

In JSP 2

<%
String titleAttribute = (String) request.getAttribute("title");
String linkAttribute = (String) request.getAttribute("links");
%>

CQ provides the concept of iParsys (inherited paragraph system) which allows to inherit the created paragraphs from the parent to child pages. This provides a way to author the promotional sidebar on section home pages and all the child pages gets the components automatically inherited. Sounds a good start point, but more often then not, the requirements mostly revolve around managing different promotions on different pages or different sequence of promotions based on page description etc. This limits the usage of iparsys component. Managing such promotion area’s is one of the main challenge for each implementation. Here is one of the technique we adopted in a project to provide flexible promotion management:

• Define a promotional area within content
• Define number of pages using same templates as used by actual pages where promotions need to be displayed
• Add components and setup content within promotional area pages
• Create promotion picker component to picks up promotional parsys from the promotional area page
• Add promotion picker component on actual page with a browse button to browse to page from where the promotion parsys need to be picked up

Good luck !

Happy New Year 2012

Cherishing the happy moments, learning from the difficult ones, and looking forward to a successful 2012, say Good Bye to 2011 !

May 2012 bring fun, happiness, prosperity and success to you and your family! Wish you and your family a very happy year 2012 !

In most of the websites today, we always find links to most viewed pages or top 5 most viewed pages.

CQ stores every hit on any webpage as an impression which can be seen in siteadmin.

There is no out of box component present in CQ5.4 which can be used or customized to get the impressions.

Below is the JSP code which can be used to find the most viewed/popular pages in your website.

<%@ page import=”java.util.Iterator,

java.util.ArrayList,

java.util.Collections,

com.day.text.Text,

com.day.cq.wcm.api.PageFilter,

com.day.cq.wcm.core.stats.PageViewStatistics,

com.day.cq.statistics.StatisticsService,

com.day.cq.wcm.core.stats.PageViewReport,

com.day.cq.wcm.api.WCMMode,

java.util.*,

com.day.cq.wcm.foundation.Download,

com.day.cq.wcm.commons.WCMUtils” %>

<%@ page import=”com.day.cq.statistics.StatisticsService, java.util.Map”

%><%@page session=”false” %><%

%><%@taglib prefix=”sling” uri=”http://sling.apache.org/taglibs/sling/1.0″ %><%

%><%@taglib prefix=”c” uri=”http://java.sun.com/jsp/jstl/core” %>

<%

%><sling:defineObjects/>

<%

String p_searchPath =”";

%>

<%!

int intarray[];

Set limitToFive = new HashSet();

java.util.List<Integer> arrayList = new ArrayList<Integer>();

private int calcPageViews(JspWriter outWriter,

HttpServletRequest request,

StatisticsService statService,

Page mostpopularPage) throws

Exception {

final String PARAM_PERIOD = “Period”;

 

int totalPageViews = 0;

PageManager pm = mostpopularPage.getPageManager();

 

Page statsPage = pm.getPage(mostpopularPage.getPath());

 

PageViewReport report = new PageViewReport(statService.getPath() + “/pages”, mostpopularPage, WCMMode.EDIT);

report.setPeriod(30);

Iterator stats;

 

stats = statService.runReport(report);

while (stats.hasNext()) {

Object[] res = (Object[]) stats.next();

totalPageViews = totalPageViews + Integer.parseInt(res[1].toString());

}

Iterator<Page> children = mostpopularPage.listChildren(new PageFilter(request));

while (children.hasNext()) {

totalPageViews = totalPageViews + calcPageViews(outWriter, request, statService, children.next());

}

return totalPageViews;

}

private void outputPopularHowTos(JspWriter outWriter,

HttpServletRequest request,

StatisticsService statService,

Page mostpopularPage,

String strNrMostPopular) throws

Exception {

ArrayList mostPopular = new ArrayList();

int nrFound = 0;

int nrToList = 0;

outWriter.write(“<ul>”);

Iterator<Page> children = mostpopularPage.listChildren(new PageFilter(request));

while (children.hasNext()) {

nrFound++;

Page child = children.next();

mostPopular.add(calcPageViews(outWriter, request, statService, child) + “; ” + child.getPath() + “; ” + child.getTitle());

}

if  (strNrMostPopular == null || strNrMostPopular.equals(“”)) {

nrToList = nrFound;

} else {

nrToList = Integer.parseInt(strNrMostPopular);

}

Collections.reverseOrder();

//Collections.sort(mostPopular);

if (nrFound < nrToList) nrToList = nrFound;

if (nrFound <= 0) {

outWriter.write(“<p><i>Page has Impressiosn…</i></p>”);

} else {

int cnt = 0;

//  outWriter.write(“Impressions”);

List<Integer> a = new ArrayList<Integer>();

for (int i = 0; i < nrToList; i++) {

String[] entry = null;

entry = mostPopular.get(i).toString().split(“;”);

Integer numberOfImpressions = Integer.valueOf(entry[0]);

a.add(numberOfImpressions);

if(numberOfImpressions>0){

if(cnt<15){

outWriter.write(“<li>”);

outWriter.write(“<a class=’view-more’ href=\”" + entry[1]  + “.html\”>” +”<span>»</span>” + entry[2] + “</a>”);

outWriter.write(“</li>”);

cnt++;

}

}

outWriter.write(“</li>”);

}

}

outWriter.write(“</ul>”);

return;

}

%>

<%@include file=”/libs/foundation/global.jsp”%>

 

<%

final StatisticsService statService = sling.getService(StatisticsService.class);

String queryDataPath = statService.getPath() + “/queries”;

String resultDataPath = statService.getPath() + “/results”;

 

pageContext.setAttribute(“properties”, resource.adaptTo(Map.class));

%>

 

<%

try {

p_searchPath = properties.get(“p_searchPath”, “”);

Page targetPage = pageManager.getPage(p_searchPath);

PageManager mostpopularPageManager = targetPage.getPageManager();

// get the parameters from the dialog

String rootMostPopular = properties.get(“rootmostpopular”, String.class);

Page mostpopularRootPage;

if (rootMostPopular == null) {

mostpopularRootPage = targetPage;

} else {

mostpopularRootPage = targetPage;

}

String strNrMostPopular = properties.get(“nrmostpopular”, String.class);

 

// check that we have a valid page to start from

if (mostpopularRootPage != null) {

// get children of start page

outputPopularHowTos(out,

request,

statService,

mostpopularRootPage,

strNrMostPopular);

}

} catch(Throwable t) {

log.error(“Popular ‘Most Popular – Error “, t);

}

if(p_searchPath.equals(“”) || p_searchPath == “”) {

%>

Click here to add the root page.

<%}

%>

 

 

Adding validation is one way of locking down flexibility, providing cleaner content entry environment. To extend the previous example around defining custom type with multifield, we need to add “listeners” node under multifield. Then add an attribute called “beforeadd” and specify its value as a Javascript function. As an example,

< linkspanel
jcr:primaryType="cq:Panel"
border="false"
height=""
title="Links"
width="">
< items jcr:primaryType="cq:WidgetCollection">
< links
jcr:primaryType="cq:Widget"
fieldDescription="Press + to add more links"
fieldLabel="Links"
hideLabel="true"
name="./links"
width="1000"
xtype="multifield">
< fieldConfig
jcr:primaryType="cq:Widget"
xtype="rbspathfieldwithintent"/>
< listeners
jcr:primaryType="nt:unstructured"
beforeadd="function(list,component,index){if(index!=0){var link=list.items.item(index-1).getValue();var myObject=JSON.parse(link);if(link.text==''){CQ.Ext.Msg.show({title:'Validation Error',msg:'Link Text can not be empty!',buttons:CQ.Ext.MessageBox.OK,icon:CQ.Ext.MessageBox.ERROR});return false;}if(link.url==''){CQ.Ext.Msg.show({title:'Validation Error',msg:'Link Text can not be empty!',buttons:CQ.Ext.MessageBox.OK,icon:CQ.Ext.MessageBox.ERROR});return false;}}}"/>
< /links>
< /items>
< /linkspanel>

To achieve the same, please refer to the steps below:

Within your app project, define a folder called “clientlib”. Create a text files called “js.txt” and specify the name of the js file which holds the custom xtype definition.

Example:
#base=js
CustomPathField.js

Define your js file which extends CQ.form.CompositeField and specify attributes required for the custom type. Here is an example for the same:

/**
* @class MyClientLib.CustomPathFieldWidget
* @extends CQ.form.CompositeField
* This is a custom path field with link text and target
* @param {Object} config the config object
*/
/**
* @class Ejst.CustomWidget
* @extends CQ.form.CompositeField
* This is a custom widget based on {@link CQ.form.CompositeField}.
* @constructor
* Creates a new CustomWidget.
* @param {Object} config The config object
*/
MyClientLib.CustomPathFieldWidget = CQ.Ext.extend(CQ.form.CompositeField, {

/**
* @private
* @type CQ.Ext.form.TextField
*/
hiddenField: null,

/**
* @private
* @type CQ.Ext.form.TextField
*/
linkText: null,

/**
* @private
* @type CQ.Ext.form.TextField
*/
linkURL: null,

/**
* @private
* @type CQ.Ext.form.CheckBox
*/
openInNewWindow: null,

/**
* @private
* @type CQ.Ext.form.FormPanel
*/
formPanel: null,

constructor: function (config) {
config = config || {};
var defaults = {
“border”: true,
“labelWidth”: 75,
“layout”: “form”
//”columns”:6
};
config = CQ.Util.applyDefaults(config, defaults);
MyClientLib.CustomPathFieldWidget.superclass.constructor.call(this, config);
},

//overriding CQ.Ext.Component#initComponent
initComponent: function () {
MyClientLib.CustomPathFieldWidget.superclass.initComponent.call(this);

// Hidden field
this.hiddenField = new CQ.Ext.form.Hidden({
name: this.name
});
this.add(this.hiddenField);

// Link text
this.add(new CQ.Ext.form.Label({
cls: “customwidget-label”,
text: “Link Text”
}));
this.linkText = new CQ.Ext.form.TextField({
cls: “customwidget-1″,
fieldLabel: “Link Text: “,
maxLength: 80,
maxLengthText: “A maximum of 80 characters is allowed for the Link Text.”,
allowBlank: true,
listeners: {
change: {
scope: this,
fn: this.updateHidden
}
}
});
this.add(this.linkText);

// Link URL
this.add(new CQ.Ext.form.Label({
cls: “customwidget-label”,
text: “Link URL”
}));
this.linkURL = new CQ.form.PathField({
cls: “customwidget-2″,
fieldLabel: “Link URL: “,
allowBlank: false,
width: 225,
listeners: {
change: {
scope: this,
fn: this.updateHidden
},
dialogclose: {
scope: this,
fn: this.updateHidden
}
}
});
this.add(this.linkURL);

// Link openInNewWindow
this.openInNewWindow = new CQ.Ext.form.Checkbox({
cls: “customwidget-3″,
boxLabel: “New window”,
listeners: {
change: {
scope: this,
fn: this.updateHidden
},
check: {
scope: this,
fn: this.updateHidden
}
}
});
this.add(this.openInNewWindow);

},

processInit: function (path, record) {
this.linkText.processInit(path, record);
this.linkURL.processInit(path, record);
this.openInNewWindow.processInit(path, record);
},

setValue: function (value) {
var link = JSON.parse(value);
this.linkText.setValue(link.text);
this.linkURL.setValue(link.url);
this.openInNewWindow.setValue(link.openInNewWindow);
this.hiddenField.setValue(value);
},

getValue: function () {
return this.getRawValue();
},

getRawValue: function () {
var link = {
“url”: this.linkURL.getValue(),
“text”: this.linkText.getValue(),
“openInNewWindow”: this.openInNewWindow.getValue()
};
return JSON.stringify(link);
},

updateHidden: function () {
this.hiddenField.setValue(this.getValue());
}
});

CQ.Ext.reg(‘mypathfield’, MyClientLib.CustomPathFieldWidget);

So, once we have defined that, its time to use in your component Here is snippet from dialog.xml from component:

< linkspanel
jcr:primaryType="cq:Panel"
border="false"
height=""
title="Links"
width="">
< items jcr:primaryType="cq:WidgetCollection">
< links
jcr:primaryType="cq:Widget"
fieldDescription="Press + to add more links"
fieldLabel="Links"
hideLabel="true"
name="./links"
width="1000"
xtype="multifield">
< fieldConfig
jcr:primaryType="cq:Widget"
xtype="mypathfield"/>
< listeners
jcr:primaryType="nt:unstructured" />
< /links>
< /items>
< /linkspanel>

And this is how it appear !

Example of custom xtype

suffix the url with ?debug=layout in Authoring environment

Example:

Determine CQ Components

Why not try it yourself !

<% request.setAttribute("attributeNAme", attributeValue); %>
< cq:include path="componentName" resourceType="app/components/content/componentName" />

OR

<% request.setAttribute("attributeNAme", attributeValue); %>
< cq:include script="callingJSPFile" />

Providing edit bar for a component is a clean way which could be achieved as:

cq:Component

_cq_editConfig (cq:EditConfig)

cq:actions text:edit bar name#-#edit#delete#insert

cq:layout editbar

CQ edit Config Setting

Edit Bar Example