wcm/foundation/components/iparsys vs. foundation/components/iparsys | Community
Skip to main content
Level 4
October 16, 2015
Solved

wcm/foundation/components/iparsys vs. foundation/components/iparsys

  • October 16, 2015
  • 9 replies
  • 8796 views

I'm working on some templates for a new site we're launching which will eventually be used across the board for all of our existing websites. I'm a bit confused at the differences between base level components, but this question is speficit to the ootb iparsys.

For sightly templates, is wcm/.../iparsys the prefred iparsys to use? I noted in the geometric outdoors activites page example that the normal parsys used is the wcm/..../parsys, however, the iparsys in thei section seems to be a bit buggy (specifically, inheritance only goes down one level), an issue that foundation/.../parsys doesn't have.

Thanks.

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 Lokesh_Shivalingaiah

If you feel there is a bug, please raise a ticket for the same

9 replies

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
Level 10
October 16, 2015

If you feel there is a bug, please raise a ticket for the same

BenSt10Author
Level 4
October 16, 2015

I'll raise a ticket separately, I guess.

I'm mainly looking for guidance on the difference/preference between wcm/foundation/components/iparsys and foundation/components/parsys.

October 20, 2015

There is a bug as well.. how we raise a ticket?

If we use the "wcm/foundation/components/iparsys" the "Dropdown Show/Hide" won't work or show the 2nd dropdown box in the list

while if we use "foundation/components/iparsys" everything works as expected.

smacdonald2008
Level 10
October 20, 2015
teufeld
Level 2
July 5, 2017

Hi,

Just to be sure, but new component with slightly, touch UI are in /wcm/foundation.

And old component jsp, classic UI are locate in /foundation.

Am I correct ?

Lokesh_Shivalingaiah
Level 10
July 5, 2017

That's correct

teufeld
Level 2
July 6, 2017

thanks

Jit
Level 2
July 6, 2017

Yes, we noticed that from CF3 to CF8 something happened where /wcm/foundation iparsys did not behave the same way as /foundation... I did not have time to track down where the problem was, so i switched them all (all the places we were using it) to /foundation.

JoseBerciano
Level 3
July 16, 2017

I just came across this bug in AEM 6.3.

I wanted to have an editable template with iparsys for both header and footer, but apparently the policies I set do not apply after saving the changes.

Any updates on this?