I tried to use tablemanager for small tabular data in node bodies that can be easily managed by not so web affine users.

I get following error message when I want set a default column sort when admin/edit a table, but don't set that columns as 'Allow sorting on column 1?':

Default sort column set to column 1 - which isn't set to be sortable.

This isn't good, because I want the table to be sorted by a column for the visitor, but there is no need for a sorting user interface on that table. The only way is to set that option 'Allow sorting on column 1?' for that column, but that generates that sort user interface and adds a different style on that column, which is unwanted in my case.

Alternatively, a param for column sorting in the tablemanager tag like would be ok.
Or a weight field for administration for sorting the rows, that is hidden when viewing tables.

I can try to get rid off the visible sort user interface in the view by adding custom css, but it will still leaves the column sort link in.

Comments

pobster’s picture

From the bottom of the README.txt file;

------
To do:
------

o Add an 'invisible' setting so that a row isn't displayed in main display function but is still
present when a row is added/ edited (useful for comments? hiding old rows?)
o Perhaps add an automatic column of 'Submitted by' (if wanted? maybe as a data type?)
o Remove the requirement that a column *must* be sortable to be sorted - it's no longer necessary
and a nice feature to sort on a default column and not have to allow it be changed by an end user

Note that it *was* necessary at one point, Drupal (4.6.x I seem to remember?) wouldn't allow a column to be sorted by default unless it was deemed to be sortable. I don't really know if this is even still the case? But it's besides the point really in this revision of Tablemanager because I sort the rows myself, I'm just not overly bothered about fixing/ adding to the 5.x release any more... The development branch has moved to 6.x and when I make an actual release of it (not just a dev release) don't worry I absolutely *will* backport it to 5.x - it'll be missing a few things like sortable columns (which rely on jquery) but it'll be more functional than the release you're currently using which tbh, was a hacky upgrade from the original 4.6.x version. Which incidentally, was the first thing I'd ever written in php which is pretty much why it doesn't look so good. That was three years ago now though, don't panic - I'm a lot more proficient now ;o)

Pobster

pobster’s picture

Status: Active » Closed (won't fix)

Won't fix for this revision... I'll just backport the 6.x dev branch when it's in a more stable state.

Pobster