Using the original collection.pt template instead of its own

[jmce]

I installed redturtle.portlet.collection in a Plone 4.1.6 instance, and it seemed ok until I created such a portlet. I then noticed that such portlets end up using the regular collection portlet template instead of the rtcollectionportlet.pt template in the package (thus ignoring the user-specified template for each portlet).

This may have something in common with this collective.portlet.contentleadimage issue collective/collective.portlet.contentleadimage#2 — in this case the problem wouldn't show up if I hadn't customized the original collection.pt [I haven't yet made a similar test for redturtle.portlet.collection, and time is quite short for much testing, but will share here any additional info I may get).

[keul]

Not sure to understand, let my try.

rt.portlet.collection extends the basic Plone portlet collection. If you customized the basic collection portlet renderer through a <plone:portletRenderer directive, you replaced the renderer for all collection and subclasses.

I never use the <plone:portletRenderer exaclty for this reason.

Is this your issue?

[jmce]

I added no plone:portletRenderer directives — I had only customized the basic collection.pt via the ZMI (portal_view_customizations). Meanwhile i also customized rtcollectionportlet.pt in the same way and now it is actually being used instead of the basic template — so it seems ok as a workaround, but I'll report any side effects I may find. Meanwhile, wondering if I've just found one, even if not specifict to this package, trying to use tag() on a image field from a template made for redturtle.portlet.collection collective/collective.contentleadimage#7

[keul]

Ok thanks, we'll try to reproduce the issue

[jmce]

Also in the context of collective/collective.contentleadimage#7 --- curious why the customized rtcollectionportlet.pt in portal_view_customizations belongs to "jmce" [my Plone account, with Manager role] instead of to "admin", since I'm reaching the ZMI separately as "admin". I tried now removing the customized copy, logged out from the "Plone side" (same browser but different URL, instead of the tunneled localhost:... I use for the ZMI) and customized it again --- the customized rtcollectionportlet.pt once again belongs to "jmce" [maybe because the product itself was activated from Plone as "jmce"?].

Anyway, I'm not sufficiently acquainted w/ much of it to be sure if this is actually relevant for the other [contentleadimage] 'Unauthorized' bug.