Admin updates to CMS portlet decorations don't take affect

[thorntond]

In JBoss Portal 2.6, the default for the CMS portlet rendering seems to be emptyRenderer. Updating the rendering properties in the Management Portlet has no effect.

Management Portlet - Portal Objects - Portals>default Portal>default Page>CMSPortlet Window theme properties

I set all renderers to divRendererNoAjax but this had no effect on the CMS portlet. I also tried divRenderer.

What I would like to do is create multiple instances of the CMS Portlet, each with a different index page and all portlet instances rendered with title bars (decorations).

When I add cms portlets through Page layout, I get peculiar behaviour like the cms portlet index page not setting properly and the theme decorations not setting properly.

In portal 2.6, can I add multiple CMS portlet instances as admin and not have to update xml property files or recompile the portal?

Danny

[theute]

Use the CMS content-type when you add a window

[thorntond]

I added a CMS portlet as user admin with the content-type set to CMS. Most of the time it sets the CMS Portlet content correctly but sometimes it does not. I haven't spent any time trying to figure out why it sometimes won't set properly.

Updating the CMS Portlet rendering properties in the Management Portlet is having no affect on the rendering of the CMS Portlet.

Danny

[theute]

I will have a look at the decorations issue. Thanks.

[theute]

Can you try to set "DecorateContent" to true on the portal:service=ContentRenderer,type=cms Mbean declared in:
portal-cms.sar/META-INF/jboss-service.xml

It should behave as you expect (note that you can still decide to hide decorations for a particular windows using the windows properties)

[thorntond]

With the DecorateContent set to true, the CMS Portlet window does render with decorations.

[theute]

This is what you wanted ?

[thorntond]

This is the way I would like the CMS Portlet to render. Thanks Thomas. However, I think it is a bug in Portal 2.6 if setting the rendering type in the management portlet has no affect.

[theute]

Yep this is misleading. I wasn't aware of this new behavior.
Fortunately this can be worked-around easily.

We'll clean that up in a future release, thanks for reporting this.