In r145, parse_tag_input() do set() and sort() on tags.
So application cannot view original structure of tag input.
I suggest an optional argument to disable both call,
to preserve original structure of user tag input.
As suggested in issue 95, AFAIK, model field name of TagField
and registered attribute name should be different to work well.
So real DB layer can works with set() and sort() as before,
while http response parse model field on the fly
to show content of tag input as is.
Original issue reported on code.google.com by kei...@gmail.com on 18 Aug 2008 at 1:34
Original issue reported on code.google.com by
kei...@gmail.com
on 18 Aug 2008 at 1:34