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 -
