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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

OOTB colctrl component not working in wcm/foundation/components/responsivegrid

Avatar

Level 2

Hi All,

I am using wcm/foundation/components/responsivegrid for changing site to responsive using bootstrap with it. Every other component is working except OOTB column control (libs/foundation/components/parsys/colctrl).

When I am using responsivegrid place holder, and drag and drop colctrl component, I can't see place holder in it. Attached are the difference between using colctrl component using responsivegrid and parsys. I tried to add colctrl in /libs/wcm/foundation/components/responsivegrid, but no use. Please advise me on this.

Note: The existing components are using OOTB colctrl (libs/foundation/components/parsys/colctrl).

Thanks for your thoughts in advance !!

Regards,

Sai. 

1 Accepted Solution

Avatar

Correct answer by
Level 5

Ideally, you should overlay the component and use it to create the pages to take care of issue which comes up after the upgrade, certainly which did not happened in your case.

Anyways, are you seeing any error in the javascript console ?

View solution in original post

3 Replies

Avatar

Level 2

Hi Ratna,

Thanks for the reply..

There are lot of pages using out-of-box column control in the site.

I am planning to use OOTB column control instead of creating a new one. If I use the custom one it will break all the pages it is been used in.

So, I want to make use of OOTB column control make it to work. Only thing is place holder is not displaying when I drag and drop on page control control when using wcm/foundation/components/responsivegrid

Thanks,

Sai.

Avatar

Correct answer by
Level 5

Ideally, you should overlay the component and use it to create the pages to take care of issue which comes up after the upgrade, certainly which did not happened in your case.

Anyways, are you seeing any error in the javascript console ?