Calendar component is not available in AEM 6.3 page | Community
Skip to main content
A
anushap40132887
Level 3
March 7, 2018
Solved

Calendar component is not available in AEM 6.3 page

  • March 7, 2018
  • 5 replies
  • 4803 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Rahul_Bhardwaj

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.

5 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
March 7, 2018

Adding a Calendar to a Page Calendar Feature

-Kautuk

Kautuk Sahni
A
anushap40132887Author
Level 3
March 8, 2018

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

Rahul_Bhardwaj
Adobe Employee
Rahul_BhardwajAdobe Employee
Adobe Employee
March 8, 2018

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?

A
anushap40132887Author
Level 3
March 12, 2018

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.

Rahul_Bhardwaj
Adobe Employee
Rahul_BhardwajAdobe EmployeeAccepted solution
Adobe Employee
March 12, 2018

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.

Terms & ConditionsAccessibility statement

Loading footer...