Adobe Experience Manager Sites

Indexing In AEM — Oak Indexing by Manu Mathew Abstract An index is a data structure used to locate and access data from AEM quickly. It generally uses JCR queries to search and retrieve the contents. Indexing is used to increase the performance of the query and reduce the overhead on AEM i.e it improves the speed of data retrieval operations. In cases where the frequency of the queries that are executed is less and the content to be searched is less, then we could ignore indexing. Oak supports the indexing of content that is stored in the repository. Oak supports Lucene-based indexes to support both property and full-text constraints. If multiple indexes are available for a query, each available indexer estimates the cost of executing the query. Oak then chooses the indexer with the lowest estimated cost. Synchronous Indexing: Here, the index content gets updated as part of the commit itself. The changes made to both the main content and index content are done in a single commit. H

AEM | Custom XMP Metadata Writeback by Suman Shekhar Jana Abstract The XMP writeback feature lets you propagate the metadata changes to all or specific renditions of the asset. The feature writes back only those metadata properties that use registered namespaces. In this blog, we will discuss briefly the OOTB feature available in AEM in the first section. In the second section, we’ll discuss a possible use case of customization and how we can customize it. And finally, in the third section, some approaches & implementation methods that an AEM/Java developer must avoid during development which shall help understand the reason for using the approach discussed in the second section. Section A: OOTB XMP Metadata Writeback We have the XMP writeback feature readily available in AEM for use with OOTB DAM Metadata Writeback workflow which comes with a set of predefined parameters. There also exists a launcher to trigger this workflow. Read Full Blog AEM | Custom XMP Metadata Writeback Q

AEM Effective Pagination with Query Builder API by Sourcedcode Abstract There are many ways to implement pagination for AEM content. Effectively choosing the right solution will indeed Bu decrease development time, and promote a performant experience to your end users. AEM has multiple search API’s like xPath, JCR SQL2, Node JCR, Query Builder, etc… But in my opinion, the Query Builder API would be the most effective decision when building a solution with pagination. In AEM, the Query Builder API has emerged as the preferred solution for creating pagination experiences. In this article, we will explore why the Query Builder API stands out as the go-to choice for pagination in AEM. 1. Understanding Pagination in AEM What is pagination? In general, pagination is a process that divides large sets of content into smaller, more manageable sections, commonly referred to as “pages”; but however, with AEM, anything can be paginated. By doing so, users can navigate through content easily, wit

Creating a custom component in AEM by Mircea Dumitrescu Abstract Adobe Experience Manager (AEM) is a content management system that allows developers to create, manage, and deliver digital experiences across different channels. In AEM, developers can create custom components to fulfill any specific business requirement. A custom component is a modular unit which is created to perform a specific task in a webpage. Creating a custom component involves the following steps: Create the component folder and files A component in AEM is represented by a node in the repository, which is essentially a folder with a predefined structure. Let’s say we are creating a “Card” component, which will consist of an image, a title, and a description. We will also provide the option for the content author to choose between a light and dark theme. Navigate to the directory where you want to create your custom component (for example, “/apps/myapp/card”). Create a new folder for your component (for exam

hi team, We are having 'mvn clean test' command on our pipeline to run the unit testing code. But with the latest maven archetype since ui.apps have dependency on ui.frontend and ui.apps.structure it is failing. We are unable to move to next step. Any way to resolve this issue. Failed to execute goal on project project-aem.ui.apps: Could not resolve dependencies for project com.project.cms:project-aem.ui.apps:content-package:0.0.1-SNAPSHOT: The following artifacts could not be resolved: com.project.cms:project-aem.ui.frontend:zip:0.0.1-SNAPSHOT, com.project.cms:project-aem.ui.apps.structure:zip:0.0.1-SNAPSHOT: Could not find artifact com.project.cms:project-aem.ui.frontend:zip:0.0.1-SNAPSHOT -> [Help 1]

we are using Aem 6.5.16, we have login implementation using an OOTB authentication handler.We are able to login from the publisher instance but not through the dispatcher. We can see that the login-token cookie is getting set on the publisher, not in the dispatcher. we have allowed all the required configurations at the dispatcher level.  Please suggest.

I'm trying to modify the dialog (content.xml) for our navigation Experience Fragment, but I made a change and reverted it, but get this error now:Cannot serve request to in /libs/granite/ui/components/coral/foundation/form/field/field.jspException:java.lang.NullPointerException at com.adobe.granite.ui.components.impl.BaseComponentHelper.include(BaseComponentHelper.java:519) at com.adobe.granite.ui.components.ComponentHelper.include(ComponentHelper.java:675) at com.adobe.granite.ui.components.ComponentHelper.include(ComponentHelper.java:652) at com.adobe.granite.ui.components.ComponentHelper.include(ComponentHelper.java:610) at org.apache.jsp.libs.granite.ui.components.coral.foundation.form.multifield.render_jsp.include(render_jsp.java:59) at org.apache.jsp.libs.granite.ui.components.coral.foundation.form.multifield.render_jsp._jspService(render_jsp.java:318) at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServl

No text available

Hello all! Currently we have developed a custom TextTransformer that replaces some constants in the html.  We have noticed that this transformer is not working when personalization is applied to the page and it's loading a variation (The master variation is working ok) We are using context hub for personalization.  Any hint how to solve this? Thank you.

In our project there is header experience fragment(xf) and inside that we have authored Header component. This header component internally adds experience fragment component using data-sly-resource and path to our experience fragment component. We are authoring path of notification XF into this experience fragment component. I deployed this code in dev and stage server and there I can author path of notification XF into this experience fragment component but same thing is not working on stage. I am getting Unknown validation error as belowanyone know why this is happening? Appreciate your help.

Content pages are blank after upgrading the AEM instance to AEM service pack 6.5.15

In our project (AEMaaCS SPA Editor) we see that empty divs are getting generated for all the components. OOTB and custom.     I tried installing the WKND project, and the issue is reproducible in WKND as well for all components.     Any ideas on why this is added or how to fix this? 

Is it possible to filter the en.model.json before the fetch?  Our json is large, and want to remove extraneous key/values, specifically the "allowedComponents" that returns a long list of components for every page and appears to be the majority of bloat in the response:[":children"]["/content/my-app/us/en/my-page"][":items"].root.allowedComponents.components Perhaps there are query parameters or some other way to return a smaller json response? I found this tutorial that allows modifying the fetch - although I'm not certain it would be useful in this case: http://experience-aem.blogspot.com/2021/09/aem-cloud-service-pass-request-parameters-in-react-spa-model-json-url.html

Hello Guys, I wanna know the method to customize the actions when invalid error occurred in widget js code, anyone knows?

I am working with AEM 6.2 local instance. Here the Configuration Browser is missing. Can someone guide me on how to enable it so that I can create Editable templates? I would really appreciate it if someone helps me.

Hi, I am creating a email template in AEM classic ui. When I first access the template the component in the sidekicks shows. Once I reload or refresh the page, the components in the sidekicks does show. I was thinking it was a caching issue so I went into our server and remove the widget.min.js file but that didn't work. 

We have Adobe Managed Services AEM 6.5 with AEM Guides add-on 4.3.  We're noticing that user preferences are not persisted across a user's session (e.g., pick a different Folder Profiles value and save, then exit Guides and come back in to find the default Global Profile selected).  Is this the expected behavior, or should the preferences be saved for the duration of the session (or even across different logins)?  Any thoughts as to why the changes are not being saved? I am relatively new to AEM and Guides, so not sure what the expected behavior is and if this is a bug in our setup.  

Hi, gentlemen.I have the following scenrio:The website has hundreds of pages, and each of them need a vanity URL. This is because the content structure on AEM does not match the expected end URLs (eg.: on content tree the page will be at /content/<site>/<lang>/<product type>/<country>/<state>/<city>/<page> while the URL will be /<city>/<page> or even /<marketing-stuff>/<another-page-name>).Those vanities must not contain extension (eg.: .html).This scenario leads me to two problems that I'd like to ask for your help or advice:As I'll have new vanities each day, following the recommendation on http://dev.day.com/docs/en/cq/current/deploying/dispatcher/disp_config.html that states "depending on how restrictive your filter configuration is, you may need to explicitly register each individual vanity URL. In the following example /my/vanity/url" is not an option for me.Instead of (on the dispatcher) deny access to all URLs fo

Is there a Out of the Box way or ACS Commons utility to get a report of all User groups in AEM?I saw something in ACS Commons for getting the list of users here - etc/acs-commons/exporters/usergroupstagelist.html, but not for user group.

We have a group of a creative user and we want to give permission for only check-in check-out to dam assets without showing menu option like edit, delete and other options as well. So how we can achieve this without overlaying or customization of OOB component.

I need to perform not like operation to get "PDK_" non matched values from DAM.But i don't get any idea.Some site provide reference to use "not" opertion.but not will give only empty value only.i need not matching number values also.Kindly help to for this.and also tried with unequals.My Query:type=dam:Assetpath=/content/dam/p.limit=-1property=jcr:content/metadata/UniqueProductIDproperty.operation=notproperty.value=%PDK_%

 

Hi,we have a requirement in which we have to disable the move functionality for pages under certain path in siteadmin . Below is screenshotIs there any configuration to disable it ? can anyone help

Hey Guys, I want to know the difference between White board pattern and Scheduler API for scheduled execution of the code. Which method is preferred ? Please help me.  

Hi All, I have a requirement that i have to capture multifield add and delete them and make ajax call after modification and capture fields. i am using a ajax call inside dialog-success function. It is working fine for adding multifields, but failing for delete. Whenever i delete any entry and save the dialog, it captures deleted entry too. It looks like node structure is not getting updated after delete operation.   Any help is appreciated.   Thanks,