Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

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

Avatar

Avatar
Validate 25
Level 3
patK-ze1xYs
Level 3

Likes

19 likes

Total Posts

60 posts

Correct Reply

2 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Boost 5
Boost 3
View profile

Avatar
Validate 25
Level 3
patK-ze1xYs
Level 3

Likes

19 likes

Total Posts

60 posts

Correct Reply

2 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Boost 5
Boost 3
View profile
patK-ze1xYs
Level 3

15-10-2015

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 ? 

View Entire Topic

Avatar

Avatar
Validate 10
Level 2
SurendraKonatha
Level 2

Likes

5 likes

Total Posts

63 posts

Correct Reply

6 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 10
Level 2
SurendraKonatha
Level 2

Likes

5 likes

Total Posts

63 posts

Correct Reply

6 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 1
View profile
SurendraKonatha
Level 2

20-10-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?