Hi @Nikhil-Kumar  For new content fragment editor, external link property should be of text type property to configure to accept a valid URL. There is no configuration as such to update for the same  Hope this helps Thanks

Hi @mohamedvalith  You can use width property for cq:dialog, that will increase the fixed width for the default touch UI dialog width property nametype Longvalue 700 (as per your requirement) hope this helps, please update if it works ThanksPrathyusha  

@BenBr9 It will work only if resource /apps/my/type exists in your instance, else it is unable to find the resource to resolve and execute it  Please create / refer existing component and refer that in your servlet  (or) access using page resource similar to below - PageName : Use existing page in p...

Servlet is not registered and it is unable to resolve. Please re-check the annotations and the import statements Try to register servlet using resourceType :  https://sling.apache.org/documentation/the-sling-engine/servlets.html#caveats-when-binding-servlets-by-path Hope this helps 

Can you update as /bin/accessibility-issues-render and post the screenshot ? '/' is missed in the screenshot you posted ! 

Additionally you can check servlet path in below sling servlet resolver  for additional debugging purpose - http://localhost:4502/system/console/servletresolver Hope this helps  Thanks

Hi @SarahBo2  Can you remove the granite:class and check any logic being written for the same I tried reproducing the same with your dialog.xml , it seems working fine after removing the granite:class Can you please try and update if not working Hope this helps Thanks

That you can restrict through user groups, I don't think there's a default config to disable only specific URL. Check this blog post by @arunpatidar https://aemlab.blogspot.com/2020/04/aem-crxde-restriction.html  Hope this helps  Thanks

Hi @Johann_Lu  Please find the relevant topic below - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-publish-block-access-to-crx/td-p/568597  

Probably issue with CSS as you mentioned elements are different in local-sdk and dev environment