Posts Tagged ‘wcm’


Access to Adobe CQ Package Share without Adobe CQ

March 5, 2013

I meant to post this a while back. We did an install of Adobe CQ in an environment that’s pretty restrictive with internet access and thus we were not able to connect to the Adobe CQ Packageshare website from within CQ. After a bit of digging we found the following URL:

after logging in you are able to download any of the packages on that site without accessing it through CQ.

Hope this will help others as well.


Adobe CQ Problem Clinic on November 7 2012

October 4, 2012

If you live in Orange County/Los Angeles or the San Diego area and work with Adobe CQ then bring your laptop, your project and your problems with Adobe CQ. We will have a session where you can present the problem you are having and we’ll discuss solutions for the problems and try to find a way to solve them to make your CQ implementations a success.

Adobe support personnel will be at the meetup to help us get through the issues.

We are meeting Wednesday November 7  from 6:30pm to 9pm at the Lake Forest/El Toro Public Library.

For more information about the meetup group and this event go to

Hope to see you there.


Touch Authoring Mode in CQ5.5

May 6, 2012

Since CQ5.4, communique supports a touch authoring mode. When you hit your site with either an iPhone or an iPad you will get a greatly different authoring experience in CQ. The login screen is still similar but when you hit the welcome screen you see a vastly different view:

As you can see above, the welcome screen features the ability to see your inbox and browse the content as well as some configuration tools for replication, workflows, could services and reports – all the features you want on a mobile device.

If you click on browse content you get a mobile tree explorer to navigate your sites and once you open a page, a slimmed down edit environment to review your site, make annotations, etc.

While this is all nice, the question that comes to mind is – is my current site I am working on supporting this feature? It’s a good idea to go and check if your templates still support this extra edit mode. I like to use the ‘user agent switcher’ plugin in firefox to switch my firefox to an iPhone mode and browse the authoring environment for a quick test.

To download the user agent switcher, go to


Using to parse Json Responses from Adobe CQ5.5

April 24, 2012 is a great little shell library that allows you to parse json responses from Adobe CQ. The following script is a simple example that pulls the current status of the installed, active and resolved bundles from the Felix System Console in Adobe CQ and presents the output. This can be used for example to check if the server is up and running. To use, download, put it in the same folder as this script and run it.

The supported arguments are the credentials (admin:admin) and the url to the server root (http://localhost:4502).  You should see a nice pink status line with the information on how many bundles are active, resolved and installed as well as an error code of  zero if the server is up and a -1 if the server is still starting up.

curl -s -u $1 $2/system/console > /dev/null
if [ $? != 0 ]; then
	echo admin console on $2 not running
	exit -1

. ./

DATA=`curl -s -u $1 $2/system/console/bundles/.json`

tickParse "$DATA"

#echo ``status``
#echo current status total bundles: ``s[0]``, installed bundles: ``s[1]``, installed fragments ``s[2]``, bundles resolved ``s[3]``, bundles installed ``s[4]``

if [ ``s[4]`` = 0 ]; then

	echo ``status``: server fully up
	exit 0
	echo -e "33[2A33[35m"
	echo -n ``status``: server still activating bundles
	echo -e "33[K33[0m"
	exit -1

Developing the style and templates/components in parallel for Adobe CQ5

April 10, 2012

In order to speed up development of a site within CQ5, it helps adopting the following process:

  •  Devise templates and components for the site based on mockups
  •  Implement a standard HTML for all templates and components
  •  Develop the components necessary
  •  Develop CSS/JS necessary to support the components

Using this approach, the front end team can develop the CSS/JS necessary for the site in parallel with the developers implementing the components and templates for CQ5. Instead of using a waterfall model where the front end team develops the basic HTML structure first and then provides the code to the CQ5 developers, this approach makes sure the CSS/JS works well within Adobe CQ.

To further minimize the risk of browser incompatibilities and to make sure the site will also look good on mobile devices from the start, it helps adopting a basic CSS/JS framework, commonly known as grid systems.

Some grid systems to consider are:

The grid systems have a well known html structure and features such as reflow that help on smaller screens. Developing your components with a grid system in mind will also make sure the developed components can be reused in the future with a different stylesheet and make your CQ5 projects faster to implement and easier to adopt to a new site style and new features provided by the grid system.

The Adobe CQ5.5 version uses 960gs for the default geometrixx site, however, choosing twitter bootstrap will provide you with more out of the box functionality commonly found on today’s website.

update: we released a bootstrap templating integration for Adobe CQ 5.5 today. See the following link for more information


Adobe CQ5.5, first impressions

March 10, 2012

Adobe recently released a new version of it’s content management suite, now called CQ5.5 again – there was an effort to rebrand it last year to WEM but that seemed not to go over that well and was quite confusing.

The new version of CQ comes with a much better integration into the Adobe digital marketing suite (Omniture, Test & Target, Scene 7, etc) and there seems to be quite some work that has been done under the hood.

This slideshow requires JavaScript.

CQ5.5 now comes as two distributions, a WAR file that can be deployed into any JEE servlet container as well as a standalone version that runs in the apache felix OSGi container – CQ used to be distributed as 2 war files with an embedded servlet container and to get to run it in any other container there was quite some work involved.

Unfortunately, the new release also has some downsides especially for system administrators. Lots has changed and it seems some of the features that were there before got lost. For example, you used to be able to just rename the jar file and drive the type of server (author instance or publish instance) as well as the port CQ would run on from the name (cq-publish-4503.jar would make it run on port 4503 as a public instance). Now, this feature only works if you start the jar file directly (java -jar cq-publish-4503.jar) but the installed service scripts, such as start and stop to control the server from an init.d script for example are now hardcoded to run an author on port 4502 (the default instance).

It seems the best way to install CQ5.5 at the moment is to do the following:

java -jar cq5- -unpack

this will just unpack CQ into a subfolder crx-quickstart. Once that’s complete, start modifying the files in crx-quickstart/bin. You want to change the port, the run mode (type of instance you’re running) and the memory settings.

The following few lines will change the settings for you (replace $NEWPORT, $RUNMODE and $MAXMEM with your desired configuration settings:


sed -i.old "s/4502/$NEWPORT/" crx-quickstart/bin/*
sed -i.old "s/author/$RUNMODE/" crx-quickstart/bin/*
sed -i.old "s/-Xmx1024/-Xmx$MAXMEM/" crx-quickstart/bin/start*

Your basic start., stop and quickstart scripts should be modified, starting and stopping CQ can now be done by executing these commands on linux or mac


on windows, you can just use


Note of advice: make sure you use Java6 and not Java7, there are still some problems with CQ on Java7 it seems.

Also visit updated-init-script for cq5.5 for an init script that works with cq5.5