is it my fault, documentation problem, or known issue?

[GoogleCodeExporter]

hi folks
just started with django-tagging and run into the problem:

I make a table with

class Expedition(models.Model):
  tags = TagField()

and I do:

tagging.register(Expedition)

Trying to add item in admin provides exception:

http://dpaste.com/37479/

If I remove call to tagging.register, everything works just fine.

HTML docs do not mention register call, overview.txt uses it, but there's
no mention that using both at the same time is wrong.

Thanks!

Original issue reported on code.google.com by druzhi...@gmail.com on 1 Mar 2008 at 1:59

[GoogleCodeExporter]

Ouch! I've just been bitten by this too. Again, removing the call to 
tagging.register fixed it for me. A doc update 
would be appreciated.

Original comment by dan.fairs on 14 Mar 2008 at 3:53

[GoogleCodeExporter]

I can't see the dpaste entry anymore, but i think i have a similar problem 
here. With
svn version 132. If in my model have a TagField() (and regiter it) then in the 
admin
interface i can't insert tag, because it's complaining about a NULL value. But 
if i
use TagField() without the register function, all works fine, in the Admin 
interface
i have the tag fields. Obviously i can't access to special tagged object from my
model. And viceversa, if i use only register function i can access special 
object
from the model, but the tags field in the admin is missing.
It would be nice if we could use both!

Original comment by blackf...@yahoo.it on 29 Apr 2008 at 9:47

[GoogleCodeExporter]

I'm definitely having this problem too, it really is a pain not having the 
shortcuts
on the model that register provides, but at the same time we need the TagField.

Original comment by JACortinas on 25 Nov 2008 at 2:02

[GoogleCodeExporter]

tagging.register will now catch these cases in r174.

Original comment by bros...@gmail.com on 22 Jan 2010 at 10:06

• Changed state: Fixed