Hi there Amit,You can sort the entries by their property: "jcr:created".The query for this (you can e.g. check in the debugger) would be: path=/content/mysite/ type=cq:Page orderby=@jcr:content/jcr:created orderby.sort=descOr if you want it in java code: Map map = new HashMap(); map.put("path", "/co...

This is how it could be done:On the dispatcher server, in the vhost you'll have to have this://........... in the VHOST file RewriteRule ^/$ /content/mysite/en/start.html [PT,L] RewriteCond %{REQUEST_URI} !^/apps RewriteCond %{REQUEST_URI} !^/content RewriteCond %{REQUEST_URI} !^/etc RewriteCond %{R...

The pattern seems to be wrong, have you tried with "/content/brand/:/brand" and "/content/mobile/:/mobile". One way of doing it would be to have like "/content/mybrand/-/" and "/content/myotherbrand/-/". That worked for me.Good Luck/Johan

Sounds like the usage of backbone.js in combination with AEM would be a great idea here IMO.http://backbonejs.org/http://recipeswithbackbone.com/This could solve the update problems that you are thinking about with and MVC kind of thinking and special event handlings.Good Luck/Johan 

Hello,good points from Justin there.What you would do is to create the user groups in the LDAP corresponding to the groups in CQ. Eg. have a group in the LDAP that is named "supergroup". Then when the first user belonging to that group is logging into CQ, that group will also be created in CQ. Set t...

Hi,it will be difficult to use this since you can't really have several elements on a page with the same id (or you can but definitely should not).You need to create a unique id for each element if you want to user getElementById. Otherwise it will just pick the first element with that id on the pag...

Thats quite strange, have tried it both in 5.6 and 5.5 with the exact code i wrote above and it works fine :SIs there anything indicating that there might be something wrong in the OSGi console about the servlet ?Now the logs clearly points out that the servlet handling your request is not your serv...

Take a look at this: http://adobe-consulting-services.github.io/acs-aem-commons/features/errorpagehandler.htmlWorks perfect and can be used in combination with setting the correct error pages in the dispatcher configurations in the vhost files.Good Luck/Johan

Can you please elaborate a bit on the error messages.Would be great to see what it is complaining about in the js files.Try to clear the var cache and your browser cache and see if the problem dissapears./Johan

Ah thats nice to hear, probably just something that was not updated correctly :)