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 ...

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"

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

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=lower...

For the publish date, you could use the more recent of jcr:created or jcr:lastModified on recipient server.

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

You go to writeback step in metadata writeback workflow and change the createversion to false

Which AEM release are you using? I have failed to reproduce the problem in 5.6.1 and 6.0

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 a...

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 meth...