@learningNeverStops You need to exclude assets from the translation to avoid creating language copies of assets.To do this you need to update the translation integration config for your project.Under Assets tab Select translation method as "Do Not Translate" and uncheck "Translate Assets" checkbox.

Hi @Dusty1186The CONTENT_PATH where you are loading your json has to be absolute path and not relative. I think json is not loading properly.Please make CONTENT_PATH absolute and try.

Hi @aliaksandr_hvozdzeu This expression should work for any match: (.*?) 

@Uppari_Ramesh You can mock static methods with Mockito library. You need mockito-core and mockito-inline dependency for this.@Mock private AccessControlManager mockedAccessControlManager; @Mock private JackrabbitAccessControlList acl; @Test void testMethod() { try (MockedStatic<AccessControlU...

@webdev91 I am not sure if AEM or maven has any straight forward solution to this issue. One probable solution I can think of is You can create a one more maven project dedicated for translation rules file and all teams utilize it for their respective changes and remove translation rules file from a...

Hi @webdev91 You can not have multiple translation_rules.xml files. There is only one translation_rules.xml file per aem instance. You can create different contexts under this file for your each site like below I have created for wknd site. You can add components specific to that site under this con...

@fionas76543059 The method you are following should work. Did you add the dependency in apps pom.xml where you are actually trying to embed it? 

@TB3dockThis is a basic skeleton of Test class which you can use. You don't need to use @Rule annotation here. import io.wcm.testing.mock.aem.junit5.AemContext; import io.wcm.testing.mock.aem.junit5.AemContextExtension; import org.junit.jupiter.api.BeforeEach; import org.junit.jupiter.api.Test; impo...

@Vani1012 Can you please check if sling:resourceType property is set on jcr:content node of template structure node and if set it is pointing to correct page component?   

@SupportMemberYou should not name your assets as per the language. You should put them in respective language directory with proper locale code.I think structure should look like/content/dam/my-site/content-fragments/en-gb/privacy-policy.html/content/dam/my-site/content-fragments/en-ca/privacy-polic...