Skip to main content

Posts

Showing posts from 2016
How to create  help  button in dialog in AEM/CQ. In our project we have to create Authoring Guide for each of the components developed .All the Authoring elements required a help button to be incorporated in each of the dialog's. AEM provide's this feature oob , we can provide an help button on dialog's on click of this button provide the target  to page to be opened in the property. Solution 1.Login to CRX  de. 2.Create a Component 3.Create Dialog within the Component 4.Create a property in the Dialog "helpPath" the type should be String and give value any existing page path , clicking of the help button should open the page in the window.

How to remove hardcoding .html from pathfield in AEM/CQ

In our project we have a pathfield in quite a lot of dialog for various custom components which refers/links to pages. After getting the value of this pathfield in the sightly template we were  adding the html extension manually on it. e.g.                 <a class="navbar-brand" href="${properties.homepagePath @ context='unsafe'}">${properties.headerAuthTitle}</a> We can avoid hardcoding the path by adding property in dialog link  linkPattern The  pathfield  xtype has a config option called  linkpattern . This allows you to configure the widget to automatically add an extension  in case the browsefield is used  to select the link. If a user types the text , the extension is not added. Use this option to add '.html' and all internal links will have .html appended (assuming the content authors always use the pathfield's browse option to select the link [which they should be doing ] ). This way the backend code doesn't hav