It takes 1 hour+ for the Adobe build process to build and deploy to a cloud env. This means a simple fix takes many hours, as first we have to build and test on dev, then build and test on UAT, then build on stage, then live. Thats 4+ hours just building duplicate code. And that is if Adobe Build sy...

Hello all, I am very new to the AEM Cloud Venia storefront, So basically I started with installing the venia store as a cloud service and downloaded the CIF connector to connect between Magento and successfully I got the data on the commerce side of AEM, but the issue is on the fresh venia theme pac...

Hi @All,i have developed 1 component which fetches documents on basis of selected tags...i have used Query Builder.The code is working fine in Author and Publisher Environment. throwing error on varnish URLModel cannot be correctly instantiated by the Use APIwhy it only visible in varnish URL

Hi all, I am trying to update the below dropdown's list. Since there are a lot of items, it takes time to add the items by using '+' icon button and remove by using '-' icon button as well. Is there any shortcut way to upload in one shot? Thanks.

Moved to forms group 

Hi there,I have tried adding the following code but the configure option is not showing still Does anyone know the node location of this configure button or maybe the toolbar, it might be a permissions issue.Thanks

When a package with JS and CSS code is built and deployed, and then a page requested from the website, it contains links to JS and CSS files processed by AEM (with additional name parts and possibly minified), e.g.: Generally, when a new version of the package is installed, new JS and CSS file names are generated; and, when they are requested, the new code is served. However, from time to time we notice that, right after deployment, pages already contain links to files with new names but those links serve old code, which often breaks important functionality, as old code is invalid for the new markup. These invalid JS and CSS files are then cached in visitors' browsers, and even when Publishers start serving the new code, it does not help, as the scripts' names are the same and client browsers get them from cache. The only way to fix it is to deploy a new build so file names are updated. But this takes hours to arrange and perform, and all this time the site is partially broken. Looks like the issue is reproduced for only a short time after deployment: we have never managed to obtain the broken JS or CSS from a Publisher manually, but still, it was cached on Dispatchers, so some visitor managed to get it. What can be the cause of this behavior? Regards,Alexander

Hello Team, Below code is part of one Sightly HTML:var hello = new Swiper(".artcile-page", {mousewheel: true,});PROBLEM:In author view source, we can see this piece of code. But in Publish page, only is visible.Rest part is removed. Regards,AP

I noticed recently a slowdown in performance and went to check for Session leaks after almost 2 years of stability. I noticed over 430 SessionStatistics but none have any values in the stacktrace field. Shouldn't I be seeing the trace of what opened the Session? What could this mean?There are a ridi...

Hi Everyone, We have multiple developers who work on the same form/template during different time periods. We like to keep track of which developer has made what change to the forms. Each developer opens the XDP template in the stand-alone desktop Designer 6.5. Makes the necessary changes to the for...