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

Reto_Zigerlig
Reto_Zigerlig
Offline

Badges

Badges
14

Accepted Solutions

Accepted Solutions
2

Likes Received

Likes Received
10

Posts

Posts
23

Discussions

Discussions
5

Questions

Questions
18

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by Reto_Zigerlig
Customize the badges you want to showcase on your profile
Re: [AEM Skill Builder | October] AEM Component Generator – Best Practice AEM Components in a Fraction of the Time - Adobe Experience Manager 07-11-2019
Hi kautuksahni​Is there a recording of the session available?

Views

6.2K

Likes

3

Replies

0
Re: Extend default oak index or create custom one? - Adobe Experience Manager 12-06-2019
Daycare ticket just created!

Views

1.5K

Likes

0

Replies

0
Re: Extend default oak index or create custom one? - Adobe Experience Manager 19-05-2019
That was my intention as well, thanks a lot Joerg for confirmation!It would be great if such a case would be documented here Best Practices for Queries and Indexing.

Views

1.4K

Likes

0

Replies

0
Extend default oak index or create custom one? - Adobe Experience Manager 17-05-2019
Hi @llI need to adjust the config of the cqPageLucene index. In detail, I need to extend the path depth, where PageContent gets indexed. To achieve this, it's possible to add a node under /oak:index/cqPageLucene/aggregates/cq:PageContent/include4 with path=*/*/*/*/*.What is your best practice in this case? Do you extend the out of the box cqPageLucene index or do you create a custom index with the same definition as the cqPageLucene index and the customization?Many thanks in advance!Regards,Reto

Views

2.1K

Like

1

Replies

5
Re: AEM 6.4 sp2 cq:actions doesn't work with editannotatecopymovedeleteinsert - Adobe Experience Manager 30-01-2019
We had exactly the same issue with AEM 6.4 SP3. Fixed it with an overlay of the described node under /libs/wcm/foundation/components/parsys/newpar/cq:editConfig.

Views

2.9K

Likes

0

Replies

0
Re: AEM 6.4.3 | Not able to edit any component - Adobe Experience Manager 10-01-2019
The mentioned workaround is now officially documented under https://helpx.adobe.com/experience-manager/6-4/release-notes/sp-release-notes.html#KnownIssues​.

Views

3.9K

Like

1

Replies

0
Re: How to remove "convert to experience fragment variation" from component? - Adobe Experience Manager 22-10-2018
Hi Arun PatidarThanks 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. B...

Views

1.8K

Likes

0

Replies

0
Re: Customize / Overlay AEM 6.4 Inbox screen - Adobe Experience Manager 19-10-2018
Hi PeterThanks a lot for your worthful response. I totally agree that this should be addressed via CR at Adobe. The downside of this will be the time. If Adobe accepts the change, it will take quite a time, until it will be available. And as it is a CR, it might be possible that they only will introduce the new feature in the upcoming (minor) release.We'll see how important this feature will be for our customer and then decide, wich option we'll choose.Regards,Reto

Views

1.5K

Likes

0

Replies

0
Customize / Overlay AEM 6.4 Inbox screen - Adobe Experience Manager 19-10-2018
In the inbox screen (/aem/inbox) of AEM 6.4, only the title of the workflow item is visible.To get a better user experience, it would be great to show the title of the page in the screen as well.With an overlay of the inbox, this would be possible, indeed. But since the content classification in AEM 6.4, it is not recommended anymore to overlay this node.Are there any recommendations?

Views

1.9K

Likes

0

Replies

2
Re: How to remove "convert to experience fragment variation" from component? - Adobe Experience Manager 28-09-2018
Hi Arun PatidarI 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: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?

Views

1.9K

Likes

0

Replies

0