You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added it to INSTALLED_APPS: INSTALLED_APPS += ['todo']
I tried migrating: python manage.py migrate todo
But it bombs with:
ERRORS:
contacts.Comment.creator: (fields.E304) Reverse accessor for 'Comment.creator' clashes with reverse accessor for 'Comment.author'.
HINT: Add or change a related_name argument to the definition for 'Comment.creator' or 'Comment.author'.
todo.Comment.author: (fields.E304) Reverse accessor for 'Comment.author' clashes with reverse accessor for 'Comment.creator'.
HINT: Add or change a related_name argument to the definition for 'Comment.author' or 'Comment.creator'.
That looks like a fairly simple issue, but surprises me immensely to see in the pip installed code. It seems simple enough to me, in that inside the Comment model:
Tendenci and todo both implement a Comment model with ForeignKey to AUTH_USER_MODEL and neither specified a related_name argument so they both attempt to implement comment_set on the user. This is actually worth a fix in both apps, as neither should be attaching such a contextless comment to users.
The text was updated successfully, but these errors were encountered:
Love this. Just taking a quick spin plugging it into a development version of our tendenci site (for a club)
Following Installation here: https://django-todo.readthedocs.io/en/latest/
SITE_ID = 1
, all goodpip install django-todo
, all goodINSTALLED_APPS += ['todo']
python manage.py migrate todo
But it bombs with:
That looks like a fairly simple issue, but surprises me immensely to see in the pip installed code. It seems simple enough to me, in that inside the Comment model:
django-todo/todo/models.py
Line 129 in 20196a1
Tendenci and todo both implement a Comment model with ForeignKey to AUTH_USER_MODEL and neither specified a related_name argument so they both attempt to implement
comment_set
on the user. This is actually worth a fix in both apps, as neither should be attaching such a contextless comment to users.The text was updated successfully, but these errors were encountered: