Hi @webtech11,sorry, my mistake, I thought you wanted to learn how to develop/customize for AEM, not author content. Forget GitHub in that case, it is used to version code for AEM customizations and extensions. Good luck,Daniel

Hi @Ana_BelénCa,not sure how "smart" this rule in SonarQube is, but in more advanced vulnerability scanning tools like Snyk would check all the places where you call the method and if you are passing any user-provided params. Good luck,Daniel

In this article, we presented an AEMaaCS and Next.js hybrid CMS demo that focuses on solving four important goals for different stakeholders: end-users, editors, developers, and architects/business owners. We've demonstrated how to achieve top performance, browsing experience, and SEO for end-users ...

Hi @rahulda2,not sure what type of frontend are you using but I did something similar using Next.js and AEM Pages (not Content Fragments) in this demo: https://www.youtube.com/watch?v=wJx4kLeGVuc Hope this helps,Daniel

Hi @webtech11,to be honest I am not aware of any free courses to recommend. Maybe something is available these days, but I had to learn AEM the good old (hard) way: by reading documentation and doing real, hands-on work.I don't think adding a completed Udemy course to your CV will help you find a jo...

Hi @toimrank,this warning suggests a cross-site scripting vulnerability. Are you creating the fileName from any user-provided parameters, like GET params in a Sling Servlet? Good luck,Daniel

Hi @NageshRaja,it should be vice versa, requests with query params should be a MISS. Here is a shell script for you to fix symlinks:cd .. project_root=$(pwd) cd dispatcher/src/conf.d/enabled_vhosts enabled_hosts=$(ls *.vhost) for host in $enabled_hosts; do rm $host ln -s ../available_vhosts/$host ...

Hi @NageshRaja,There is definietly a problem with your Dispatcher cache not being flushed. Can you confirm that you defined the statfilelevel in the invalidation.farm? As that is the farm used for Dispatcher flush/invalidation requests.The statfilelevel starts from your DOCROOT, so it looks fine. In...

Thanks @arunpatidar, will share it today on LinkedIn and would appreciate your feedback

Hi @BohdanYurevych,I did solve that in my Next.js demo, you can watch it here: https://www.youtube.com/watch?v=wJx4kLeGVucSo the solution was to add a custom button in /apps/wcm/core/content/sites:<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http:...