There is no direct way to create that. At my work I faced the same requirement and I went following way: 1. Created a servlet2. Created an html input field where the user can type in the path.3. Created a query that looks for type "dam:Assest" in given path.4. Collected and iterate through all found...

I solved it by going a different way: I created an extra css file with value "overflow:unset". After that I added the recently created css file to clientlib category "coralui3", by creating an extra .content.xml with following content<?xml version="1.0" encoding="UTF-8"?><jcr:root xmlns:cq="http://w...

I could find the problem and a solution for it. A simple display:inline solves the problem. My question: what is the name of catogory of clientlibs so the gui for page properties accept this? By the way: the "cosmetical problem" occurs also in we-retail project, so it is a general bug.

How can I achive that, that my own css will be applied to page properties dialog?

As I wrote "since AEM 6.3" this issue exists in AEM 6.4 und 6.5 either. And it is a little bit annoying.

In my projects I used often the component granite/ui/components/coral/foundation/form/selectSince AEM 6.3 there is an issue that this granite component looks differently when you include it into a dialog for page properties and in dialog for a component. Here the look in page properties: (This is no...

I get a "Page not found" message. The ".html" is missing in posted link.

I don't understand what your requirements exactly are. As far as I understand your prictures -whose shows your structure- the marked tags are a part of full path from others. So there is no other way. May be the keyword 'contains' allows you to avoid der percent signs. My above query would looks lik...

 SELECT * FROM [cq:PageContent] AS page WHERE ISDESCENDANTNODE(page ,"/search/in/path") AND NOT (page.[cq:tags] like "dsc:keywords%" or page.[cq:tags] like "dsc:device%") Due to the fact that the information is saved in jcr:content node, you have to work with this resource.

I could figure out that was an issue with missing content index and too many subnodes.