-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Maurits van Rees wrote:
> Op 28-09-10 06:23, Andreas Jung schreef:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I have a content-type "Leitlinie" and a content-type specific portlet.
>> The content-type should be displayed together with the portlet in the
>> left column. I am using
>>
>>   23<assignment
>>   24     purge="True"
>>   25     manager="plone.leftcolumn"
>>   26     category="content_type"
>>   27     key="Leitlinie"
>>   28     />
>>
>> for blocking all portlets (including the navigation portlet)
> 
> I would expect this to mean: purge any portlets that are specifically 
> set for this content type.  Portlets assigned to a location would still 
> show up, as is indeed happening.
> 
> 
>> and
>>
>>   30<assignment
>>   31       type="dgho.onkopedia.portlets.LeitlinieInhaltPortlet"
>>   32       manager="plone.leftcolumn"
>>   33       category="content_type"
>>   34       key="Leitlinie"
>>   35       insert-before="*"
>>   36>
>>
>> for adding my own portlet.
>>
>> However purging the portlets does not seem to work. The navigation
>> is still showing up.
>>
>> <blacklist...>
>>
>> also does not work for me.
>>
>> http://plone.org/products/plone/roadmap/203
>>
>> mentions 'location' as required key - however in my case
>> 'location' does not make much sense since a 'Leitlinie'
>> may appear in various folders within the site.
> 
> What I see when I blacklist content type portlets from a location, say 
> simply '/' for the Plone Site root, is that any portlets specifically 
> set for any content type are not shown; portlets not limited to a 
> content type are still shown.
> 
> I highly suspect what you want is not possible out of the box.
> 
> Possibly you could override the 
> plone.app.portlets.interfaces.ILeftColumn manager for this specific 
> content type, or do a patch on the code that fetches the registered 
> portlets.

I "resolved" the problem right now by hiding the navigation portlet
through a conditional CSS (checked by portal_type) :-)))

Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQGUBAEBAgAGBQJMoa7KAAoJEADcfz7u4AZjWoQLwJqSqLPRVMm7hum8r+FSieC4
gl40GAKFVLxzzdgjwZSNOoz2NY3MC+GKFQqKjEgaWD/70+HNY/LSYhX6BVzB6ZhQ
ZlNDEfUux9c6OAt8U0RobJrtTfLNuHYam9N885f7hy5FqHdh1tnp1k8ARd5+/63R
p7rDjwn7iqeQoOSRDo72+XeAdSM1KOIiNeziiBRDmfv4IzGsmChl2+DXGZcjwGIB
HNpRL1PyhCpslEwNxSNTZ91wjbdYukszqPMImRlXO6JfEeP7qiz43zcKwRHgrTq0
d+/kUirRiMl5H41Gg1iQltJagwAfiEbEtE2SESkurlPdEtJxrjlaSX1ro1Fvb5aU
EnkoJV4d2qZEjjlt5jhgq5n6oeF8+aJpfF5uNgwhil+mnkVFgKu/kZw+7xF9fTm/
r6j0PtEvZZq4zU3j17Z5neyoV8zUXok4CLyChQMLYyUmOatkImRT7CLEfKCEwoWU
HbltpRsVNK0Hlm5AySwaLyUPPuLzaKA=
=OJ1C
-----END PGP SIGNATURE-----

<<attachment: lists.vcf>>

_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers

Reply via email to