Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix reverse_name issues with using ContentsEntryMixin in another model. #5

Open
vdboor opened this issue Apr 24, 2013 · 0 comments
Open

Fix reverse_name issues with using ContentsEntryMixin in another model. #5

vdboor opened this issue Apr 24, 2013 · 0 comments
Labels
bug

Comments

@vdboor
Copy link
Contributor

vdboor commented Apr 24, 2013

When the ContentsEntryMixin is used in another model, Django raises an error that the related_name for the contents field is already used. This likely needs to be fixed in https://github.com/edoburu/django-fluent-contents and it's visible in the blogs app.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vdboor