Please log a daycare ticket with desktop app logs Location of log files You can find the log files for AEM desktop app at the following locations. When uploading many assets, if some files fail to upload, see backend.log file at the above location to identify the failed uploads.On Windows: %LocalApp...

You can look into boost and search relevancy at [1] [1] https://jackrabbit.apache.org/oak/docs/query/lucene.html#boost

Refer to doc at [1] for more details: [1] https://helpx.adobe.com/ca/experience-manager/6-5/sites/administering/using/aem-as-portal.html

Modules are defined in the parent project POM file: <modules><module>core</module><module>ui.apps</module><module>ui.content</module><module>it.tests</module><module>it.launcher</module></modules> So, you can create site specific modules as per your business need in the parent POM. More details at [...

Can you log a daycare ticket with steps to reproduce the issue on a plain AEM instance and we can check internally.

 The Dispatcher Flush replication agent on the AEM publish instance must send invalidation requests to the correct Dispatcher farm. To target a farm, use the URI property of the Dispatcher Flush replication agent (on the Transport tab). Include the value of the /virtualhost property for the Dispatch...

Have you looked into using the "sling:orderBefore (String)" proeprty and update it dynamically using Sling Models? sling:orderBefore (String)Contains the name of the sibling node that the current node should be positioned in front of." More details at [1] [1] https://helpx.adobe.com/experience-manag...

They are all the same. Its basically a paragraph system that:Contains other components.Defines the layout.Responds to changes. [1] https://helpx.adobe.com/ca/experience-manager/6-3/sites/authoring/using/responsive-layout.html#AddingaLayoutContaineranditsContentEditmode

Can you check the following:- DAM Update Asset workflow is triggered when you upload an asset.- Check for any workflow related errors.- Check if other renditions for other file types are generated as expected. If this is the case, there is an issue with workflow cconfiguration.

Have you tried with the deprecations jar? uber-jar-6.5.3-apis-with-deprecations.jar [1] https://repo.adobe.com/nexus/content/groups/public/com/adobe/aem/uber-jar/6.5.3//