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

Component toolbar missing options in Targeting Mode

Avatar

Avatar
Validate 1
Level 2
ruchim
Level 2

Likes

4 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile

Avatar
Validate 1
Level 2
ruchim
Level 2

Likes

4 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
ruchim
Level 2

02-01-2018

Hi,

We are facing an issue with the toolbar options in the AEM 6.1 targeting mode for some components.

When we try to personalize the components with this issue, we are able to - target a component, add an offer and then configure the component.

The toolbar looks like:

1385450_pastedImage_2.png

However, after configuring it for the first time, the options go missing in the toolbar and it looks like:

1385451_pastedImage_3.png

Then we have to switch to another experience and come back to the first one and then the same behavior is repeated. We can configure/edit the component one time and then the buttons again go missing.

This happens with just a few components. I have checked and we have no special setting for these components.

There is no JS error as well.

I tried to debug in the OOTB files and found that when the issue happens, the editable type of the component is: cq/personalization/components/target

When we see all options, the editable type is the component resource type.

1385452_pastedImage_4.png

Please advise if someone has faced an issue like this.

Thank You.

Replies

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

03-01-2018

For this - please report to the Support Team by opening a ticket.

Avatar

Avatar
Validate 1
Level 2
ruchim
Level 2

Likes

4 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile

Avatar
Validate 1
Level 2
ruchim
Level 2

Likes

4 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
ruchim
Level 2

17-01-2018

Thanks Scott.

We finally figured out the issue so thought I will share in case others face the same.

We use a client side rendering framework for components. So from AEM, a data-model with update request is passed to the front-end to render the component on page load or component update.

In the affected components, we had a CQ listener of REFRESH_PARENT set on edit.

When we were targeting a component in an experience, 2 calls were being made by AEM. One for experience related update and another one (caused by REFRESH_PARENT) for default. This was causing AEM to believe that we were trying to update the default view in an experience and hence all component edit toolbar options were getting removed.

When we changed it to REFRESH_SELF, no default call was made, and or toolbar rendered fine.

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

17-01-2018

Thanks for posting the fix