Thanks, I'll do that

hi folks,   I am developing a React SPA and using it as a AEM component. It works very well generally. Here is my problem though. I can add public  npm packages (that the Cloud manager gets from a public repo somewhere) fine. But we have some internal common npm packages that contain reusable React ...

Thanks for this

Thanks for your reply

Thanks!

{ /type "allow" /selectors "*" /extension '(gif|ico|jpeg|jpg|png|svg|pdf|webp)' /path "/content/dam/*" }   Hi folks, In dispatcher filters, "url" and "path" seem to be interchangeable, at least in the examples I can find.  Suppose I put "url" in the filter above, would it work any differently? thank...

/wildcardselectors { /type "deny" /url "/content*" /selectors "*" } hi folks, what additional publisher rules filters should I add to allow DAM images with dots in them i.e.     blah blah .something.2000X3000.jpg or is this disapproved of?   Maybe /wildcardselectorsdam { /type "allow"  /url  "/cont...

Actually, I think it is "acs-commons-email-service". That seems to work. https://adobe-consulting-services.github.io/acs-aem-commons/features/e-mail/email-api/index.html#creating-an-email-template  

Hi folks, I recently upgraded my AEM project's embedded ACS COMMONs libraries from 4.11.0 to 5.2.0. and sending emails fails afterwards.   "...ang.IllegalArgumentException: Mail template path [ /conf/myproject/notification/email/dentist.html ] could not resolve to a valid templateat com.adobe.acs.co...

Thanks Arun, I'll have a look at how you could add "sort" and buttons to that...