Nope, nothing wrong in what you are doing.
Just make sure that trigger is called on the table and not the row.
Ex.
$("table").trigger("update");
/c
2007/12/3, Adam Kroll <[EMAIL PROTECTED]>:
>
>
> I'm having problems with tablesorter 2.0.1 and removing rows. I'm
> allowing users to remove rows, and after a removing a row using a call
> to remove() I'm calling trigger("update"), but if I remove a row and
> then resort it brings back the row I just removed.
>
> It looks like trigger("update") rebuilds the cache which should ignore
> the row I just removed, but it always comes back.
>
> Any ideas, or am I just totally missing something here?
>
