Turns out I forgot to make my viewlets theme specific.
I added
layer=".interface.IThemeSpecific" to my newly registered viewlets
in my browser/configure.xml and that did the trick.
<browser:viewlet
name="jalugskin.global_sections"
manager="plone.app.layout.viewlets.interfaces.IPortalHeader"
class=".viewlets.GlobalSectionsViewlet"
permission="zope2.View"
layer=".interfaces.IThemeSpecific"
/>
This was mentioned in the tutorial
http://plone.org/documentation/tutorial/customizing-main-template-viewlets,
I somehow neglected it.
On 10/16/07, David Bain <[EMAIL PROTECTED]> wrote:
>
> Why are changes to the viewlets.xml of one skin affecting other skins on
> other plone instances?
>
> I've created a skin that removes the plone.global_sections and adds a
> custom global_sections
> works great in the instance with my custom skin! except in other
> instances, that don't use the custom skin I now have two global_sections.
> This is happening, even with newly added instances.
>
> I've an explanatory screenshot.
>
> Below is my code:
>
> browser/configure.zcml
>
> ---snip ----
> <browser:viewlet
> name="jalugskin.personal_bar"
> manager="plone.app.layout.viewlets.interfaces.IPortalHeader "
> class="plone.app.layout.viewlets.common.PersonalBarViewlet"
> permission="zope2.View"
> />
>
> --- snip ---
>
> profiles/default/viewlets.xml
>
> --- snip ----
> <order manager="plone.portalheader" skinname="JALUGSkin">
> <viewlet name="plone.site_actions"
> insert-before="*"
> />
> <viewlet name="jalugskin.global_sections"
> insert-before="plone.searchbox"
> />
> <viewlet name="jalugskin.personal_bar"
> insert-before=" plone.searchbox"
> />
> <viewlet name="plone.searchbox"
> insert-before="plone.logo"
> />
>
> </order>
> <hidden manager=" plone.portalheader" skinname="JALUGSkin">
> <viewlet name="plone.global_sections" />
> </hidden>
>
> --- snip ----
>
>
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
