Hi @smahesh    Can you provide more details on the issue?   Thanks,

Hi @Mayank_Gandhi any response on this from the Product team.

Hi @anika_agarwal    You can rollout the language copies to "/content/website/us/en" and "/content/website/us/fr". That's a valid scenario.    Thanks

Hi @kirthi_murali    There are two ways to install acs commons. One is to install the acs commons package in each of your aem instances. And the other way is to embed acs commons in your project so that it will be installed on your aem instances whenever you deploy your code. I would recommended you...

Hi @sanjay7777    Try installing the same using your package manager. Should not be an issue.  If you still want to do it via the above step, I would recommend checking the logs to see what error is occurring to investigate further.   Thanks 

Please share the content.xml for the same or the node structure.  

Can you kindly provide more details on the issue so that the community can help. Screenshots of the issue would really help along with any error/console logs.  

Hi @vasu54220    Can you please check /apps/cq/xssprotection/config.xml file in your project. I suspect there is a rule for tabindex added. Search with keyword 'tabindex' to look for rule if any. Try altering/removing the rule and check if it works.    Thanks

Hi @Ronnie09    Please check the below link. The use case tries to create a column control with a parsys in it. You can maybe extend the same implementation to add parsys from react.    https://aemsimplifiedbynikhil.wordpress.com/tag/parsys/   Thanks

Hi @Ronnie09    Make sure you have added the Key value pair for Arabic language in the dictionary .   Please follow the below document. It explains how to add key and values in dictionary and how you can incorporate the same on your html pages.   https://aem4beginner.blogspot.com/internationalizatio...