I completely agree with what you said about frameworks. I'd use a different module, but nobody else makes one comparable to it. I reviewed about 6 or 8 modules before settling on this one. I completely understand the author's viewpoint, though - he originally authored the module over a year ago when jQuery wasn't being considered for inclusion into DNN and when MS AJAX inclusion was being hotly debated.
Clearly, they never *really *decided, and I'm caught in the lurch. However, I think the author sees the benefit of switching over to jQuery, it's just going to take him a while to get the new versions out the door. Thanks, Dave On Thu, May 7, 2009 at 4:37 PM, Eric Garside <gars...@gmail.com> wrote: > > Try using a try-catch block around the scriptaculous code? > > There's really no other way that I'm aware of to capture a javascript > error and continue processing. Though, depending on how crucial the > module is, you may consider using something else. 3 frameworks, 2 > major ones, on a site at the same time isn't ideal. > > On May 7, 4:08 pm, David Meiser <dmei...@gmail.com> wrote: > > This is slightly off topic, but if anybody can solve this, it'll be this > > mailing list. The basic question is: Is there a way to catch an error > > thrown in an external js library so that I can continue parsing the > > remaining javascript on the page? > > > > The more detailed version is this: I'm using DotNetNuke (DNN) for my > > website. A module that I'm using include Scriptaculous, DotNetNuke uses > a > > mixture of jQuery and MS AJAX. To avoid namespace pollution, the DNN > folk > > have used the jQuery prefix for jQuery functions and the $ shortcut for > MS > > AJAX (actually, I think this is the only way you can do this). The third > > party module uses $ to reference Scriptaculous. > > > > I think we all know where this is going: the namespace pollution of $ > > causes an error to be thrown very early on, leaving parts of my page > > unstyled (cornerz), dates unformatted, etc, etc, etc. The good news - > for > > me - is this only happens when an admin is logged in. > > > > My thought would be to catch the errors and continue parsing *my *portion > of > > the page. > > > > Thanks in advance, > > Dave >
