Skip to content

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

Open
@vdboor

Description

@vdboor

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions