Improved UI layout and UX for the file clean-up configuration

Created on 29 July 2013, almost 12 years ago
Updated 21 May 2025, 13 days ago

D.o procid experiment

This issue would be a good case study to evaluate procid #2154143: Evaluating Procid, a tool to help the drupal community improve the consensus building process for d.o issues β†’
You do not have to use procid to work on this issue, but if you want to, your feedback would be very helpful.

----
Follow up for: #1399846: Make unused file 'cleanup' configurable β†’

Problem/Motivation

The automatic file clean-up functionality in Drupal core is a destructive feature that automatically, and without warning, permanently removes file content that meets a specific criteria. That criteria is when the file usage for individual files reaches zero (0).

Since since is a rather unique, maybe even the only, behaviour of Drupal core it is important that users fully understand this concept so they can make an informed decision about its configuration.

The current implementation UI is not making this stand out and this there is chance/risk users will miss it. At least until they start to wonder why files are disappearing from their site.

Proposed resolution

Mockup proposal for new UI that also will improve the UX for users:

This will both separate the file clean-up configuration and make it stand out much better against the other configurations on this page.

The proposed options for the drop-down are:

  • Disabled
  • After 3 hours
  • After 12 hours
  • After 1 day
  • After 1 week
  • After 4 weeks
  • After 3 months

Remaining tasks

  • Finalize the texts
  • Finalize the names of the drop-down options
  • Create the d.o page for more detailed information
  • Write the patch

User interface changes

See mockup above

API changes

None

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

file system

Created by

πŸ‡ΈπŸ‡ͺSweden tsvenson

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Needs backport to D7

    After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024