Ticket #11615 (confirmed Bug)
plone.app.customerize.tool.ViewTemplateContainer(portal_view_customizations) uses two inspecific ids for customizations
Reported by: | dieter | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 4.x |
Component: | General | Version: | 4.1 |
Keywords: | view_customization | Cc: | dieter@… |
Description
"plone.app.customerize.tool.ViewTemplateContainer", used to implement "portal_view_customizations", uses ids formed of registered for interface and template name. These ids are not sufficiently specific.
For example, a standard Plone registers two "login.pt" for "zope.interface.Interface" in "plone.app.openid.portlets" and "plone.app.portlets.portlets", respectively. Both use "zope.interface.interface-login.pt" as id. As a consequence, trying to customize both templates fails with a "BadRequest: The id "zope.interface.interface-login.pt" is invalid - it is already in use."
I am not yet sure whether this only prevents to customize several views registered for the same interface with the same template name or whether this already yields unpredictable results for a single customization when multiple such views exist (using the customized template for views that should not be modified).
Please always specify which Plone version that is affected.