{"title":"System check framework","version":"3.0","locale":"pl","docname":"ref/checks","url":"/pl/3.0/ref/checks/","canonical":"https://djangodocs.dev/pl/3.0/ref/checks/","summary":"The system check framework is a set of static checks for validating Django projects. It detects common problems and provides hints for how to fix them.","html":"

System check frameworkLink to this heading#

\n

The system check framework is a set of static checks for validating Django\nprojects. It detects common problems and provides hints for how to fix them.\nThe framework is extensible so you can easily add your own checks.

\n

For details on how to add your own checks and integrate them with Django’s\nsystem checks, see the System check topic guide.

\n
\n

API referenceLink to this heading#

\n
\n

CheckMessageLink to this heading#

\n
\n
\nclass CheckMessage(level, msg, hint=None, obj=None, id=None)Link to this definition#
\n
\n\n

The warnings and errors raised by system checks must be instances of\nCheckMessage. An instance encapsulates a single reportable error or\nwarning. It also provides context and hints applicable to the message, and a\nunique identifier that is used for filtering purposes.

\n

Constructor arguments are:

\n
\n
level

The severity of the message. Use one of the predefined values: DEBUG,\nINFO, WARNING, ERROR, CRITICAL. If the level is greater or\nequal to ERROR, then Django will prevent management commands from\nexecuting. Messages with level lower than ERROR (i.e. warnings) are\nreported to the console, but can be silenced.

\n
\n
msg

A short (less than 80 characters) string describing the problem. The string\nshould not contain newlines.

\n
\n
hint

A single-line string providing a hint for fixing the problem. If no hint\ncan be provided, or the hint is self-evident from the error message, the\nhint can be omitted, or a value of None can be used.

\n
\n
obj

Optional. An object providing context for the message (for example, the\nmodel where the problem was discovered). The object should be a model,\nfield, or manager or any other object that defines a __str__() method.\nThe method is used while reporting all messages and its result precedes the\nmessage.

\n
\n
id

Optional string. A unique identifier for the issue. Identifiers should\nfollow the pattern applabel.X001, where X is one of the letters\nCEWID, indicating the message severity (C for criticals, E for\nerrors and so). The number can be allocated by the application, but should\nbe unique within that application.

\n
\n
\n

There are subclasses to make creating messages with common levels easier. When\nusing them you can omit the level argument because it is implied by the\nclass name.

\n
\n
\nclass Debug(msg, hint=None, obj=None, id=None)Link to this definition#
\n
\n\n
\n
\nclass Info(msg, hint=None, obj=None, id=None)Link to this definition#
\n
\n\n
\n
\nclass Warning(msg, hint=None obj=None, id=None)Link to this definition#
\n
\n\n
\n
\nclass Error(msg, hint=None, obj=None, id=None)Link to this definition#
\n
\n\n
\n
\nclass Critical(msg, hint=None, obj=None, id=None)Link to this definition#
\n
\n\n
\n
\n
\n

Builtin tagsLink to this heading#

\n

Django’s system checks are organized using the following tags:

\n\n

Some checks may be registered with multiple tags.

\n
\n
\n

Core system checksLink to this heading#

\n
\n

Backwards compatibilityLink to this heading#

\n

Compatibility checks warn of potential problems that might occur after\nupgrading Django.

\n\n
\n
\n

CachesLink to this heading#

\n

The following checks verify that your CACHES setting is correctly\nconfigured:

\n\n
\n
\n

DatabaseLink to this heading#

\n
\n

MySQLLink to this heading#

\n

If you’re using MySQL, the following checks will be performed:

\n
    \n

  • mysql.E001: MySQL does not allow unique CharFields to have a\nmax_length > 255.

    • \n

  • mysql.W002: MySQL Strict Mode is not set for database connection\n<alias>. See also Setting sql_mode.

    • \n
\n
\n
\n
\n

Model fieldsLink to this heading#

\n\n
\n

File fieldsLink to this heading#

\n
    \n

  • fields.E200: unique is not a valid argument for a FileField.\nThis check is removed in Django 1.11.

    • \n

  • fields.E201: primary_key is not a valid argument for a FileField.

    • \n

  • fields.E202: FileField’s upload_to argument must be a relative\npath, not an absolute path.

    • \n

  • fields.E210: Cannot use ImageField because Pillow is not installed.

    • \n
\n
\n
\n

Related fieldsLink to this heading#

\n
    \n

  • fields.E300: Field defines a relation with model <model>, which is\neither not installed, or is abstract.

    • \n

  • fields.E301: Field defines a relation with the model <model> which\nhas been swapped out.

    • \n

  • fields.E302: Accessor for field <field name> clashes with field\n<field name>.

    • \n

  • fields.E303: Reverse query name for field <field name> clashes with\nfield <field name>.

    • \n

  • fields.E304: Field name <field name> clashes with accessor for\n<field name>.

    • \n

  • fields.E305: Field name <field name> clashes with reverse query name\nfor <field name>.

    • \n

  • fields.E306: Related name must be a valid Python identifier or end with\na '+'.

    • \n

  • fields.E307: The field <app label>.<model>.<field name> was declared\nwith a lazy reference to <app label>.<model>, but app <app label>\nisn’t installed or doesn’t provide model <model>.

    • \n

  • fields.E308: Reverse query name <related query name> must not end\nwith an underscore.

    • \n

  • fields.E309: Reverse query name <related query name> must not contain\n'__'.

    • \n

  • fields.E310: No subset of the fields <field1>, <field2>, … on\nmodel <model> is unique.

    • \n

  • fields.E311: <model> must set unique=True because it is\nreferenced by a ForeignKey.

    • \n

  • fields.E312: The to_field <field name> doesn’t exist on the\nrelated model <app label>.<model>.

    • \n

  • fields.E320: Field specifies on_delete=SET_NULL, but cannot be null.

    • \n

  • fields.E321: The field specifies on_delete=SET_DEFAULT, but has no\ndefault value.

    • \n

  • fields.E330: ManyToManyFields cannot be unique.

    • \n

  • fields.E331: Field specifies a many-to-many relation through model\n<model>, which has not been installed.

    • \n

  • fields.E332: Many-to-many fields with intermediate tables must not be\nsymmetrical. This check appeared before Django 3.0.

    • \n

  • fields.E333: The model is used as an intermediate model by <model>,\nbut it has more than two foreign keys to <model>, which is ambiguous.\nYou must specify which two foreign keys Django should use via the\nthrough_fields keyword argument.

    • \n

  • fields.E334: The model is used as an intermediate model by <model>,\nbut it has more than one foreign key from <model>, which is ambiguous.\nYou must specify which foreign key Django should use via the\nthrough_fields keyword argument.

    • \n

  • fields.E335: The model is used as an intermediate model by <model>,\nbut it has more than one foreign key to <model>, which is ambiguous.\nYou must specify which foreign key Django should use via the\nthrough_fields keyword argument.

    • \n

  • fields.E336: The model is used as an intermediary model by <model>,\nbut it does not have foreign key to <model> or <model>.

    • \n

  • fields.E337: Field specifies through_fields but does not provide the\nnames of the two link fields that should be used for the relation through\n<model>.

    • \n

  • fields.E338: The intermediary model <through model> has no field\n<field name>.

    • \n

  • fields.E339: <model>.<field name> is not a foreign key to <model>.

    • \n

  • fields.E340: The field’s intermediary table <table name> clashes with\nthe table name of <model>/<model>.<field name>.

    • \n

  • fields.W340: null has no effect on ManyToManyField.

    • \n

  • fields.W341: ManyToManyField does not support validators.

    • \n

  • fields.W342: Setting unique=True on a ForeignKey has the same\neffect as using a OneToOneField.

    • \n

  • fields.W343: limit_choices_to has no effect on ManyToManyField\nwith a through model.

    • \n
\n
\n
\n
\n

ModelsLink to this heading#

\n\n
\n
\n

SecurityLink to this heading#

\n

The security checks do not make your site secure. They do not audit code, do\nintrusion detection, or do anything particularly complex. Rather, they help\nperform an automated, low-hanging-fruit checklist, that can help you to improve\nyour site’s security.

\n

Some of these checks may not be appropriate for your particular deployment\nconfiguration. For instance, if you do your HTTP to HTTPS redirection in a load\nbalancer, it’d be irritating to be constantly warned about not having enabled\nSECURE_SSL_REDIRECT. Use SILENCED_SYSTEM_CHECKS to\nsilence unneeded checks.

\n

The following checks are run if you use the check --deploy option:

\n\n
\n
\n

SignalsLink to this heading#

\n\n
\n
\n

TemplatesLink to this heading#

\n

The following checks verify that your TEMPLATES setting is correctly\nconfigured:

\n\n
\n
\n

TranslationLink to this heading#

\n

The following checks are performed on your translation configuration:

\n\n
\n
\n

URLsLink to this heading#

\n

The following checks are performed on your URL configuration:

\n\n
\n
\n
\n

contrib app checksLink to this heading#

\n
\n

adminLink to this heading#

\n

Admin checks are all performed as part of the admin tag.

\n

The following checks are performed on any\nModelAdmin (or subclass) that is registered\nwith the admin site:

\n\n
\n

ModelAdminLink to this heading#

\n

The following checks are performed on any\nModelAdmin that is registered\nwith the admin site:

\n
    \n

  • admin.E101: The value of save_as must be a boolean.

    • \n

  • admin.E102: The value of save_on_top must be a boolean.

    • \n

  • admin.E103: The value of inlines must be a list or tuple.

    • \n

  • admin.E104: <InlineModelAdmin class> must inherit from\nInlineModelAdmin.

    • \n

  • admin.E105: <InlineModelAdmin class> must have a model attribute.

    • \n

  • admin.E106: The value of <InlineModelAdmin class>.model must be a\nModel.

    • \n

  • admin.E107: The value of list_display must be a list or tuple.

    • \n

  • admin.E108: The value of list_display[n] refers to <label>,\nwhich is not a callable, an attribute of <ModelAdmin class>, or an\nattribute or method on <model>.

    • \n

  • admin.E109: The value of list_display[n] must not be a\nManyToManyField field.

    • \n

  • admin.E110: The value of list_display_links must be a list, a tuple,\nor None.

    • \n

  • admin.E111: The value of list_display_links[n] refers to <label>,\nwhich is not defined in list_display.

    • \n

  • admin.E112: The value of list_filter must be a list or tuple.

    • \n

  • admin.E113: The value of list_filter[n] must inherit from\nListFilter.

    • \n

  • admin.E114: The value of list_filter[n] must not inherit from\nFieldListFilter.

    • \n

  • admin.E115: The value of list_filter[n][1] must inherit from\nFieldListFilter.

    • \n

  • admin.E116: The value of list_filter[n] refers to <label>,\nwhich does not refer to a Field.

    • \n

  • admin.E117: The value of list_select_related must be a boolean,\ntuple or list.

    • \n

  • admin.E118: The value of list_per_page must be an integer.

    • \n

  • admin.E119: The value of list_max_show_all must be an integer.

    • \n

  • admin.E120: The value of list_editable must be a list or tuple.

    • \n

  • admin.E121: The value of list_editable[n] refers to <label>,\nwhich is not an attribute of <model>.

    • \n

  • admin.E122: The value of list_editable[n] refers to <label>,\nwhich is not contained in list_display.

    • \n

  • admin.E123: The value of list_editable[n] cannot be in both\nlist_editable and list_display_links.

    • \n

  • admin.E124: The value of list_editable[n] refers to the first field\nin list_display (<label>), which cannot be used unless\nlist_display_links is set.

    • \n

  • admin.E125: The value of list_editable[n] refers to <field name>,\nwhich is not editable through the admin.

    • \n

  • admin.E126: The value of search_fields must be a list or tuple.

    • \n

  • admin.E127: The value of date_hierarchy refers to <field name>,\nwhich does not refer to a Field.

    • \n

  • admin.E128: The value of date_hierarchy must be a DateField or\nDateTimeField.

    • \n

  • admin.E129: <modeladmin> must define a has_<foo>_permission()\nmethod for the <action> action.

    • \n

  • admin.E130: __name__ attributes of actions defined in\n<modeladmin> must be unique.

    • \n
\n
\n
\n

InlineModelAdminLink to this heading#

\n

The following checks are performed on any\nInlineModelAdmin that is registered as an\ninline on a ModelAdmin.

\n
    \n

  • admin.E201: Cannot exclude the field <field name>, because it is the\nforeign key to the parent model <app_label>.<model>.

    • \n

  • admin.E202: <model> has no ForeignKey to <parent model>./\n<model> has more than one ForeignKey to <parent model>.

    • \n

  • admin.E203: The value of extra must be an integer.

    • \n

  • admin.E204: The value of max_num must be an integer.

    • \n

  • admin.E205: The value of min_num must be an integer.

    • \n

  • admin.E206: The value of formset must inherit from\nBaseModelFormSet.

    • \n
\n
\n
\n

GenericInlineModelAdminLink to this heading#

\n

The following checks are performed on any\nGenericInlineModelAdmin that is\nregistered as an inline on a ModelAdmin.

\n
    \n

  • admin.E301: 'ct_field' references <label>, which is not a field\non <model>.

    • \n

  • admin.E302: 'ct_fk_field' references <label>, which is not a\nfield on <model>.

    • \n

  • admin.E303: <model> has no GenericForeignKey.

    • \n

  • admin.E304: <model> has no GenericForeignKey using content type\nfield <field name> and object ID field <field name>.

    • \n
\n
\n
\n

AdminSiteLink to this heading#

\n

The following checks are performed on the default\nAdminSite:

\n\n
\n
\n
\n

authLink to this heading#

\n\n
\n
\n

contenttypesLink to this heading#

\n

The following checks are performed when a model contains a\nGenericForeignKey or\nGenericRelation:

\n\n
\n
\n

postgresLink to this heading#

\n

The following checks are performed on django.contrib.postgres model\nfields:

\n\n
\n
\n

sitesLink to this heading#

\n

The following checks are performed on any model using a\nCurrentSiteManager:

\n\n
\n
\n

staticfilesLink to this heading#

\n

The following checks verify that django.contrib.staticfiles is correctly\nconfigured:

\n\n
\n
","rootId":"system-check-framework","toc":[{"title":"API reference","anchor":"api-reference","children":[{"title":"CheckMessage","anchor":"checkmessage","children":[]}]},{"title":"Builtin tags","anchor":"builtin-tags","children":[]},{"title":"Core system checks","anchor":"core-system-checks","children":[{"title":"Backwards compatibility","anchor":"backwards-compatibility","children":[]},{"title":"Caches","anchor":"caches","children":[]},{"title":"Database","anchor":"database","children":[{"title":"MySQL","anchor":"mysql","children":[]}]},{"title":"Model fields","anchor":"model-fields","children":[{"title":"File fields","anchor":"file-fields","children":[]},{"title":"Related fields","anchor":"related-fields","children":[]}]},{"title":"Models","anchor":"models","children":[]},{"title":"Security","anchor":"security","children":[]},{"title":"Signals","anchor":"signals","children":[]},{"title":"Templates","anchor":"templates","children":[]},{"title":"Translation","anchor":"translation","children":[]},{"title":"URLs","anchor":"urls","children":[]}]},{"title":"contrib app checks","anchor":"contrib-app-checks","children":[{"title":"admin","anchor":"admin","children":[{"title":"ModelAdmin","anchor":"modeladmin","children":[]},{"title":"InlineModelAdmin","anchor":"inlinemodeladmin","children":[]},{"title":"GenericInlineModelAdmin","anchor":"genericinlinemodeladmin","children":[]},{"title":"AdminSite","anchor":"adminsite","children":[]}]},{"title":"auth","anchor":"auth","children":[]},{"title":"contenttypes","anchor":"contenttypes","children":[]},{"title":"postgres","anchor":"postgres","children":[]},{"title":"sites","anchor":"sites","children":[]},{"title":"staticfiles","anchor":"staticfiles","children":[]}]}],"breadcrumbs":[{"docname":"ref/index","title":"API Reference","url":"/pl/3.0/ref/"}],"prev":{"docname":"ref/applications","title":"Applications","url":"/pl/3.0/ref/applications/"},"next":{"docname":"ref/class-based-views/index","title":"Built-in class-based views API","url":"/pl/3.0/ref/class-based-views/"},"formats":{"html":"/pl/3.0/ref/checks/","markdown":"/pl/3.0/ref/checks.md","json":"/pl/3.0/ref/checks.json"},"source":"https://github.com/django/django/blob/stable/3.0.x/docs/ref/checks.txt","official":"https://docs.djangoproject.com/pl/3.0/ref/checks/","inVersions":["6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11","1.10"],"inLocales":["en","zh-hans","fr","ja","id","pt-br","ko","es","el","pl"]}