Hi,I guess below steps would help you achieve what you have mentioned:Steps:First of all you will need to overlay OOTB LinkDialog.js file.Current location of LinkDialog.js is - /libs/cq/ui/widgets/source/widgets/form/rte/plugins/LinkDialog.jsOverlay the path and bring it under appsYou will need to d...

foundation/components/iparsys would be a good reference to identify any configuration miss. It has childEditConfig node through which it inherits cq:actions to child component dragged in iparsys container.

You can follow below steps to achieve it:If you component can be dragged in container then:On your main page drag the component in parsys container and configure it with dataOr you can create a config admin only page with parsys container (contains only parsys in JSP Script)Once you have configured ...

One way to solve this could be - maintain a map in etc/map for all domains versus their locale path.. in your error page then read the domain which you can resolve it to its corresponding content structure using resourceresolver. Once you have your content locale path, suffix it with error page iden...

Just to rule out the case of caching you can put some query parameter to your page URL and see the behavior, if you still see the UGC content, if it is still coming up then it means it is still in AEM.

You can first concat it into one string and assign it to sightly variable using data-sly-test. See the snippet below<div data-sly-test.prefix="next"><div data-sly-test.suffix="text"><div data-sly-test.i18key="${prefix}.${suffix}">Value - ${i18key @ i18n}You can also use @format to form a single stri...

Hi Clive,If your need is to only list down the select options dynamically then you can also drive it from servlet of JSP file.refer to foundations, list component - /libs/foundation/components/list/dialog/items/list/items/displayAs to know how you can do it.Also can you put down the details why you ...

I guess with what you suggested it is going to append '.html' with '#' as well.

Hi,You can use format method of sightly to form a formatted path url with extension${ '{0} {1}' @ format=[url,extension]}url and extension are again sightly variables, where url contains the page path - '/content/mysite/abc' and extension contains the value of extension you need i.e. '.html'Do forma...

I strongly agree with what Justin mentioned and proposed.Also custom namespace creation is going to be one time process, hence there is no point of putting it in workflow, you can trigger creation of namespace from your content package.- Runal