CQ Portals and Portlets

[kishan_gowdhama]

Hi,

We are trying with "Using CQ as a Portal" by following the docs at http://dev.day.com/docs/en/cq/current/administering/cq_as_portal.html (section Using CQ as a Portal).

We are using CQ 5.6.1 war with java6 and tomcat6 in windows7 env.

    Step1: We installed CQ5 With an Application Server (tomcat6)

    Step2: Install the Portlet component and shared libraries

    Step3: Add the Portlet component to Sidekick

We are blocked at Step3, since we could not Add the Portlet component to Sidekick. The Portlet component is not getting displayed in the GENERAL component category.

We are not seeing any errors in the logs as well.

Can anyone please help us on this?

Thanks for your help in advance.

Regards,

Kishan. G

[Sham_HC]

Have you selected components from design mode?

If so Any error in the firebug console

[smacdonald2008 · Accepted solution]

If this is not working as documented, please open a ticket here:

http://helpx.adobe.com/marketing-cloud/experience-manager.html 

[kishan_gowdhama]

Hi,

Thank you for the reply.

Followed all the steps as mentioned in http://dev.day.com/docs/en/cq/current/administering/cq_as_portal.html section “Using CQ as a Portal”

But in the edit mode as mentioned in section “Adding the Portlet component to Sidekick”, the ‘Portlet’ component is not in the sidekick ‘General’ component category. See attached screen shot below.

There are few errors in fire bug console, but not sure that caused this issue.

Thanks for your help in advance.

Regards,

Kishan. G

[j_purchase]

It looked like I double posted. so I deleted on and then they were both gone. So I'll re-post so the thread makes sense.

Basically, there are errors in the log when I try to install cq-portlet-components-5.4.20.zip:

 Error during processing of /libs/foundation/components/portlet/dialog: javax.jcr.nodetype.ConstraintViolationException: No child node definition for dialog found in node /libs/foundation/components/portlet

As you suggest, I'll raise a ticket. Thanks

[kishan_gowdhama]

Hi,

A ticket was raised a long time back.

In the mean time we got a fix as below from Edouard Lafargue od Adobe and it works.

   There seems to be a bug in the "cq-portlet-components.zip” package. When you install it in the package manager, the “portlet” node does not have the right type - it is created as a folder. This means     that there cannot be a “cq:Dialog” child node underneath, and therefore, the Sidekick won’t display the Portlet component, since it only displays components that have dialogs.

    Now for the fix: after installing the package, if you unzip cq-portlet-components.zip and look at the “dialog.xml” under jcr_root/libs/foundation/components/portlet/ you will see the structure that has to     be recreated: just a couple of nodes. You will have to rename ‘/libs/foundation/components/portlet” to something like “portlet_1” in CRXDELite, then create a cq:Component called portlet, and move     the child nodes of portlet_1 into it.

You can try the above,

Thank you.

Regards,

Kishan. G

[nsvsrk]

Hi Kishan,

I am starting a POC on creating a Portal page using AEM and so wanted to leverage your experience here.

After you built the portal, do you see the portal page with portlets, which could be dragged and dropped on to the page from somewhere? (May be sidekick)

Admin could specify access rights at Portlet level? In a normal AEM page, it could be done only at page level and not at component level.

Kindly share your experiences, for the benefit of this community.

I highly appreciate your guidance here.

Thanks,

Rama.