Overriding the Column Control [/libs/foundation/components/parsys] | Community
Skip to main content
P
patK-ze1xYs
New Participant
October 16, 2015
Solved

Overriding the Column Control [/libs/foundation/components/parsys]

  • October 16, 2015
  • 3 replies
  • 1918 views

I am trying to override the Column Control component , as per the document that I have gone through , I need to copy the node at  [/libs/foundation/components/parsys] and place it under the /apps . In my case it would be : [/apps/foundation/components/parsys] .  This path was not present on my local so I created a folder structure under : apps [/foundation/components]

I am using the maven plugin to push my local changes to localhost:4502.  So I created the exact replica of node structure at the  [/apps/foundation/components]

[img]Capture_OverrideColumn.PNG[/img]

When I build the project I dont see anything under crxde. 

To try another place , I took the exact node structure and placed it under the [/apps/projName/components] , even with this I dont see  parsys under [/apps/projName].  Am I missing anything about overriding the component ? 

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 smacdonald2008

Instead of using a Maven plugin - try to manually copy and paste the code from libs/foundation/components/parsys to /apps/projName. Copy and paste the content using CRXDE Lite. That will ensure that you get the CQ component that you want to extend under /apps. Then you can successfully modify the app logic and use it in your CQ app. 

3 replies

smacdonald2008
smacdonald2008
New Participant
October 20, 2015

Best practice of overlaying a component is to copy component from /libs to /apps in CRXDE lite as documented here:

https://docs.adobe.com/docs/en/cq/5-6-1/getting_started/first_steps_for_developers.html#Developing a new component by adapting an existing     component   

Once done in CRXDE lite - you can sync the code using vault to eclipse that uses developer plug-in. 

Also for those reading this and wanting to create/or customize the column component - see this community article: 

Creating Adobe Experience Manager Custom Column Components

A
Anonymous
October 20, 2015

But this will only be on the AEM side and cannot be pushed through maven as "ptK" asked? This also add additional maintenance step on AEM for the project?

smacdonald2008
smacdonald2008Accepted solution
New Participant
October 16, 2015

Instead of using a Maven plugin - try to manually copy and paste the code from libs/foundation/components/parsys to /apps/projName. Copy and paste the content using CRXDE Lite. That will ensure that you get the CQ component that you want to extend under /apps. Then you can successfully modify the app logic and use it in your CQ app. 

Terms & ConditionsAccessibility statement

Loading footer...