Product Communities

HI All,Have a requirement of using Search core component and enhance its functionality to meet few business logic.Could anyone let know the process to make core functionality to work on page for searching a text in a component content and provide the results matching it. Also let know on how steps to be followed to enhance Search capabilities.Thanks in Advance.

EDIT:Figured it out!  The problem is in my /private/etc/hosts file.  For whatever reason, certain processes were not respecting this file - specifically maven and other build tools such as Angular CLI (trying Angular is how I ultimately picked up on what was happening).  In short, "localhost" was not resolving to 127.0.0.1 when running maven install.  It was instead resolving to nonsense IP's (a few different ones actually).  The tricky part was that "localhost" did correctly resolve in the browser or when running terminal commands such as telnet/curl manually.  If this hadn't been the case the problem would have been super obvious.  But in any case my hosts file had the "127.0.0.1       localhost" entry like you'd expect so something else was up.  I added a new line like "127.0.0.1       localhost2" to see if this resolved correctly, and it did not.  Not in maven, angular, the browser, or te

I am seeing a lot of odd spikes in direct traffic to pages I would not expect to see direct traffic and at the same time, I am see search traffic to those same pages fall. Is there a way to QA if traffic is being correctly classified? Thanksml

Hi All, Used Social Media share Core component available in AeM 6.4 & 6.5 vanilla instances. Created and authored proxy component of it on page, enabled properties on Social Media Tab of page & 'View as published' but icons of FB, Pinterest are not visible.Installed Core components 2.9 + versions package as well & try the same but still the issue of icons are not show-up on page.Anything else needs to be done, to make it work. Inputs would be really appreciated. Below is observed as per log:*ERROR* [[0:0:0:0:0:0:0:1] [1633509295176] GET /content/we-retail/us/en/men.html HTTP/1.1]org.apache.sling.scripting.sightly.render.ObjectModel Cannot access method metadata on object com.adobe.cq.wcm.core.components.internal.models.v1.SocialMediaHelperImpl@4b48ddf2java.lang.reflect.InvocationTargetException: nullat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at su

Next up, the REST API, which is, relatively speaking, a new thing. The custom object parts of the REST API are documented on the developer blog on their own separate page, and in my opinion it makes sense to monitor that page for changes so you know when the API has new features added.For the purposes of this, I'll be referencing the Automobile object that I created in part 1 of this series, and I'll be using Postman to make my REST calls. (note you can read about use of the SOAP api in Part III of the series) Here's what it looks like:Create/Update Custom ObjectsRequest491-XYZ-299.mktorest.com/rest/v1/customobjects/automobile_c.json?access_token=3471-4804-afd9-e9925fd632f9:sjjSON Payload{  "action": "createOrUpdate",  "dedupeBy": "dedupeFields",  "input": [    {      "bodystyle": "Coupe",      "color": "Silver",      "make": "Hyundai",      "model": "Sonata

Use this thread to ask any questions related to the Understanding Real-time CDP for Audience Manager Users course on Experience League. Experts are monitoring this thread to ensure your questions are answered.

Existing technotes have been grouped and added to the new Technote section and a Hardware sizing recommendations page has been updated and added to the Technotes section as well.    Read here for more details:  Hardware Sizing Recommendations   Please feel free to reach out in case you have any questions through the below comment section.

Hi All,Need to create Product Carousel proxy component. How to create it and refer has we won't find in core components list apart from carousel. Can anyone let me on it How to proceed on it.

window["Coral"]["templates"]["RichTextEditor"]["InputPlugin"] = (function anonymous(data_0 /**/) {  var frag = document.createDocumentFragment(); var data = data_0; var el13 = document.createElement("div"); el13.style.display = "table-cell"; el13.style.vertical_align = "middle"; el13.style.padding = "0.25rem"; el13.style.line_height = "2.375rem"; el13.className += " rte-dialog-columnContainer"; var el14 = document.createTextNode("\n "); el13.appendChild(el14); var el15 = document.createElement("div"); el15.className += " rte-dialog-column"; var el16 = document.createElement("label"); var el17 = document.createTextNode(" "); el16.appendChild(el17); var el18 = document.createElement("input","coral-textfield"); el18.style.z_index = "10000 !important"; el18.setAttribute("is", "coral-textfield"); el18.setAttribute("data-action", "munged"); // el18.setAttribute("data-type", "hu"); // el18.setAttribute("value", ""); el16.appendChild(el18); var el19 = document.createTextNode(" "); el16.ap

AEM - Creating a New Template by Adobe Abstract When creating a page you need to select a template. The page template is used as the base for the new page. The template defines the structure of the resultant page, any initial content and the components that can be used (design properties). This has several advantages: Page Templates allow specialized authors to create and edit templates. Such specialized authors are called template authors Template authors must be members of the template-authors group. Page Templates retain a dynamic connection to any pages created from them. This ensures that any changes to the template are reflected in the pages themselves. Page Templates make the page component more generic so the core page component can be used without customization. With Page Templates, the pieces that make a page are isolated within components. You can configure the necessary combinations of components in a UI, thereby eliminating the need for a new page component to be develop

Cutting Through the Noise: What is the Adobe Marketing Cloud CDP? by Ryan Greene Abstract The customer data platform (CDP) market is confusing — but it doesn’t have to be. This is part 1 in a series of blog posts exploring different types of CDP vendors, how their products differ from other technologies and what you can do to select the right CDP for your enterprise company. The Adobe Marketing Cloud CDP is among the most well known in terms of brand recognition, as Adobe is a legacy brand with a long history of providing software for printing and publishing. But being well known is not the same as being well understood. The Adobe Marketing Cloud, of which the Adobe CDP is one product offering among many, operates similarly to other marketing clouds. It’s a portfolio of point solutions brought together under one roof. Marketing cloud point solutions — which are often the result of vendor acquisition — are ostensibly designed to operate on their own, but this isn’t always the case in

User synchronization in AEM by Sanjay Kushawaha Abstract When AEM deployment topology is multi-publishers or publish farms based and deployed websites have features like user’s registration then there occurs a need of synchronizing the user’s data on each publishers. This is also applicable when you create the user using https:///security/users.html OR https://useradmin options and want that user account to be replicated on different publishers available in publish farms. This synchronization is generally required because once an individual user register that registration request may go randomly to any one of the publish instance of publish farms and during next login session that user request may go to another publisher in the publish farms. If we do not synchronize the user registration data on all publish instances, then on another publish instances that user would appear as a new user and again registration need to perform by that user thus this creates bad user experience. Below

Fast Facts — AEM Best Practices Analyzer (BPA) by Sanjay Kushawaha Abstract The Best Practices Analyzer (BPA) which earlier known as Cloud Readiness Analyzer is used to assess the AEM project code implementation by indicating areas that are not following the best practice guidelines of AEM as a Cloud Service (AEMaaCS). By using the report generated by BPA you can identify the potential code refactoring areas that need to be fixed before deploying it to AEMaaCS. Let’s understand the flow by referring below diagram. Important considerations for BPA It is supported on AEM instance 6.1 or above and can be run by admin or user having administrator rights. It can be downloaded from Adobe Software Distribution Portal and install on AEM Author using Package Manager. Once installed it can be accessed by following the path Tools → Operations → Best Practices Analyzer. Read Full Blog Fast Facts — AEM Best Practices Analyzer (BPA) Q&A Please use this thread to ask the related questions.

Example Use Case for Real-time Customer Data Platform B2B Edition by Adobe Abstract Real-time Customer Data Platform B2B Edition expands the existing Real-time CDP and Adobe Experience Platform offerings to support B2B data and workflows. This document provides an example use case that demonstrates the additional benefits provided by the B2B Edition. They include: Combine person and account data from different siloed data sources to produce a comprehensive view that enables a better understanding of the customers and more accurate segmentation. See the documentation on creating XDM schema relationships for use with varied B2B sources for more information. Segment an audience based on attributes of related entities. This includes Accounts, Opportunities, Campaigns, and Marketing Lists. Segments are no longer limited to just Person attributes and Experience Events. See the B2B segmentation documentation for more examples of creating B2B-specific audiences. Natively support the use case

AEM(Adobe Experience Manager): Extend Experience Fragment model to support localized header/footer with custom site structure by Albin Issac Abstract One of my earlier blogs talked about how to reuse the same editable templates with multiple sites, how to use the XF localization feature to enable different headers and footers for the websites build on the same template — there are multiple approaches to achieve this e.g. dedicated template for sites, enabling the header at page level rather in template level but we enabled the header in template level and used the localization feature to support the header variants. Refer to the following URL for more details — How To Reuse Editable Template With Multiple Sites — Adobe Experience Manager(AEM)? The XF localization feature works well if the content(/content/mysite1/us/en) and experience fragment(/content/experience-fragments/mysite1/us/en) structures follows the same pattern. Recently we had a use case to reuse the pages created with

Hi all, I am currently working with trying to get a folder full of content fragments through the assets api, and am able to access this folder no problem on author instance (Gives me the full JSON with all files inside) but after publishing everything (Folder, content fragments, and content fragment model) and trying this URL on our publish server gives a 404 error. I've tried with just a single content fragment in a different folder and it gives the same 404 error. The file clearly exists as the file shows it has been published, so I am wondering if it is some sort of issue with permissions?  As a note, on my local instance it was working on author + publish instance (Could access the folder on both) but once we deployed to our dev server something seems to have changed.  Please let me know if you have any ideas as to why this might be happening.

Photoshop and Adobe Experience Manager: Accelerating creativity through APIs by Adobe Blogs Abstract Today, we are thrilled to announce that we have created the most powerful connection yet between Creative Cloud and Experience Cloud by integrating Adobe Photoshop and Lightroom’s world-class imaging technology natively into Adobe Experience Manager Assets, a platform used by the world’s top brands to manage and store hundreds of millions of assets. By bringing the power of Photoshop directly to where the assets live, creative and marketing teams can now automate image editing on a massive scale, applying complex operations such as background removal, smart object replacement and even scripting through Photoshop Actions to thousands of files with a single click. Imagine you’re an art director responsible for creating a myriad of product images for online and print catalogs. Instead of having to manage multiple workflows for different audiences and deliverables, you can now create all

So confused with this issue... Running AEM 6.5.2 with Components 2.9.0 and Java 1.8.0. We were originally using a newer version of components, but had to downgrade them and the Java version from 11 to 8 and, things were seemingly working perfectly fine, but the Accordion won't work in publisher with this showing in the console: Uncaught TypeError: Cannot read properties of undefined (reading 'container'). We did have a cq error before that, but I added <sly data-sly-call="${clientlib.js @ categories='cq.widgets'}"/> to the customheaderlibs.html to make sure it was grabbing those.On top of that, the Carousel won't work either anymore on any install, which wasn't an issue until we downgraded and added the 6.5.2 service pack, but we are getting no error for that component at all. It's as if the buttons are all just dead. I find it hard to switch between any of the components I add as well to slide through, so it may be a clientlib issue? Just not sure what to do

Use this thread to ask any questions related to the Data Ingestion for Data Engineers course on Experience League. Experts are monitoring this thread to ensure your questions are answered.    

Get Started with XML Documentation by Adobe Abstract Get Started with XML Documentation Learn how to create, organize, author, and publish content with XML Documentation for Adobe Experience Manager. What you'll learn: Understand the XML Documentation user interface Create and structure content with the repository view and XML Editor Work with images Add web-links to your content Work with bulleted and numbered lists Version your content Create and organize a map Publish a map as an AEM Site and PDF Lesson 1 Introduction Learn the basics of XML Documentation. Lesson 2 Understanding the Exprience Manager User Interface Learn about managing assets, files, and folders in the XML Editor for Experience Manager. Lesson 3 Creating and Structuring Content Begin creating and structuring content in the XML Editor Repository. Create folders, subfolders, and begin adding content to a Concept topic. Lesson 4 Authoring Content Learn how to author content in XML Documentation for Adobe Experien

Getting Started with AEM Sites for Business Users by Adobe Abstract Getting Started with AEM Sites for Business Users Explore the basics of AEM Sites, including navigation, how site pages are organized and stored, along with how to creating a page for your site. Lesson 1 The Basics Explore the basics of AEM Sites, including navigation, how site pages are organized and stored, along with how to creating a page for your site. Lesson 2 Authoring Basics Explore the basics of page authoring in AEM sites, including an introduction to Page Editor's UI tools, adding content to a page, along with how to create responsive content for your site. Lesson 3 Authoring Features Explore some of the page authoring features in AEM sites, including an introduction to Page Editor's UI tools, adding content to a page, along with how to create responsive content for your site. Lesson 4 Publishing and Managing Explore some of the basic page management operations including publishing a page, page edit op

Getting Started with AEM Sites for Developers by Adobe Abstract Getting Started with AEM Sites for Developers An introduction to the basic concepts and technology involved in an AEM Sites implementation. Important topics of component development, local runtime, Core Components, and the AEM Project archetype are covered. What you'll learn: AEM and authoring basics The underlying AEM technology How to set up a local development environment How to create your first AEM website AEM Developers Lesson 1 Introduction An introduction to the course Getting started with AEM Sites for developers. Learn about the target audience, course structure, and topics covered in this course. Lesson 2 The Basics An introduction to the basic concepts and technology involved in an AEM Sites implementation. Important topics of component development, local runtime, Core Components, and the AEM Project archetype are covered. Lesson 3 Underlying Technology Learn about the technologies of OSGi, JCR, Oak, and

Getting started with Multi-Site Management for Business Users by Adobe Abstract Getting started with Multi-Site Management for Business Users Introduction to the Getting Started with Multi-Site Management for business users course. Lesson 1 Introduction to Multi-Site Management Introduction to the Getting Started with Multi-Site Management for business users course. Lesson 2 Live Copy Explore the basics of creating a multinational and multilingual site for your organization using AEM Sites' multi-site management capabilities like Language Copy, Live Copy, and Blueprint. Lesson 3 Language Copy and Translation Learn how to use AEM Sites' translation features and capabilities to create, manage, and translate your site's content for different regions. Lesson 4 Create a site Learn how to create a multinational, multilingual site for your organization using Language Copy, Live Copy, Translation Jobs, and other multi-site management capabilities of AEM Sites. Read Full Blog Getting start

Getting started with AEM SPA Editor for developers by Adobe Abstract Getting started with AEM SPA Editor for developers Learn how to build highly performant Single Page Applications (SPAs) that can be authored in AEM with the AEM SPA Editor. This course covers the major development tasks from creating a new SPA Editor Project all the way through building custom components. Equivalent lessons for Angular and React frameworks are provided; it is expected that most developers will choose a single framework to use. Lesson 1 Introduction Getting started with the AEM SPA Editor course covers the major development tasks from creating a new SPA Editor Project all the way through building custom components. Equivalent lessons for Angular and React frameworks are provided. Lesson 2 SPA Editor Basics Get an introduction to the SPA Editor feature in Adobe Experience Manager. Understand the basics behind how the SPA Editor empowers authors to dynamically edit content for a SPA. Lesson 3 Devel

AEM 6.3.1.2 with Dynamic Media EnabledHello Adobe Community,This is my first posting here . . . I hope I'm doing it correctly . . . here is my question, I hope someone can help!When we enabled Dynamic Media, it automatically installed two log files in <cq-installation-dir>/crx-quickstart/logs/:s7access-<yyyy>-<mm>-<dd>.logImageServer-<PortId>-yyyy>-<mm>-<dd>.logAs with our other log files, for each of these dynamic media log files, a new one is added each day (the documentation refers to this as "rotating").For each of the other (non-dynamic media) log files, only the 7 most recent files are kept.  But for our dynamic media log files, the number that is kept is not limited to 7; the dynamic media log files just keep accumulating.Can someone please share the secret for how the number kept of the Dynamic Media log files be configured in AEM? Or is the only way to manage it ourselves, such as by setting up a chron job to zip up and or delete ol