search

zenoss / ZenPackGenerator

Proof of Concept for streamlining zenpack development.
Other
5 stars 3 forks source link

wiring issue fixed? #19

Closed dougsyer closed 11 years ago

dougsyer commented 11 years ago

I havent started a new ZenPack to see if this is fixed yet but the last time I tried to use the Generator I noticed that there wasn't a viewlet set up in $ZPDIR\configure.zcml or the javascript that registers the non-plural/plural names.

ie this WAS in configure.zcml <browser:viewlet name="js-ZenPacks_NWN_CiscoWAAS" paths="/++resource++ZenPacks_NWN_CiscoWAAS/js/ZenPacks_NWN_CiscoWAAS.js" for="*" weight="20" manager="Products.ZenUI3.browser.interfaces.IJavaScriptSrcManager" class="Products.ZenUI3.browser.javascript.JavaScriptSrcBundleViewlet" permission="zope2.Public" />

this was MISSING:

<browser:viewlet name="js-ZenPacks.NWN.CiscoWAAS" paths="/++resource++ZenPacks_NWN_CiscoWAAS/js/ZenPacks.NWN.CiscoWAAS.js" for="*" weight="15" manager="Products.ZenUI3.browser.interfaces.IJavaScriptSrcManager" class="Products.ZenUI3.browser.javascript.JavaScriptSrcBundleViewlet" permission="zope2.Public" />

eedgar commented 11 years ago

This should be resolved I believe. Please do reopen if your still seeing this in the latest code.

dougsyer commented 11 years ago

thanks

From: Eric Edgar [mailto:notifications@github.com] Sent: Friday, August 23, 2013 1:31 AM To: zenoss/ZenPackGenerator Cc: Doug Syer Subject: Re: [ZenPackGenerator] wiring issue fixed? (#19)

This should be resolved I believe. Please do reopen if your still seeing this in the latest code.

— Reply to this email directly or view it on GitHubhttps://github.com/zenoss/ZenPackGenerator/issues/19#issuecomment-23144258.

Note: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately.