cq:CalendarEvent nodetype is deprecated in 5.6.1 | Community
Skip to main content
A
aemanonymous
Level 3
May 5, 2016
Solved

cq:CalendarEvent nodetype is deprecated in 5.6.1

  • May 5, 2016
  • 4 replies
  • 1048 views

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.

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 Lokesh_Shivalingaiah

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

4 replies

JK_Kendall
JK_Kendall
Level 9
May 5, 2016

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

A
aemanonymousAuthor
Level 3
May 5, 2016

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"/>

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
Level 10
May 6, 2016

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

A
aemanonymousAuthor
Level 3
May 6, 2016

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.

Terms & ConditionsAccessibility statement

Loading footer...