All these debugging tips are very helpful. But the OP said that there were two versions of the page that in theory should be identical, except that one was a static HTML page and the other was generated by the CMS, and the static page works but the CMS page doesn't.
If that is truly the case, then there is obviously some difference between the two versions of the page, and the problem has to be in that difference. Diffing the two versions as shown by View Source should reveal the problem immediately. Diffing is easier than debugging any day. :-) -Mike > -----Original Message----- > From: jquery-en@googlegroups.com > [mailto:[EMAIL PROTECTED] On Behalf Of donb > Sent: Tuesday, December 09, 2008 6:57 PM > To: jQuery (English) > Subject: [jQuery] Re: TableSorter vs CMS > > > My guess is that the 'CMS' inserts some onload code that > interferes with your jQuery code that's supposed to run on page load. > > If you haven't already, get fthe Frefox browser and the > Firebug addin. You will be able to step through the > javascript as the page loads, to see what is actually > happening. There's possible a javascript error occurring > that you aren't even aware of, and again Firefox will let you > see the details of any that DO occur. > > On Dec 9, 9:39 pm, "David Blomstrom" <[EMAIL PROTECTED]> > wrote: > > What constitutes "manipulation"? It's a dynamic table, so I use PHP > > and a MySQL query to "populate" it with data. I removed a > PHP script > > that gave each table row a class - though I didn't touch a similar > > touch that gives each table cell a class. > > > > At any rate, I'll replace the entire dynamic table script with a > > simple table from my source code tomorrow and see how that works. > > > > Thanks for the tip. > > > > > > > > On Tue, Dec 9, 2008 at 4:20 PM, MorningZ <[EMAIL PROTECTED]> wrote: > > > > > Understanding > > > > > $(document).ready(function() > > > { > > > $("#myTable").tablesorter({ widgets: ['zebra']} ); > > > } > > > ); > > > > > would go a long way to understanding why/how... > > > > > That code gets executed *one single time*, when the page > is pulled > > > up and the DOM is "ready" > > > > > if at some point after that, you manipulate "#myTable", then the > > > tablesorting functionality is *gone* and it will need to > be wired up > > > upon re-population...- Hide quoted text - > > > > - Show quoted text - >
