AEM 6.4 Customization of convert to experience fragment dialog | Community
Skip to main content
Y
yashwantv652839
April 29, 2020
Solved

AEM 6.4 Customization of convert to experience fragment dialog

  • April 29, 2020
  • 2 replies
  • 4405 views

We have the following requirement that at time of experience fragment creation I have to provide variation title and variation tag but I don't have those options in the dialog in the new fragment creation action, I tried to overlay the dialog but it is still loading the libs.

I am able to override the existing dialog if I change the dialog url variable in /libs/cq/experience-fragments/editor/clientlibs/experiencefragments/js/editor/actions/convert.js to point to apps instead of libs.
is the above approach a good practice?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vish.dhaliwal

Hello,

 

That is not a good approach and certainly not recommended. Your changes will go away on the installation of service packs (if SP has code changes related to this path). 

Please review the sling Resource Merger doc [1] to make sure the overlay/override is implemented correctly.

I am assuming you are using 6.4 or 6.5. This path is marked as Internal (granite:InternalArea) which means it cannot be overlaid, inherited, or used directly. These nodes are meant only for the internal functionality of AEM.

[1] https://docs.adobe.com/content/help/en/experience-manager-65/developing/platform/sling-resource-merger.html 

Regards,

Vishu

 

 

2 replies

V
Adobe Employee
vish.dhaliwalAdobe EmployeeAccepted solution
Adobe Employee
April 30, 2020

Hello,

 

That is not a good approach and certainly not recommended. Your changes will go away on the installation of service packs (if SP has code changes related to this path). 

Please review the sling Resource Merger doc [1] to make sure the overlay/override is implemented correctly.

I am assuming you are using 6.4 or 6.5. This path is marked as Internal (granite:InternalArea) which means it cannot be overlaid, inherited, or used directly. These nodes are meant only for the internal functionality of AEM.

[1] https://docs.adobe.com/content/help/en/experience-manager-65/developing/platform/sling-resource-merger.html 

Regards,

Vishu

 

 

    Y
    yashwantv652839Author
    April 30, 2020

    yes but the URL call is var dialogUrl = Granite.HTTP.externalize("/libs/cq/experience-fragments/content/v2/conversion.html/libs/cq/experience-fragments/content/v2/conversion/converter") where the path was fixed to libs  in /libs/cq/experience-fragments/editor/clientlibs/experiencefragments/js/editor/actions/convert.js file.


    the way which i see is to override the js to apps and update the dialogUrl path to the overlayed node.


    so how can we make that point to the one I overlayed without overriding the clientlibs? 

    D
    davidef34326447
    Level 3
    April 14, 2021
    i have a similar problem. i want using the functionality i want override the the component injected in my site page "cq/experience-fragments/editor/components/experiencefragment" with my custom experience fragments component (inherited from core component). i don't have found any article that can help me.
      rsundaram
      rsundaram
      Level 2
      February 9, 2022

      Hello @davidef34326447 - I am currently working exactly the same functionality. Are you able to complete it by any way?

      Terms & ConditionsAccessibility statement

      Loading footer...