내 커뮤니티 업적 표시줄을 확대합니다.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.

해결됨

cq:CalendarEvent nodetype is deprecated in 5.6.1

Avatar

Level 4

While migrating from AEM 5.6.1 to 6.1, we have noticed that this node is deprecated. In the existing code, this node has been used as the primaryType for certain component includes in the templates instead of 'nt:unstructured' (probably for querying the repository). Could you please let me know how could we install this nodetype in aem 6.1. Also, please let me know if we should not introduce this deprecated nodetype.

1 채택된 해결책 개

Avatar

정확한 답변 작성자:
Level 10

yes, any such primary type has to be changed in AEM 6.1

원본 게시물의 솔루션 보기

4 답변 개

Avatar

Level 9

Did you read Upgrading to AEM 6.1 Communities?

The code for the 5.6.1 calendar feature uses JSP, not the SCF framework and HBS scripts.

AEM 6.1 also brought changes to the location and method for accessing UGC (no more reverse/forward replication).  See Community Content Storage (often referred to as SRP).

I would suggest exploring what it would take to upgrade to SCF.

- JK

Avatar

Level 4

Thanks JK for proving more insight into the SCF Framework.

However, in our implementation this is being used for an event detail component that renders event details on the page based on data coming from an external system. This component is configured into a template with jcr:primaryType as 'cq:CalendarEvent' instead of 'nt:unstructured' and we have logic to create a new page using this template whenever new events are coming from external system.

 

<jcr:content
        jcr:primaryType="cq:PageContent"
        sling:resourceType="foobar/components/pages/eventPage">
        <event
            jcr:lastModified="{Date}2014-02-14T18:16:34.126+08:00"
            jcr:primaryType="cq:CalendarEvent"
            sling:resourceType="foobar/components/eventDetail"/>

Avatar

정확한 답변 작성자:
Level 10

yes, any such primary type has to be changed in AEM 6.1

Avatar

Level 4

Thanks for the update Lokesh. We will make this change eventually.

However, as quick work around, just thought of asking if it is really possible to reintroduce this nodetype in AEM 6.1 by installing a package or something.