Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Component is not listed in sidekick

Avatar

Level 3

When I created the component and mentioned the component group it’s not visible in sidekick but when I added the sling: resourceType:/foundation/components/list  property it’s visble in sidekick.

May I know what would be the reason why it is not visble when I didn’t mention the sling:resourceType property to the component.

Thanks in advance!

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

I guess you may not have dialog for your component. By extending list component it will have dialog. Only the components which have dialog will be shown in sidekick I guess

View solution in original post

3 Replies

Avatar

Correct answer by
Former Community Member

I guess you may not have dialog for your component. By extending list component it will have dialog. Only the components which have dialog will be shown in sidekick I guess

Avatar

Level 5
Level 5

Make sure that if you have any group for the component is selected in the Design mode and also the component is having a "cq:Dialog" or "cq:editConfig" node.

Avatar

Level 3

We've dialog in our component but still it's invisible

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----