[GH-ISSUE #252] system check complaining... #212

New issue

Closed

opened 2026-02-26 09:36:35 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:36:35 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Jan 8, 2016).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/252

When cron ran the django-admin testuser command, this was sent via email:

System check identified some issues:

WARNINGS:
registration.RegistrationProfile.user: (fields.W342)
Setting unique=True on a ForeignKey has the same effect as using a OneToOneField.

    HINT: ForeignKey(unique=True) is usually better served by a OneToOneField.

Originally created by @ThomasWaldmann on GitHub (Jan 8, 2016). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/252 When cron ran the django-admin testuser command, this was sent via email: ``` System check identified some issues: WARNINGS: registration.RegistrationProfile.user: (fields.W342) Setting unique=True on a ForeignKey has the same effect as using a OneToOneField. HINT: ForeignKey(unique=True) is usually better served by a OneToOneField. ```

kerem closed this issue

2026-02-26 09:36:35 +03:00

kerem commented

2026-02-26 09:36:36 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Aug 27, 2016):

Temporary silenced it via:

SILENCED_SYSTEM_CHECKS = [
    'fields.W342',  # caused by django-registration-redux?
]

@ThomasWaldmann commented on GitHub (Aug 27, 2016): Temporary silenced it via: ``` SILENCED_SYSTEM_CHECKS = [ 'fields.W342', # caused by django-registration-redux? ] ```

kerem commented

2026-02-26 09:36:36 +03:00

Author

Owner

@elnappo commented on GitHub (Dec 27, 2016):

seems to be fixed with https://github.com/macropin/django-registration/pull/42

@elnappo commented on GitHub (Dec 27, 2016): seems to be fixed with https://github.com/macropin/django-registration/pull/42

kerem commented

2026-02-26 09:36:36 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Jan 21, 2017):

confirmed: the warning is gone after merging the PR.

@ThomasWaldmann commented on GitHub (Jan 21, 2017): confirmed: the warning is gone after merging the PR.