Hi, This is due to a bug in Sling that hasn't been addressed yet. AEM relies on the Out-Of-The-Box (OOTB) Sling Sitemap Generation, which is likely where the problem originates.    

 @akashkriz005 Thanks for clarifying. Unfortunately, this is a bug that Adobe is supposed to fix in the future. Please check this thread: AEM Upgrade 6.5.17 Issue with Nested Multi-Field Authoring Focus. You could still use some JavaScript as a workaround to address the issue in the meantime, but be...

Question: Regarding Opt-in, does this seem ok to you?    This would be my reasoning, but I am not sure if it is true: RequirementSolutionsImpactFirst-party measurement is okay to collect in pre-consent state. All other types of data usage prevented until consent is received.Use Opt-in to enable Ana...

Hi,  You cannot access inheritedPageProperties from JavaScript directly because it is server-side data. As explained, you either need to expose the server-side data (inheritedPageProperties) in your HTML markup and then access it via JavaScript, or use a service that retrieves this information from ...

Hi,    I would suggest breaking this down into components that represent different parts of the structure—such as parent component and child components. Then, use Java to assemble a final representation of what you're aiming to achieve for the frontend. While the multifield approach is simpler from ...

Hi, I don't see that behavior in AEM6.5.16. The "Add" button is at the bottom of the multifield, when you click on the "Add" button, the scroll keeps whenever it stays. Below is the config I am using <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0...

Hi, Could you specify which "move" command you are referring to? Are you using the UI or some other type of script?

Hi, What option are you following? How is your project structured, and what does your content look like?  The component does not exist in your AEM project.The component exists in your AEM project but its required content does not.The component and its required content both exist in your AEM project....

Hi,    The traditional ways to handle such scenarios with pages are using ACLs (Access Control Lists) or CUGs (Closed User Groups). The best solution will depend on your specific requirements. From what I understand, CUGs might be suitable for your needs. You can find more information here: CUGs Doc...

Hi,This issue is related to the use of vh (virtual height) in your custom CSS. Most likely you are using something like this: height: 100vh which may not work in "Edit mode" due to its iframe relationships. To fix this, you should add a condition to set a fixed height in Edit mode.Hope this helps.