Hi @faeemazaz92    I noticed from your screenshot that You are checking it on preview mode. Could you please click on edit mode and reload the page?   Regards, Arpit Varshney

Hi @Sumit91  Could you please verify if the same issue is coming in AEM Vanilla Instance(without any custom code) with SP14?   If the issue is coming there as well -> Raise an Adobe support ticket.If the issue is not coming -> Debug your custom code if any custom code changes are breaking this. Rega...

Hi @pixeldvx Could you please go to the template of this page and look for the text v2 component in the same container, there you would notice a button to open a component policy like below Click on this and then go to the Style tab, where you would notice the style with css classes. It might be po...

Hi @AMANATH_ULLAH    It might be possible the jar you are adding via maven dependency is not available as a bundle in target AEM. You need to add third party bundle.   You can follow this blog for the same.  https://www.linkedin.com/pulse/how-add-third-party-bundle-you-aem-package-veena-vikraman   R...

Hi @Saicharan0120    The user that you are using to login into publisher should have read access on the /conf directory.   Regards, Arpit Varshney

Hi @Codelime    Could you please check the below things: open /system/console/bundle and check if all bundles are active - If not, start from there why bundles are not active.Please check the error logs after loading the page and check if you see any error in logs that might cause the issue.Check fo...

Hi @Ronnie09 the name field is a unique value to identify a field. Giving two fields the same name and making them both editable would make a weird issue. Ideally, it should have a different name.   However if a business requirement wants to have two fields, the best way is to make another field dis...

Hi @Dillibabu77 We also noticed the same issue with SDI while upgrading to SP15. This happened only for Experience Fragment because it seems to be treating XF as a synthetic resource after the upgrade.Were you able to fix this issue? Is there any way to letting SDI know to not append resource type i...

Hey @akhilraj In your running AEM instance, you can get the report via the link checker service which can be found here http://localhost:4502/etc/linkchecker.html (Please update the link based on your instance host and port)Regards,Arpit Varshney

Hi @LyonMartin Yes, You can pass it via selectors while including the resource  as shown below in your parent component:<div class="heading" data-sly-resource="${ './headingItem' @ resourceType='weretail/components/heading-item', selectors=['underline','style_h1'] }"></div> and in your heading-i...