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.

separating characters

Right now gloo&gl is taken as a unique identifier. Because all characters that are not a number or string are taken as as an "atom"

By saying, all latin numeric characters form one set while everything else combines as something different would translate that into 3 identifiers gloo, &, and gl.

Makes it easier for doing functions and writing the code in general

Possible changes

I'm considering two possible changes for posl.

1. Separating ascii and special characters into different groups. This would allow for a condensed form of writing the code
2. Including an EOL indicator - This would be huge change in the structure and format that's allowed