Rte content fragment path | Community
Skip to main content
Shubham_borole
Community Advisor
Shubham_boroleCommunity Advisor
Community Advisor
November 30, 2022

Rte content fragment path

  • November 30, 2022
  • 1 reply
  • 1617 views

Hello All, 

 

We are using rte component and in the link option trying to link to a content fragment path (A custom requirement). The link option seems to provide a 'page browser' but we are looking to use a 'path browser'.

The reason being currently the link option's page browser, we can navigate to content fragments but the content fragment itself are not visible.

Further looking, we found a call to linkpathpicker(/mnt/overlay/cq/gui/content/linkpathfield/picker/views/column) is adding the hideContentFragment=true as param in URL which keeps the CFs hidden.

 

Is this a desired behavior that rte (plugin) shouldn't be pointing to a CF?

 

We can always overlay below path and make the hide value false or remove it.

However, we are looking to find a solution that does not involve an overlay of /apps.

 

Please share thoughts on what else can be tried. I feel using path browser via link browser may help. Looking into rte configuration documentation unable to find a way that could point to a Content Fragment.

 

Thanks

 

Shubham

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

1 reply

Mohit_KBansal
Adobe Employee
Mohit_KBansalAdobe Employee
Adobe Employee
December 1, 2022

Logically, CFs are used to collect structured data, which does not have any presentation linked to it.

Saying this, CFs are re-useable content, to be consumed by other components, so that components can consume the CF data and render it in a presentable layout.

So ideally, you should create a page, put a component in it, which will consume CF, and in RTE, link the page using the Link plugin.

Hope it makes sense now.

    Shubham_borole
    Community Advisor
    Shubham_boroleCommunity AdvisorAuthor
    Community Advisor
    December 1, 2022

    @mohit_kbansal

    Thank you so much for responding. I agree, however as this is a custom requirement not directly related to showing content in a presentable way rather to fetch the content fragment data and do something with it. ( We get the cf link and use those CF data to present else where)

    Regardless of the custom use case I mentioned above, if some project needs to include some content in rte and also add some data from CF to it, if they were able to just link to a CF. Would you know why showing CF in link plugin may be blocked? Doesn't seem so in AEM 6.4 we are on AEM cloud sdk (092022).

      Mohit_KBansal
      Adobe Employee
      Mohit_KBansalAdobe Employee
      Adobe Employee
      December 2, 2022

      I have noticed that the pathbrowser make following request [1] which has hideContentFragments as true. If we make it false, path browser start returning CFs also. So you have to find out a way to make this flag as false.

      [1] http://localhost:4502/mnt/overlay/cq/gui/content/linkpathfield/picker/views/column.0.40.html/content/dam/cf/cf-master-exit-ramp/en?root=%2fcontent&exclude=%2fcontent%2f(catalogs%7claunches%7cmac%7cpublications%7cusergenerated%7cexperience-fragments%7ccommunities%7ccommunity%7ccommunity-components%7ccommunity-templates%7cforms%7cprojects%7cphonegap%7cmobileapps%7cscreens%2f(svc%7cblueprints)%7centities%7cversionhistory)(%2f.*)%3f&supportedPrimaryTypes=dam%3AAsset&hideContentFragments=true&_=1669992460519

        Terms & ConditionsAccessibility statement

        Loading footer...