Ticket #2090 (new defect)

Opened 10 years ago

Content portlet robustness

Reported by: gracinet Owned by: jmorliaguet
Priority: P2 Milestone: CPS 3.5.7
Component: CPSPortlets Version: TRUNK
Severity: normal Keywords:


Content portlets can crash if there are catalog inconsistencies. Of course, there's CPSSkins' crash shield, but that's not enough. Even without proper bugs like #2004, Catalog inconsistencies can occur with non transactional catalogs, such as CPSLuceneCatalog.

For basic renderings, content portlets shouldn't even try and lift the object from ZODB, and use brains instead (but that also means that users can follow outdated links). At least, they should survive missing objects in ZODB.

Note: See TracTickets for help on using tickets.