Adobe Experience Manager Sites

I have a minimal amount of DAM assets under source control (~30 images). These correspond to some "test" content that is used for the local development loop- basically a handful of pages and components that always deploy out on every compilation. I am noticing that every image under source control actually gets quite a few renditions. Is it safe to omit these from source control, or are they required for the system to function properly?  Will they be regenerated automatically or leave everything in a semi broken state? For example, let's say I have a file: icon.png. This is resulting in the following source control structure:/dam/icon.png/.content.xml/dam/icon.png/_jcr_content/renditions/cq5dam.thumbnail.48.48.png/dam/icon.png/_jcr_content/renditions/cq5dam.thumbnail.48.48.png/.content.xml/dam/icon.png/_jcr_content/renditions/cq5dam.thumbnail.140.140.png/dam/icon.png/_jcr_content/renditions/cq5dam.thumbnail.140.140.png/.content.xml/dam/icon.png/_jcr_content/renditions/cq

 When adding a page for translation with target language en_gb, the source path is automatically set with en-gb instead of en_gb and translated page is created under en-gb. It seems like AEM is picking the first matching language in Sites, instead of correctly identifying the actual language code. 

Hi, I am trying to setup a local AEM instance with docker. So far I was able to setup a Author, Publish and dispatcher. But I only have issues with setting up the JVM remote debugging. I am able to connect the JVM debugger it is just not stopping at the breakpoints. This is the setup :Dockerfile : FROM openjdk:11WORKDIR /opt/aemEXPOSE 4502EXPOSE 5005COPY author-p4502.jar /opt/aem/author-p4502.jarCOPY start.sh /opt/aem/start.shCOPY install /opt/aem/install/RUN chmod +x /opt/aem/start.shCMD ["/opt/aem/start.sh"]Docker-compose.yml :version: '3.8'services:aem-author:build:context: ./authorcontainer_name: aem-authorports: - "4502:4502" - "5005:5005"environment: - AEM_RUNMODE=author - JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005volumes: - ./author/crx-quickstart:/opt/aem/crx-quickstartaem-publish:build:context: ./publishcontainer_name: aem-publishports: - "4503:4503"environment: - AEM_RUNMODE=publishvolumes: - ./publish/crx-quickstart:/opt/aem/crx-

I have a checkbox and a textfield. If the checkbox is checked the textfield is an required field. If the checkbox is not checked the textfield is not required. It works fine when changing the page properties of an existing page. I can only save the page if I filled the textfield when the checkbox is checked and I can save it when the checkbox is not checked and the textbox is not filled.But if I creat a new page the changing of the checkbox has no effect to the create Button.The validation works I can see that the required textbox changes if I check or uncheck the checkbox. That meens the red corner appears and diappears and in the HTML I see the "required".But the create Button is grey until I first add something into the textfield. I can then remove it an save the page no matter if I added something in the required textfield or not. So there is the flag: required but the create button do not really works correctly. So how can I "add" the "refresh" of the "create Button" if

Hello, I am using Language Wire for translations and I wanted my custom references to CFs to be automatically translated. Therefore I added the following config to translation_rules.xml with a property name and resource type to a custom component.<assetNode assetReferenceAttribute="contactList" checkInChildNodes="false" createLangCopy="true" resourceType="my-project/components/content/components/group-contacts/v1/group-contacts"/>The component resource type matches and the property contactList contains a string linking to a CF (/content/dam.../my-cf).However, this doesn't seem to be working and my referenced CF doesn't great translated. What am I missing?  BR,Daniel

Publish to Brand portal doesnt work for Non-Admins inspite of having read, modify and replicate permissions. This used to work earlier with same set of permissions for non admin users but suddenly stopped working after the oct 2024 brand portal release - https://experienceleague.adobe.com/en/docs/experience-manager-brand-portal/using/introduction/brand-portal-release-notes. The same set of permissions allows the same user to publish to dynamic media but publish to brand portal doesnt seem to work.

Hi all, Generally consultants offer Roadmap to the client, in their implementationIs there an example of an Adobe Roadmap (sequence of different projects) with some reasonable justification?Ex: One brand going live and all others follow, and Cloud Migration. For example, how could we justify the sequence?"One brand going live and all others follow" is fully justifiable. What about Cloud Migration? Appreciate all your replies. Thanks,RK.

We are using AEM as a cloud service version 6.5.19.0 and ACS AEM Commons version 5.0.2. We are facing issues with the Dispatcher flush feature and the MD5 hash that is getting added to the client libraries after deploying JS or CSS changes. To fix both issues, we are planning to upgrade the ACS Commons version to 6.10.0. Can anyone help me with the best considerations to avoid any potential issues? Also, if you have faced any issues post-upgrade, please share your experience.

We have a requirement to authenticate the backend api , so how can we Implement OAuth 2 in AEM as client. Thanks 

We are trying to set the cookie userRegionDispatcher when the dispatcher domain(https://dev-aem-www.samplerm.org/home) gets loaded but that's actually not happening. Please find the below rewrite rules from the dispatcher. We don't see any effect with the code(last line of the code piece) we have added.Can someone help us out on the problem. ################################################# ## Rules for setting up userRegion cookie at the starting ################################################# # For 'us' or 'in' country codes RewriteCond %{HTTP:x-aem-client-country} ^(us|in)$ [NC] RewriteCond %{HTTP_COOKIE} !userRegion= [NC] RewriteRule ^ - [CO=userRegion=%1:31557600:/:Secure] # For 'mena' countries RewriteCond %{HTTP:x-aem-client-country} ^(DZ|DZA|BH|BHR|KM|COM|DJ|DJI|EG|EGY|IQ|IRQ|JO|JOR|KW|KWT|LB|LBN|LY|LBY|MA|MAR|MR|MRT|OM|OMN|PS|PSE|QA|QAT|SA|SAU|SO|SOM|SD|SDN|SY|SYR|TN|TUN|AE|ARE|YE|YEM)$ [NC] RewriteCond %{HTTP_COOKIE} !userRegion= [NC] RewriteRule

The image width renditions functionality of the image core component breaks when using with Vue.jsThe error says as follows  Uncaught TypeError: Cannot read property 'removeAttribute' of null at unwrapNoScript (clientlib-base.js:1877) at init (clientlib-base.js:1797) at new Image (clientlib-base.js:2000) at HTMLDocument.onDocumentReady (clientlib-base.js:2007)  The error happens right here.The div with the id app is being used as the Vue main template. This Vue template encompass the whole page body of the page core component.  <div data-sly-attribute.id="app" data-sly-use.templatedContainer="com.day.cq.wcm.foundation.TemplatedContainer" data-sly-repeat.child="${templatedContainer.structureResources}" data-sly-resource="${child.path @ resourceType=child.resourceType, decorationTagName='div'}"></div>  Tracing down the problem I found that the Vue.js is changing the HTML of the nonscript tag generated b

Hello,   We are able to upload webp images in AEM Assets and are able to assign processing profiles. But we are unable to author the same webp image in core image component. I understand if we enable the "Enable Web Optimized Images" checkbox, the JPGs/PNGs can be processed through DM and rendered in webp format in the browser, but the webp image itself cannot be authored with Image component.    Secondly, while the upload of webp image is possible and local renditions are generated the processing in Dynamic Media fails with the error: 17.03.2023 20:09:24.546 [cm-p42408-e166538-aem-author-6f9bd6d466-2twrt] ERROR [sling-threadpool-e442a27c-e04b-4de4-b845-44309ab6b220-(com.adobe.cq.assetcompute.impl.assetprocessor.assetprocessoreventhandler)-1] com.adobe.cq.assetcompute.impl.senseisdk.SenseiSdkImpl Unable to process Sensei event due to failure. Reason: RenditionFormatUnsupported. Message: Format machine-metadata-json is not supported for webp files   This is causing d

I can only think of some sort of scheduled job (written in Java) that retrieves the data from the Mulesoft API and then creating CF/nodes from the response. perhaps you have  some links/guides you can suggest? thank you.

On-Prem AEM 6.5 SP 21 I'm building an application to create pages automatically based on an input file.  I can get the page created, but the created page is not showing the sub-nodes (components) which should appear because of the use of the template page. I have read that in order to resolve this I need to call a "replicate" action on the page i just created to have it "sync" and build the child nodes from the template on the target page. The problem is the code below is what I'm using and regardless of what environment i try it on I'm getting either unauthorized or invalid request for responses to the replicate call.  Even when working on a local development copy using the admin account I encounter this issue. Looking for assistance in debugging where I'm going wrong with this approach or what else should be checked?It's the line: var response = await client.PostAsync($"{aemUrl}/bin/replicate.json", content); whose result is the error.public static

We am overlaying Journal component and using ckEditor in that. There is a media embed plugin where we can put youtube url and it adds the video onto the blog. But the issue arises when we use Youtube-shortUrl and the internal jQuery call happens to convert it to longURL over http protocol. And that API call is being blocked on our website as it serves only https.Also, it works fine when we use YT long-url. Expected behavior/codeExpected that is should convert YT shortUrl to longUrl over https call and embed the video onto blogEnvironmentAEM version 6.4.2.0Looks like the issue is in /libs/clientlibs/ckeditor/resources/ckeditor/plugins/oembed/libs/jquery.oembed.min.js https://github.com/adobe/aem-core-wcm-components/issues/1174 

Hi all,Hope everyone good ! Wondering if there is a way to Manage Dispatcher Custom Headers from AEM Authoring Screen instead of making changes directly in dispatcher. we wanted to grant "Super Authors" to add / update any Custom Headers using Authoring Screen itself rather than asking DevOps help (since authoring team will not have access to clientheaders.any / dispatcher.any files). Updating Headers will be once in a while activity - but will take some burden from DevOps team. See example here from Adobe sitehttps://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html#specifying-the-http-headers-to-pass-through-clientheaders Wondering if there is any OOB feature or anything from ACS Common which can achieve this. I am using AEM 6.4   

 We are trying to integrate the Dispatcher end from AEM screen player, but we are getting the AEM Screen Blank Page.  How do configure the dispatcher end. We are not able to find dispatcher end point URL integration steps. Can you please suggest in this.I have followed the below docs.https://docs.adobe.com/content/help/en/experience-manager-screens/user-guide/administering/dispatcher-configurations-aem-screens.html

"Please resolve publish conflicts in Adobe Launch andre-trigger the download workflow manually afterwards."  receiving  this msg while trying to update the cloud service configs.  For the very first time only with "Analytics"  able to connect and afterward added IDservice and Target extensions to the Launch and trying to update IMS configs.  Does anyone have idea why this is happening? Please guide me.  Thank You  

If we make use of any ready mark up available for carousel component w.r.t amp, we are unable to fetch the teaser title,description and button link. We followed this link https://amp.dev/documentation/examples/multimedia-animations/image_galleries_with_amp-carousel/ for getting ready markup for AMP.

Unable to read json file using CQ.Util.formatData(CQ.Util.eval('/apps/ax.json')  in 6.4.IT is working in other instance.Any js files need to be installed or any config changes needed

Hello everyone,I'm working in a project  AEM SPA with ReactJS, since last week i have a warning when i am building the project because AEM react libraries that i am using are deprecated.After reading about this new libraries, i realise that besides the package renaming also it were introduced in the new versions support to typescript, and thats is very interesting because i am using typescript in my project.After i done the changes below, i have a lot of errors in my typescript validation because i have to use the new typsecripts types. "@adobe/cq-react-editable-components": "1.2.0","@adobe/cq-spa-component-mapping": "1.0.3","@adobe/cq-spa-page-model-manager": "1.1.1"To"@adobe/aem-react-editable-components": "1.0.4","@adobe/aem-spa-component-mapping": "1.0.5","@adobe/aem-spa-page-model-manager": "1.0.3" I tried to find some documentation to help me in this migration, but i am not able to find in this forum or in the aem documentation some documents with support for AEM w

Hi Everyone,    I am facing the issue in experience fragment, like live copy is working from XF lang-master to XF live copy. But the moment when I am creating language copy its not reflecting in live copy. As per this thread: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/language-copy-reference-updates-issue-with-experience-fragments/m-p/611652below line is present in this path: /libs/settings/translation/rules/translation_rules.xml. <assetNode resourceType="cq/experience-fragments/editor/components/experiencefragment" assetReferenceAttribute="fragmentPath"/> Also, there is no override is created at location  /conf/global/settings/translation/rules/translation_rules.xml Kindly anyone help on this problem statement, Thanks in advance! CC: @aanchal-sikka 

Hello AEM community, I'm encountering an issue where a workflow instance keeps running even after I restart the bundle in AEM. I've tried various troubleshooting steps like terminating the instance, purging active instances, and restarting the AEM instance itself, but none of these actions seem to resolve the problem. Interestingly, the issue is temporarily fixed after a full machine restart and setting up AEM again, but it eventually recurs. Has anyone else faced this problem before? What steps or solutions have you used to resolve this issue permanently?Any help or suggestions would be greatly appreciated! Thanks in advance!

How to unlock the default metadata in aem cloud and make the title and description fields as mandatory without creating a custom metadata schema.

Hello Team, I have a page which has these titlejcr:title has the value: ABC PagenavTitle has the value: navTitle123pageTitle has the value: myPageTitle In my custom sling model logic, I have written these statements to get the page title.    private Page currentPage; // Initialized properly with annotation. String navTitle = StringUtils.defaultIfEmpty(currentPage.getNavigationTitle(), currentPage.getTitle()); // Displays Navigation title: navTitle123 String newTitle = currentPage.getTitle(); // This displays "ABC Page" instead of "myPageTitle"    When I googled, i came to know that currentPage.getTitle() internally checks for page Title. If its not present, then only it returns jcr:title   So, What I am missing here? cc @arunpatidar  @asutosh_jena_  @vijayalakshmi_s  @amitvishwakarma