Hi Moritz,

I think the documentation is a bit misleading here. It sounds as it was optional to put a hidden field with class SortData which actually contains the data relevant for sorting. But following the code, Init() always looks for elements with class SortData and gets it's content by using .val() which only works for form fields. Please see my attached patch for a working example.

Marc

Am 13.05.15 um 11:04 schrieb Moritz Lenz:

Hi all,

I tried to make some tables in the Admin interface sortable with Javascript.

I tried the patch that's in the attachment, on top of the following commit on the master branch:

commit f0278db35026e6aad260e5559eab45c314f393df
Author: Moritz Lenz <mlenz@noris.net>
Date: Wed May 13 10:57:16 2015 +0200

Try to make the AdminQueue-Table sortable

After applying the patch (and rebuilding the config), when I click on the "Name" column in AdminQueue, I get the down-facing triangle that indicates that the table is sorted by this column, and when pressing agian, I get the up-facing triangle, but the table isn't sorted at all, all rows stay just how they are.

What am I missing here? Or is this a bug in the table sorter?

I've tried to model the HTML after the sortable table in AgentTicketZoom.tt, since there's no documentation in the Javascript about how the HTML should look like.

Cheers,
Moritz
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

-- 
--  

Marc Bonsels
Research & Development
 
OTRS AG
Norsk-Data-Straße 1
61352 Bad Homburg
Germany 

T: +49 (0) 6172 681988 0
F: +49 (0) 9421 56818 18
I:  http://www.otrs.com/

Business location: Bad Homburg, Country Court: Bad Homburg, HRB 10751, VAT ID: DE256610065
Chairman: Burchard Steinbild, Managing Board: André Mindermann (CEO), Christopher Kuhn, Sabine Riedel