Adobe Experience Manager Sites

Hi AllAEM Linkshare functionality when multiple assets within a folder is shared and downloaded, the assets are inside another sub-folder instead of all assets directly inside the parent/root folder. Is this a recent change in OOTB Link share functionality?Is there a configuration to download all assets in the same root folder instead of respective sub-folders?For example, DAM folder /content/dam/test has assets a.jpg & b.jpg, when folder test is shared via Share Link functionality to an author and downloads the folder, then extracts it to find folder with name a.jpg and b.jpg inside these folders, assets a.jpg and b.jpg exists.The expected result is directly inside extracted folder test, the assets a.jpg and b.jpg must be available. Is this possible?

You can give a Teaser, like the rest of the core components an arbitrary ID, which also shows up in the data layer. This is useful for identifying the things you'd like to track. Unfortunately this only happens at the component level. For something like a CTA that can be added to a Teaser component, an ID is generated.You can see an example of this on wknd.site. If I inspect the teaser on the first slide on the home page.....you can see its ID, "teaser-2122a9f81a-cta-6b28b693be"The first part, teaser-2122a9f81a" can be arbitrarily changed by adding an ID to the teaser in question. But can the second part be altered somehow?If I look at the even generated in the data layer when this is clicked, I again see this ID.But this doesn't seem like a great ID to identify an obvious clickable item; an arbitrary, intuitive ID would be much better. What are people doing when a site owner comes and says they want an analytics report for the View Trips button clicks? Does a developer have to do

Metadata schema where we are using the Generic list to load the drop downs . A generic list with all options was created. Pasting the generic list path in the schema settings under “Add Manually” populates all options correctly.Problem: After saving the metadata schema , options do not persist vanish.Observation: Issue occurs only when the dropdown contains more than ~1,000 options. Smaller lists work as expected.Visibility and choices rules can only be configured after the dropdown options are populated and saved.Please assist me how I can save more than1000 value in list

Hi Team,I am having a requirement, such that I should be able to select multiple values from a drop-down in Content fragments in AEM.I tied as is from this blog, but was unsuccessful :https://blogs.perficient.com/2021/05/27/how-to-extend-content-fragment-model-data-types/  Can you look at the blog and say, if anything is missing from the post. Or can you give any recommendations / solutions.

Does anyone in this community manage to set up their AEM/ Assets 6.5 Managed Service Shared Link? Any tips?

I’m trying to understand experience fragments and how I can use them on our customer portal site. Our content authors would like the ability to build them in our main site authoring environment that is on AEMaaCS. The portal site is Ionic/Angular and has different CSS and JS than our AEM site.Where I’m having difficulty is understanding how the clientlibs of our main site can be used. Is this something that needs to be handled by the link rewriter for experience fragments based on a specific experience fragment template so that the correct domain is used? Something like what is discussed on this page about Target offers? Or am I overthinking this?https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/configuring-and-extending/experience-fragments#default-link-rewriting

Is there a way to use Asset Renditions ( mobile, tablet or custom) in Image component  AEM Authoring( instead of uploading assets for each breakpoint in the component)Trying to optimize the authoring process here. Please share best practice.

I have an issue with some inconsistent behaviour in the UI when navigating though pages which can often lead to a longer period of time trying to achieve what I set out to do.Scenario:An AEM Author has asked if a certain page (in this case a staff profile page) has any references so it can be safely unpublished and/or deleted.I know the format of the URL and Page name so I use the search function. However, when you get the results, you cannot open any reference panel to check references to that page.But if you have the time and patience to scroll through 1000s of profile pages through the usual column view, use ALT+3 to open references and check on the page required you do get the information needed.What I have to do is:Find the page via search queryOpen the page as if I was editing itOpen the Page Information menuChoose "View in Admin"Which still doesn't take me to the actual file, it takes me to the parent folder which I then scroll through 100s (to put my rant in context, this is a

Hi Community,I’ve restricted access to /content/dam/secure/ using ACLs, which work fine on Author, but after replication the assets are still accessible on Publish via direct URLs.What is the recommended best practice in AEM as a Cloud Service to ensure DAM assets remain secure on Publish - ACL replication, CUGs, Dispatcher filters, or another approach?

Hi,Can we use Microsoft OpenJDK11 with AEMaaCS  for our local setup? Does this have any issue with the long term code run or its safe to use? 

Hi All, I could see a clear difference between html page source and current DOM structure of the same html page. I need to fetch current DOM structure (mouse right click and inspect option in browser) of the page. Would like to know if there is any API in java or FE js?I tried making http call but all those are giving html source of the page. Any help is highly appreciated.  Thanks,Pradeep

Hi All, EDS spreadsheet content is accessible with json extension in url. I have a requirement to fetch doc page content in the form of json. Is there any way I can access? Manually replacing the extension to json throwing 404 page not found. Thanks,Pradeep

Hi Everyone,I'm currently adding a custom stopwords.txt file to my custom Lucene index in AEM to filter out common stopwords during search. While most of the words in my list are being excluded as expected, I've noticed that some very common ones like "are", "was", and "that" are still being indexed and returned in search results.My stopwords.txt file includes all of these terms (one per line), and I’ve confirmed the file is correctly referenced in the analyzer configuration for the index.I’m wondering if anyone else has experienced this issue? Is there anything I might be missing related to:File encoding or formatting of the stopwords.txt file?Analyzer or tokenizer order/configuration?Case sensitivity issues even with ignoreCase = true?Possible overrides by other filters or analyzers?Any suggestions or shared experiences would be greatly appreciated!Thanks in advance!

Hello Community,We are in the process of setting up the integration between AEM and Adobe Target. Could you please let me know which PIDs I need to use to create OSGi configs so that they are deployed as part of the code? Additionally, there are some existing configs that were created manually. I want to ensure that these existing configurations are not overwritten and that the new config is added as part of the deployment. Security -> Adobe IMS ConfigurationsAdobe IMS Technical Account ConfigurationCloud Services -> Legacy Cloud Services -> Adobe Target Configurations 

Hi Everyone, We are running AEM 6.5 on-premise (AMS) and recently noticed that our Publish pages are automatically including the following script tag:<script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js" data-routing="p00000-e000000"></script> ObservationsThe script is not present in Author mode.It is always injected in Publish output.We confirmed it by hitting the publish instance directly (bypassing dispatcher and CDN) using curl:curl -s -D- https://publish1apsouth1-XXXXX.stage.bajajfinance.adobecqms.net/en | grep rum.hlx This returns the script element, meaning it is injected inside Publish itself.AnalysisThe script is not authored in our page templates, HTL, or clientlibs.Searching /apps and /libs in CRX/DE gives no matches for rum.hlx.page or helix-rum-js.This indicates the injection is not content-based, but done by an OSGi bundle or service active only on Publish.From documentation, I found this

I am new to AEM and learning it. One implementation I want to learn is to integrate Adobe analytics with the AEM 6.5? How can I integrate Adobe Analytics with the AEM 6.5 ? Can you please guide me in the simple way from scratch ? Thanks !! 

hi all, my aio-cli version is not upgrading even after running the command "npm install -g @adobe/aio-cli"Here's the log below -  nkrish@SYSMACH io runtime action % npm install -g @adobe/aio-clinpm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fsnpm warn deprecated readdir-scoped-modules@1.1.0: This functionality has been moved to @npmcli/fsnpm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.npm warn deprecated debuglog@1.0.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.npm warn deprecated read-package-json@6.0.4: This package is no longer supported. Please use @npmcli/package-json instead.npm warn deprecated npmlog@5.0.1: This package is no longer supported.npm warn deprecated @npmcli/move-file@2.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are weaving AI into their workflows securely, responsibly, and at scale. You'll walk away with: Getting legal & security approvals faster Prioritizing the right use cases Building trust for safe AI experimentation Can't attend live? No problem, register anyway, and we'll send you the recording after the event!   Register here: https://engage.adobe.com/scaling-aI-adoption.html