Improvement on InlineFormSet doc, refs #21006
When both parent and child classes are decorated with override_settings, child class settings should take precedence. Thanks Sephi for the report and Marc Tamlyn for the review.
`HttpRequest.scheme` is `https` if `settings.SECURE_PROXY_SSL_HEADER` is appropriately set and falls back to `HttpRequest._get_scheme()` (a hook for subclasses to implement) otherwise. `WSGIRequest._get_scheme()` makes use of the `wsgi.url_scheme` WSGI environ variable to determine the request scheme. `HttpRequest.is_secure()` simply checks if `HttpRequest.scheme` is `https`. This provides a way to check the current scheme in templates, for example. It also allows us to deal with other schemes. Thanks nslater for the suggestion.
…eFormSet. Thanks treysta at gmail.com for the suggestion.
Fixed #19617 -- Refactored form metaclasses to support more inheritance scenarios.
Previously admindocs would throw an error when processing it: "Error in "default-role" directive: no content permitted." refs #6681
Thanks ebertti at yahoo.com.br for the suggestion.
Thanks firstname.lastname@example.org for the report.
Avoids failures on Windows. Refs #8918.
This config allows a clean run of flake8. Some of the ignored codes will be remove over time as we clean things up.
… a filename. Thanks Marc Tamlyn for the suggestion.
…tions. Thanks Keryn Knight for the report.
… by shadowing them.
…ce scenarios. Thanks apollo13, funkybob and mjtamlyn for the reviews.
…elds. The ModelForm docs suggested that fields defined declaratively override default fields generated from the form Meta. This is conceptually wrong, especially with inheritance in mind. Meta is usually defined on the topmost ModelForm subclass, while fields can come from anywhere in the MRO, especially base classes; therefore we suggested that something defined in a base class override something from a subclass. This patch rephrases the docs around the idea that Meta is used to generate *missing* fields. Refs #8620, #19617. Thanks @mjtamlyn and @timgraham for the review.
Thanks gergely at polonkai.eu for the suggestion.
Fixed #18866 -- added validation error for verbose_name longer than 39 characters
…9 characters Added a validation error check when creating the permissions for model, to avoid cryptic database error when the verbose_name is longer than 39 characters thanks elena for reporting it
Thanks Aymeric Augustin for the report and the documentation and Tim Graham for the review.
Without those imports, affected test files cannot be run independently. Refs #21164.
Thanks jpic for the report and chmodas for working on a patch. Reverts 2ea80b9. Refs #19362.
Thanks gcc for the report and vajrasky for the patch.
…time Thanks Marc Tamlyn for the review.