Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

amalhotr
amalhotr
Online

Badges

Badges
7

Accepted Solutions

Accepted Solutions
2

Likes Received

Likes Received
1

Posts

Posts
13

Discussions

Discussions
3

Questions

Questions
10

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by amalhotr
Customize the badges you want to showcase on your profile
Re: AEM 6.3 Collections Search - Timeout Issue - Adobe Experience Manager Assets 15-10-2018
504 is a timeout response code; implying search query is taking too long to run. You turn on debug logs using /system/console/slinglog on package org.apache.jackrabbit.oak.query and see the query being run, the query plan & index being used to serve results. Usually /content/dam path is part of the query run in backend even if its not explicitly sent ui. I suspect the query being run in your setup is missing the path constraint, causing a timeout.

Views

1.7K

Likes

0

Replies

1
Re: AEM Assets 6.3 search bar - change from OR to AND? - Adobe Experience Manager Assets 15-10-2018
Search bar is typically doing AND across operators and text terms. Are you sure its an OR? A lot of metadata fields make part of the full text index, so even if the asset title say contains only Ford, some other metadata field might hold the keyword "car"

Views

2.0K

Likes

0

Replies

0
Re: AEM 6.2 DAM Collections. Share Link Button leads to localhost:4502 - Adobe Experience Manager Assets 15-10-2018
The issue is fixed from 6.2 SP1 CFP3 onwards; recommend installing the latest cfp https://helpx.adobe.com/experience-manager/release-notes--aem-6-2-cumulative-fix-pack.html

Views

949

Like

1

Replies

1
Re: querybuilder search on Property case insensitive - Adobe Experience Manager 21-06-2018
yeah it doesn seem to work via property map, though xpath works/jcr:root/content///element(*, cq:Page)[(fn:lower-case(jcr:content/@jcr:title) = 'hi') ]There is additonal support in oak index definitions to run such query optimally by defining function indexes [OAK-3574] Query engine: support p=lowercase('x') and other function-based indexes - ASF JIRA

Views

2.0K

Likes

0

Replies

0
Re: Permanently disable ReplicationPropertiesFilterFactory - Adobe Experience Manager 01-06-2018
For the publish date, you could use the more recent of jcr:created or jcr:lastModified on recipient server.

Views

655

Likes

0

Replies

0
Re: Catalog Producer - Adobe Experience Manager Assets 20-04-2016
rajivn76919298 wrote... ..Then i followed step "a" and "b" of your previous post. Skipped step c and d as AEM is running on localhost:4502 and Indesign server is running on localhost 8080. .. You still need to do step c) even for default setup ports for indd server & aem

Views

1.0K

Likes

0

Replies

0
Re: Version for an asset should not be created when we change Metadata - Adobe Experience Manager Assets 08-04-2016
You go to writeback step in metadata writeback workflow and change the createversion to false

Views

996

Likes

0

Replies

0
Re: Static Replication Agent ISSUE - Adobe Experience Manager 15-10-2015
Which AEM release are you using? I have failed to reproduce the problem in 5.6.1 and 6.0

Views

255

Likes

0

Replies

0
Re: Error thrown (instead of fault) when user with insufficient permissions tries to subscribe tochatmod - Adobe LiveCycle 23-02-2010
Here is the usecase. The owner is already connected to an instance of SimpleChatModel(access model=20). Now if some other user with role say 10 tries to connect I need to gracefully show the popup in my application, not the error trace that comes. I simply want to catch the error and may be show a alert box. I reiterate owner is already connected to the SimpleChatModel.

Views

439

Likes

0

Replies

0
Re: Error thrown (instead of fault) when user with insufficient permissions tries to subscribe tochatmod - Adobe LiveCycle 23-02-2010
Just to be on the safer side I tried your solution, but it didn't work. Here is the reason why, if we peruse the error trace, error is isn't thrown from ChatModel.onSynchronizationChange(). Your solution would have worked if error was thrown from this method. Had the error been thrown from this method, we could override it, catch the error and BINGO, world would have been such a happy place. But error is thrown from MessageManager.createNode() [see the trace]

Views

441

Likes

0

Replies

0
Likes from