Ticket #1703 (new defect)

Opened 13 years ago

Last modified 13 years ago

Portlet cache parameters GS initialisation

Reported by: gracinet Owned by: gracinet
Priority: P2 Milestone: CPS 3.5.7
Component: CPSPortlets Version: 3.4.0
Severity: minor Keywords: portlet cache parameters event
Cc:

Description

Portlets created by Generic Setup have wrong cache parameters. Namely, the list of interesting events is empty after the import. A call to portlet.resetInterestingEvents solves the observed cache-related problems.

Reminders: portlet interesting events are object-level granular, which is potentially great but doesn't get leveraged. They simply are reset by cpsportlet_edit.py, afaict.

I plan to have the XML adapter call the above method if the list of events is empty.

Change History

comment:1 Changed 13 years ago by gracinet

  • Severity changed from critical to minor

Digging a bit further:

  • the tool's rebuild_portlets(), which is exposed in the Rebuild ZMI tab, calls resetInterestingEvents() on each portlet
  • the GS adapter for the portlets *tool* calls rebuild_portlets().

The latter means that the described issue applies to those extension profiles that don't have a portlets.xml file only. Putting a dummy one in the profile and running the step (actually, twice !) solves the issue, too.

In any case, the situation isn't very user-friendly. An option would be to lift the call of rebuild_portlets() to the import step handler, at the very end of the process.

Note: See TracTickets for help on using tickets.