That looks ok to me. That is how the standard feed also would look like in CQ/AEM.You ARE creating a RSS feed and you get the desired output. The RSS links (eg. somerandomsite.com/blogs/myblog/2/februaryblog.feed.xml) are not supposed to show a nice looking html site and chrome will certainly not tr...

Hello Punith,the structure of a normal RSS feed is xml like (http://www.rssboard.org/rss-specification) and you do not have to create a html version. Some web browsers however have the native ability to translate that into something that looks like html straight away (like Firefox). Usually, when su...

Hi Mahesh.Could you please elaborate on the question?/Johan

Ok,well since you already are using the jcr:title the thing you have to do now is to follow the steps in the link (and the excerpt that I posted above) and register that jcr:title as a metadata property for images. Otherwise, there is no way for the assets method getMetadata() to know what other met...

Hi,first of would it not be better to use the title metadata that is already there (dc:title) ?Since you probably have your reasons for not doing so it could be possible to reach the metadata that you have created if you read this article.http://dev.day.com/docs/en/cq/current/dam/metadata_for_digita...

Hi Debal.Are you trying to find all assets in the DAM and paginate those (and then show their individual metadata) ?If so, the QueryBuilder API would work just great here. The following creates a new map of the search predicates and adds the path to the dam and the type to "dam:Asset". Map<String, S...

Hi !You definately don't need to have the author and the publish instance on the same server. Within the author, you simply browse to the replication settings. There you will find settings for the publish instance (http://localhost:4502/etc/replication/agents.author/publish.html) The default setting...

Hi there,As Scott mention. There is a direct and hardcoded way of doing this by different mapping that will handle the requests for a page so you don't even get to that page in the first place. This of course could be a bit annoying if these pages change from time to time and that is something that ...

I have used the following predicate in the java for the Query Builder, I have the date-range and the path in there, can that be of any use ? /* Some code.. */ HashMap<String, String> map = new HashMap<String, String>(); map.put("path", MY_PATH); map.put("type", "nt:unstructured"); map.put("property"...

Hmm, thats strange.You should be able to work with multiple daterange properties like such:map.put("daterange.p.or","true"); map.put("daterange.1_property","@jcr:content/event_par/event/recurrence/rule/until"); map.put("daterange.2_property","@jcr:content/cq:lastModified"); map.put("daterange.lowerB...