stopping the CQ5 linkchecker from validating a link

If you want a specific link to not be validated by the linkchecker just insert the following property into the <a> tag

 x-cq-linkchecker="skip"

Converting the multifield to use something other than text

The traditional use of the multifield is to allow users to enter a number of text fields, which are then stored all in one location in the jcr.

However the type of component that is rendered is identified by the fieldConfig property. Which defaults to a text field.

Here is a sample structure to support changing the default type to a drop down selection;

{
  "xtype": "multifield",
  "name": "./shadow",
  "fieldlabel": "stuff",
  "jcr:primaryType": "cq:Widget",
  "fieldConfig": {
    "xtype": "selection",
    "type": "select",
    "jcr:primaryType": "nt:unstructured",
    "options": {
      "jcr:primaryType": "cq:WidgetCollection",
      "o1": {
        "value": "google",
        "jcr:primaryType": "nt:unstructured",
        "text": "google"
      },
      "02": {
        "value": "yahoo",
        "jcr:primaryType": "nt:unstructured",
        "text": "yahoo"
      }
    }
  }
}

Removing a CQ lucene index

Sometimes bad things happen in CQ and the only way to correct the problem is to remove the lucene index.

• Go to ./cq-quickstart/repository
• Search for directories named index
• Move, rename, or delete, as appropriate
• restart your cq instance

bad path element "": no such file or directory

According to Google this is usually a problem that occurs when a class path is defined in a manifest file that no longer exists.

In my case, I got this compiling with maven, it occurred when I had changed a reference to a method from an instance call to a static call and failed to commit the associated change to the repository.

Modifying the landing page in Adobe CQ5

Recently got a request to modify the CQ5 landing page so only certain items appeared for authors when they logged in.

The landing page is divided into 4 sections. To change what appears we need to use the group control to set permissions on the specific nodes that are being represented on the landing page.

The right side sections are the easiest. These are defined as child nodes of the following;

/libs/cq/core/content/welcome/resources (section 2)
/libs/cq/core/content/welcome/docs (section 3)
/libs/cq/core/content/welcome/features (section 4)

Just go in and set the relevant read permissions for the group on these child nodes and voila, the page is modified.

The core list that appears on the left is a little bit trickier.

What's appearing is a list of resources that have the mixin type applied to them of cq:Console, sorted in descending order by their sling:vanityPath

To find all the items, go into crxde and perform an xpath search of
/jcr:root//*[@jcr:mixinTypes = 'cq:Console']

And following up on this, if you were to look at any of the nodes. You can easily extend your content by including the cq:Console mixin type and have this appear on your landing page.

Realized the existing jar file on the download site is extremely old. The language has changed syntax since that inception and I need to get a new one out soon

I have a second person working on the code. That's an odd experience, it's sharing something that you've been working on for so long. It's hard not to take it personal at times. Fortunately the new guy is good.

Has decent ideas and is taking it in directions I wouldn't have thought of. Which is is the whole point.