How to remove "convert to experience fragment variation" from component?

Avatar

Avatar

mikes22421318

Avatar

mikes22421318

mikes22421318

14-09-2018

Hi Community!

Does anybody know how to get rid of the "convert to experience fragment variation" button in the editbar of a component?

convert_to_exp_frag_ver.png

Is it possible to remove this button for a group of users?

Thanks for your help!

Regards

Mike

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

3.1K

Likes

1.2K

Correct Reply

883

Avatar

Arun_Patidar

MVP

Total Posts

3.1K

Likes

1.2K

Correct Reply

883
Arun_Patidar
MVP

14-09-2018

Hi,

You can do this by :

1. overlaying /libs/cq/experience-fragments/content/v2/conversion node

2. create rendercondition node Render Conditions — Granite UI 1.0 documentation , you can go with Privilege or Feature. Feature will give you the more control over Privilege but you can choose based on your requirement.

Answers (5)

Answers (5)

Avatar

Avatar

bwells78

Avatar

bwells78

bwells78

23-03-2020

I just added some CSS to my author-only clientlibraryfolder:

 

.coral3-Button[data-action=XFCONVERT] {

    display: none;

}

 

Not sure yet if this will have any unintended consequences elsewhere... will adjust if needed.

 

Applying the cq.authoring.dialog.all category to your clientlibraryfolder will ensure it's made available to the editor page.

Avatar

Avatar

Reto_Zigerlig

Avatar

Reto_Zigerlig

Reto_Zigerlig

22-10-2018

Hi Arun Patidar

Thanks again for your response. Your last mentioned workaround looks a little buggy to me, so the author gets the feeling, that something is broken. Then I would prefer to do it as you mentioned in your first workaround. Render the icon but don't do anything there. Feels a little less buggy to me . In this case, the "proper" solution would be an overlay of the

/libs/cq/experience-fragments/editor/clientlibs/experiencefragments/js/editor/actions/edit .EditableActions.XFCONVERT.js. But since it is below a "granite:InternalArea" node, it is just kinda proper.

Regards,

Reto

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

3.1K

Likes

1.2K

Correct Reply

883

Avatar

Arun_Patidar

MVP

Total Posts

3.1K

Likes

1.2K

Correct Reply

883
Arun_Patidar
MVP

28-09-2018

Hi,

The icon is rendering from below js not from granite item, to remove icon you can override below js and make changes

/libs/cq/experience-fragments/editor/clientlibs/experiencefragments/js/editor/actions/edit.EditableActions.XFCONVERT.js

But there is a workaround to deal with your case, you can hide dialog instead button by adding rendercondition node at e.g.

/libs/cq/experience-fragments/content/v2/conversion/content/granite:rendercondition

for testing you can add simple to hide for all

Simple — Granite UI 1.0 documentation

Screen Shot 2018-09-28 at 5.16.41 PM.pngScreen Shot 2018-09-28 at 5.14.36 PM.png

Avatar

Avatar

Reto_Zigerlig

Avatar

Reto_Zigerlig

Reto_Zigerlig

28-09-2018

Hi Arun Patidar

I tried your workaround quickly with adding the node granite:rendercondition with privileges restriction directly on the /libs/cq/experience-fragments/content/v2/conversion. (This was just for testing purposes) See:renderConditionExample.png

But the option is still rendered. The function itselves does not work, because the user does not have the permission.

Do I have to add the logic of checking the rendercondition within the overlay on my own?

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K
smacdonald2008

14-09-2018

As Arun suggests - it's involves overlaying the ootb AEM code.