Question

I’m restructuring a page for a client, and I’m having some issues with the jQuery code I implemented on the page.
There’s a pop-up lightbox that uses Prototype which appears when the page loads, and then there’s marquee/scrollers on the top and right that I put there that use jQuery. I’m really unsure about what’s causing the error.
I’m familiar with jQuery’s noConflict, but I’ve tried pretty much every variation of it on this page and I still get an error – after a few seconds the marquees stop – and IE displays that “Errors on page” dialog, referencing line 464 (“Array length must be assigned a finite positive number”).
Here is the page: -link removed by author-
Here is prototype.js: -link removed by author-

I have absolutely no idea what is causing this error and JavaScript isn’t my strongest side.

Answer 1

When I first started seeing this error, I was Googling around for more general “Prototype + jQuery” errors, when I should have been looking for a solution specific to the exact problem I was dealing with.
Adding the terms “array length” and “line 464” actually led me to the solution to this specific problem, and here it is:

1. Updated from prototype v1.4 to v1.5.1.2 (v1.7, the latest release,
   didn’t work right and even produced a stack overflow error).

2. Changed around the order of the scripts, and changed noConflict:

   <script src="/scripts/jquery-1.5.2.js" type="text/javascript"></script> 
   <script src="/scripts/jquery.Scroller-1.0.src_4.js" type="text/javascript"></script><!-- all _$_'s replaced with _jQuery_ -->
   <script type="text/javascript">
   <!--
   // more jquery, all $'s replaced with jQuery
   -->
   </script>
   <script type="text/javascript"> 
   <!--
   jQuery.noConflict();
   -->
   </script>       
   <script src="scripts/prototype-1.5.1.2.js" type="text/javascript"></script> 
   <script type="text/javascript">
   <!--
   // everything else, including prototype scripts
   -->
   </script>
   

And that’s it! Now I don’t get the “Line 464” error and all scripts work fine.
Thank you @Ken and @Diodeus for leading me to the solution.