On Fri, Jun 22, 2012 at 12:27 PM, Melvyn Sopacua <m.r.sopa...@gmail.com> wrote: > On 22-6-2012 12:09, Bram de Jong wrote: > >> However, when I turn this field into a filter in the admin, instead of >> seeing the filter-versions as my string (i.e. "1.0.5rc3") I see it as >> the underlying database type (i.e.10000301) > > I suspected there is another code path that doesn't call to_python > properly, but let's rule out it's not the same as my issue: > Is this field a foreign key for the model that's being displayed?
It isn't. Where should I be digging to figure out the code path being called? Additionally clicking the filter will make things crash because I'm getting a string which is "10000301" if I do. Just to rule out simple stupidity on my part, here's the model field and form field I'm using. http://dpaste.com/762328/ - Bram -- http://www.samplesumo.com http://www.freesound.org http://www.smartelectronix.com http://www.musicdsp.org office: +32 (0) 9 335 59 25 mobile: +32 (0) 484 154 730 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
