Hi @SaujanyaGu,your Dispatcher config looks ok, I suggest you check the following things:As this feature has just been released, ensure that you are testing on the up-to-date instance of AEMaaCSEnsure that your AEM Publisher is returning a valid map on the configured pathCheck the Dispatcher logs, t...

Hello,on my project, we have a custom multifield enabled for Content Fragments. Now I want to evaluate if we can continue to use this approach when we migrate to the new Content Fragment Editor.I was curious if someone already tried to build a plugin/extension like that? I see there are many example...

Hi @_CL,I believe you can use Environment variables directly in your code without having them included in the OSGi configuration. I haven't tried it myself, but the Java API: System.getenv("YOUR_ENV_VARIABLE") should work normally. Good luck,Daniel

Hi @RohitKu17,to extend and customize AEM you need to use Java and the provided interfaces from Adobe.You can use Node.js to build APIs and microservices that communicate with AEM. Good luck,Daniel

Hi @HPM-,my personal preference is definitely to have local developer environments. It is simpler and faster to test code locally. The only downside is that some features can be tested on a real AEMaaCS environment. But 95% of things can be done on local SDK. Also, RDEs are not free AFAIK. Good luck...

Hi @chavad,keeping dummy markup in HTL files will indeed help, but a better solution would be to deliver fully rendered content to SEO robots. This can be done using third-party pre-rendering services, such as Prerender.io, or building it yourself with Node.js. In case you want to build it custom, y...

Hi @Prithwiraj_Deb,personally, I consider content backflow a bad architectural pattern and a relic from the past. I would strongly suggest looking for 3rd party solution or building your own microservices for storing and delivering user-generated data. Good luck,Daniel

Hi @djohn98390536,in case your method is private, then you shouldn't write a unit test for it at all. This is considered bad practice by most. Instead, focus on testing your public methods that will cover the logic in your private methods as well. Good luck,Daniel

Hi @BenBr9,check the OSGi Configuration named Apache Sling Servlet/Script Resolver and Error Handler if it allows for the /bin/* path. By default /bin/* should be allowed, but maybe you are not using the default config. Also, it is recommended to use resource type based servlets over path based. Goo...

Hi @chalamcharla,true, I also see it on AEMaaCS Author, but not on Publisher. In our case, we use a custom servlet to fetch Vanity URLs so we don't use the one from libs. Maybe you will need to ask Adobe support. Good luck,Daniel