Should be:

{{ value }}

not

{{ value }}

I’d prefer you use the django-apps Google Group for support requests though.

Exception Value:
‘WSSWSite’ object has no attribute ‘get’
Exception Location: /Users/ssteiner/.virtualenvs/wssw1/lib/python2.6/site-packages/django_tables/tables.py in _build_snapshot, line 261

It’s pretty much straight out of the docs, just with my own classes.

Any idea what’s going on?

I searched through the code but get() is not explicitly called anywhere in django-tables anywhere so I’m a little lost…

Thanks,

S

you should be able to use:

– “verbose_name” for the column header text.
– “name” – for the field name.
– “data” – specify a callable for custom formatting.

In other words, something along those lines might work:

    def format(row):
        if row['name_to_expose_as'] == 0: return "yes"
        else: return "no"
    name_of_field_in_model = tables.Column(name="name_to_expose_as", verbose_name="column header text", data=format)

I agree that how the different options interact is somewhat confusing right now, but I’m not yet quite sure what the right way would be to make it more straightforward. I’m reluctant to introduce many more arguments to Column(), since there are already so many, and I suspect that is to some extend where the confusion stems from.

Apart from that, I’d really prefer to use the mailinglist for future discussions.

I can accomplish this now with a db column, which contains 0 or 1, which gets custom formatted to “yes” or “no”, but I have to fix the column heading to the db column name.

the latest code is on Launchpad and the Bazaar repository linked to in the post. The current documentation is limited to the README file that is part of the distribution.

Generally, for questions please use the django-apps Group and prefix your message with “(tables)”:

http://groups.google.com/group/django-apps

As for your questions:

1) I’d need some code to reproduce this. Feel free to use django-apps, post a bug report on Launchpad, or send me an email (michael@elsdoerfer.info).

2) The parameter is actually called “order_by” – sorry, a mistake I made in this post here (now fixed). The README should be correct.

3) Sorry, I’m not quite sure what you mean here.

I got the package from pypi today, and I have few issues with it. Is that the right place to get your latest version? Where can I find additional documentation?

1) Every table column is followed by an empty column. I was able to counter this behaviour by inserting empty TH after each TH with content. Problem seems to be in ModelTable.
2) ModelTable.__init__ doesn’t accept the sort parameter.
3) How to use is_ordered_reverse (should be automatic after item 2 is fixed)?

I agree that your code should be included in contrib, although after some cleanup and documentation.