微信内可能无法直接打开本站。请点右上角 ··· → 在浏览器打开，或复制链接。
Metadrop: Managing untracked files in Drupal with File Inspector
RSS 官方收录 · 可信分层展示
关键摘要
Content management systems include different types of files as part of the managed content.…
- However, for several reasons, those files are not always tracked by th…
- This article explores this problem and proposes File Inspector as a so…
- The files that Drupal does not track Any long-lived Drupal site, wheth…
规则摘要 · 来源可核验
正文提要
The files that Drupal does not track
Any long-lived Drupal site, whether it stores files in a local folder or a remote bucket like Amazon S3, holds hundreds of files, and there is no easy way to see which ones Drupal still tracks and which it has lost sight of. The files come from four places: live content, leftovers from nodes deleted years ago, migration and backup residue, and direct uploads, such as a PDF dropped onto the server because it was faster.
This is a common problem in the sector, and it does not depend on the technology in use. Every content system faces it sooner or later. The root cause is two stores that must agree: the bytes in storage versus the database that is supposed to keep track of them. The moment both stores exist, they drift. It happens in three ways: records get deleted but the files stay, files get uploaded but never registered, and jobs fail halfway.
These accumulated unreferenced files are untracked files, a kind of dark data: information an organisation keeps but no longer uses.