Ticket #2485 (new task)

Opened 8 years ago

Last modified 8 years ago

Main Content Portlet for backwards compatibility

Reported by: gracinet Owned by: gracinet
Priority: P2 Milestone: CPS 3.6.1
Component: CPSDefault Version: 3.5.2
Severity: normal Keywords: Main content portlet widget cpsskins
Cc:

Description

The Main Content portlet has been introduced with CPS 3.4, in order to provide a page rendering entirely based on portlets, which provided more flexibility than the direct ZPTs that existed before : it could be on the page or not.

With CPSDesignerThemes, we don't need it any more, since we have an XML tag (cps:main-content) for the same purposes ; removing it was a consequence of the lift of dependency to CPSSkins in the 3.6 branch.

In CPSDesignerThemes, Main Content Portlets are supported, but just as markers.

Now exported themes, or themes written for 3.5 will need adaptation that cannot be really automatic, since it was with other portlets in the content_well slot. In some cases, we might need the added flexibility that portlet visibility conditions provide.

What remains of this portlet (layout, type) and instantiation should be done again in a separate profile.

Change History

comment:1 Changed 8 years ago by gracinet

The default theme has been adapted

Note: See TracTickets for help on using tickets.