modSizeControl

modSizeControl walks every file of the site once, so "where did the space go" is answered inside the manager. A dashboard widget shows the limit as a ring and the categories as slices; the component page has folders largest first, extras, file types, largest files and history. Scanning runs in steps, so a large site never hits max_execution_time. Cleanup frees cache, logs and old packages.

Install the package with the Package Manager. Nothing to configure: the dashboard widget appears on first install, and the component page is at Extras -> modSizeControl (the settings permission).

Press "Refresh" in the widget or "Scan" on the component page to run the first scan. Optional: modsizecontrol_site_limit sets the limit in megabytes, modsizecontrol_control refuses uploads that do not fit, and core/components/modsizecontrol/cli/scan.php runs the same scan from cron.

• Upload control no longer breaks uploads: with a limit set, every file that fit the limit failed with a PHP fatal error, and the manager's uploader showed "unknown".
• Only files the file manager actually wrote count as uploaded. A file MODX turns down by its extension, upload_maxsize or an existing name no longer makes the site look bigger until the next scan.
• Deleted files free room for uploads again: when an upload would not fit after files were changed or deleted, the site is measured again before the file is refused.