#250 — Can't manage portlets on Poi Issue Trackers

by David Beitey — last modified May 18, 2012 08:50 PM

State	Resolved
Version:	2.0.1
Area	Functionality
Issue type	Patch
Severity	Medium
Submitted by	David Beitey
Submitted on	Mar 14, 2011
Responsible	Maurits van Rees
Target release:	—

Return to tracker

Testing Plone 4.0.4 and Poi 2.0.1.

At present, Poi issue trackers can't have portlets assigned or controlled. For instance, PoiIssue content automatically receives portlet assignments from parent folders, and one may wish to disable these portlets in the context of the issue tracker. Currently, this is not possible.

Adding this to Poi's configure.zcml allows portlet management:

<class class=".content.PoiTracker.PoiTracker">
    <implements
      interface="plone.portlets.interfaces.ILocalPortletAssignable"/>
  </class>

As for the 'Manage Portlets' fallback link, it doesn't appear for the issue tracker, as the PoiTracker content type doesn't provide the Products.ATContentTypes.interface.IATContentType interface, required by the viewlet:

<browser:viewlet
        name="plone.manage_portlets_fallback"
        for="Products.ATContentTypes.interface.IATContentType"
...

Providing this interface in the same method above works, but probably isn't best practice.

Added by Maurits van Rees on Sep 06, 2011 09:57 PM

Issue state: Unconfirmed → Resolved

Responsible manager: (UNASSIGNED) → maurits

Makes sense. I have added the ILocalPortletAssignable interface to both trackers and issues in r244223.

I don't see that the viewlet requires the IATContentType interface though. On Plone 4.0.9 with plone.app.layout 2.0.11 I simply see that viewlet registered for ILocalPortletAssignable. This may have been changed recently for compatibility with dexterity. With the above change I see the link just fine.

No responses can be added.