Is Iparsys really not recommended to use in editable template? | Community
Skip to main content
Anderson_Hamer
Anderson_Hamer
Level 4
July 22, 2021
Solved

Is Iparsys really not recommended to use in editable template?

  • July 22, 2021
  • 2 replies
  • 1941 views

I heard that Iparsys component is not compatible in editable template and not recommended to use in editable template but I never seen any document from adobe on this.

 

The fact is, Iparsys works in editable template in the same how it works in static template but it may not function properly when you are in editable template but the same will work in actual page. Can you one tell if it is really not recommended to use in editable template? If so please point me to adobe documentation.

 

UPDATE

Assume that below pages are built on editable template and keep component X in initial content in editable template  which will actually goes to ALL pages while creating
 

Experience fragment or Initial Structure will not be able to replace iparsys. Iparsys has it's own functionality. How do we handle inheritance in a pages that is built on editable template? what is the recommendation from AEM? 

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 joerghoh

 

iparsys is part of the product almost forever, and it did have its usecase, but I see them less and less relevant (and also other components taking over, at least partially).

 

I am not aware of any explicit deprecation or compatibility problem. But the iparsys belongs to the "old" foundation components, and I can cleary see that the focus has shifted to the Core Components, along with editable templates. And I don't think (haven't checked it) that the iparsys can make use of the features provided there, so unless it is re-implemented it does not really fit in.

 

2 replies

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
July 22, 2021

 

iparsys is part of the product almost forever, and it did have its usecase, but I see them less and less relevant (and also other components taking over, at least partially).

 

I am not aware of any explicit deprecation or compatibility problem. But the iparsys belongs to the "old" foundation components, and I can cleary see that the focus has shifted to the Core Components, along with editable templates. And I don't think (haven't checked it) that the iparsys can make use of the features provided there, so unless it is re-implemented it does not really fit in.

 

    ChitraMadan
    Community Advisor
    ChitraMadanCommunity Advisor
    Community Advisor
    July 22, 2021

    Hi @anderson_hamer ,

     

    You can still make iparsys work with editable templates, but it is NOT recommended by Adobe.

     

    Please go through some interesting and similar conversations in these links:

    https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-2-to-6-4-upgrade-issue-with-iparsys/td-p/295108

    https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/iparsys-like-behavior-with-layout-containers/qaq-p/289990

     

    Please also see comment below from one of the above links.

     

     

    Adobe recommended way is to use Content Fragments or Experience Fragments to achieve similar functionality to iparsys.

     

    Please let us know if you need help in moving away from iparsys and use newer recommended options.

     

    Thanks,

    Chitra

     

      Anderson_Hamer
      Anderson_HamerAuthor
      Level 4
      July 24, 2021
      Chitra & Jorg - Like you said XF can not replace iparsys behaviour. I could not format the content in comment hence let me update the msg in summary of this ticket. Please check.
      Terms & ConditionsAccessibility statement

      Loading footer...