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

SOLVED

Component unavailable?

Avatar

Level 1

Hi,

 

I am following the WKND tutorial and learning how to build custom components. I have created a component definition and sync'd it to AEM, but the component is not recognized by the system.  What could be the cause of this?

 

At this step, the component is not available in my local instance.

 

This I have tried/observed:

- I have confirmed that the .content.xml calls out the proper Component Group, and that my .xml files and folders match the tutorial.  I have gone through the tutorial 3 times with the same result.

- I can see the component specification in CRXDE Lite, so AEM Sync worked and pushed the component to my local instance

- Tools > General > Components - the component is not listed here

- Checking the policy on the page template's container, I do not see the component listed

 

 

jdylanmc_0-1663792595249.png

 

jdylanmc_1-1663792675797.png

 

jdylanmc_2-1663792718206.png

 

On a side note- is there an easier or preferred way to add components?  The JCR syntax seems like a steep learning curve and fragile.

1 Accepted Solution

Avatar

Correct answer by
Level 4

It seems the component group you have added in policy and the group of component that you have created is different.

 

allowed one:  WKND SITES PROJECT - CONTENT (It is not listing the byline component)

desired component's group: WKND Sites Project - Content

 

Can you change the casing of the group name to capital and then try?

View solution in original post

2 Replies

Avatar

Level 1

I tinkered with the byline.html file from the tutorial, and observed that if I remove `<sly data-sly-call="${placeholderTemplate.placeholder @ isEmpty=true}"></sly>`, then the component begins working.

 

Is this a coincidence?  Or is this a typo in the HTL and any HTL errors prevents the component from working?

Avatar

Correct answer by
Level 4

It seems the component group you have added in policy and the group of component that you have created is different.

 

allowed one:  WKND SITES PROJECT - CONTENT (It is not listing the byline component)

desired component's group: WKND Sites Project - Content

 

Can you change the casing of the group name to capital and then try?