Classic UI: Copy/paste components that are hidden in sidekick

[andresh54167051]

Hello everyone.

We are running Classic UI on AEM 6.3 and have recently sunset some components by marking their componentGroup as .hidden. This allows existing components to continue rendering while ensuring authors don't continue to create new instances of these components.

The issue we are running into is this prevents authors from moving the existing components around the page using cut/copy/paste.

Is it possible to remove a component from the sidekick while still allowing it to be moved on an existing page?

Thank you!

[smacdonald2008]

Typically, if you want to work with a given component, it should still be available on Side Kick.

[andresh54167051]

I understand that. Does this mean there is no functionality in place that allows for .hidden components to be copy/pasted?

[Gaurav-Behl]

A workaround could be to restrict the component to be dropped/moved only in certain containers/parsys/templates. That ways author could still move the component on page but only in limited sections of the page. Make this as restrictive as possible.

Refer to Geometrixx how the components are restricted to be dropped only on certain sections of the page-

/etc/designs/default/jcr:content  or

/etc/designs/geometrixx-outdoors/jcr:content

[andresh54167051]

Unfortunately, this method leaves the component in the sidekick. We do not want the component to be displayed in the sidekick.

[Gaurav-Behl · Accepted solution]

The other solution is not a clean solution -

Move all those components to a particular Group (You can create multiple Groups for your project's design) and hide that entire group in the sidekick via css (add display:none; on that group's element on sidekick load/ready event). This way the component can still be moved but would not be visible in the sidekick.

Pick any sidekick article and customize it -

Experiencing Adobe Experience Manager - Day CQ: In the blog "Experiencing Adobe Experience Manger - ...