Changes between Initial Version and Version 5 of Ticket #35674


Ignore:
Timestamp:
Sep 2, 2024, 3:47:21 PM (3 months ago)
Author:
Natalia Bidart
Comment:

Edited the description to match what was agreed on the referenced forum topic.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #35674

    • Property Component Error reporting → Core (System checks)
    • Property Easy pickings unset
    • Property Triage Stage Unreviewed → Accepted
    • Property Summary Provide a check for `DEFAULT_FILE_STORAGE` → Provide a check for settings removed (post deprecation)

  • Ticket #35674 – Description

    initial v5  
     1This ticket was repurposed following the original report and a related [https://forum.djangoproject.com/t/deprecation-of-default-file-storage-can-we-easen-the-migration/34284/ forum conversation] to provide a check for "outdated settings", meaning those settings that went thru the usual and expected deprecation process and have been removed from the code base. These settings are effectively pointless to have defined, as they no longer have any effect, and even in some cases, having them defined might lead project maintainers to mistakenly believe they are still in effect.
     2
     3Original report:
     4
    15Hello friends, I had a `DEFAULT_FILE_STORAGE = "storages.backends.s3.S3Storage"` in my Django 5.0.8 project. When I upgraded it the project worked but the user-uploaded content was uploaded to the filesystem instead of S3. This happened because my `DEFAULT_FILE_STORAGE` setting was ignored so it fall back to the STORAGES default (https://docs.djangoproject.com/en/5.0/ref/settings/#storages):
    26
Back to Top