Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Calendar component is not available in AEM 6.3 page

Avatar

Level 4

When I am trying to include AEM 6.3 OOB calendar component in pages, I couldn't see the component in communities group.Ans for the blog, style is breaking.

Any one faced similar issue?

design_mode.JPGcrx.JPG

blog.JPG

1 Accepted Solution

Avatar

Correct answer by
Employee

anushap40132887​ - If there is an issue with styles, it has to be a problem with clientlibs. If you are sure(just double check once), that all required clientlibs are included, it can probably also mean that either :

1. Customization wasn't removed properly, some mapping between resource types remain.

2. Customization wasn't implemented correctly and you made changes to some OOTB resource mappings.

View solution in original post

5 Replies

Avatar

Administrator

Adding a Calendar to a Page Calendar Feature

-Kautuk



Kautuk Sahni

Avatar

Level 4

Yes kautuksahni​, I have already gone through this doc. My issue is, I am even unable to find the calendar in OOB communities group.

Avatar

Employee

anushap40132887​ - I wasn't able to see this issue in-house. Can you quickly confirm following :

1. Have you applied any customizations?

2. Have you installed any feature packs?

Avatar

Level 4

yes Rahul, I was using custom calendar component. When I removed that, I am able to see the OOB component. But still there is issue with styles. All the required clientlibs as mentioned here ( Calendar Essentials )are included already.

I haven't installed any feature pack.

Avatar

Correct answer by
Employee

anushap40132887​ - If there is an issue with styles, it has to be a problem with clientlibs. If you are sure(just double check once), that all required clientlibs are included, it can probably also mean that either :

1. Customization wasn't removed properly, some mapping between resource types remain.

2. Customization wasn't implemented correctly and you made changes to some OOTB resource mappings.