Librizent - Media Library Health
| 开发者 | mujahidwp |
|---|---|
| 更新时间 | 2026年9月18日 01:07 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Media Health Score calculated from actual scan results.
- Missing ALT text detection for images with completely empty ALT values.
- Oversized image detection with a configurable pixel threshold.
- Heavy image file-size detection with a configurable per-image MB threshold.
- Missing or incomplete image dimension metadata detection.
- Missing or unreadable local attachment file detection, with an offloaded-media caution.
- Potentially poor filename detection using conservative filename patterns.
- Possible duplicate detection using SHA-256 hashes where practical and metadata signatures as a fallback.
- Possibly Unused Media review using WordPress-native attachment, featured-image, and content-reference checks.
- Manual ALT text editing with capability and nonce checks.
- Batched manual scanning designed to avoid loading the full Media Library into memory.
- Batch-built usage index so post-content and featured-image checks are not repeated once per attachment.
- Dedicated Media Usage workspace with Usage Found, Possibly Unused, and live attachment review states.
- Scan History with up to 10 compact local summaries, score trends, issue totals, and scan duration.
- Five focused admin destinations: Dashboard, Media Health, Media Usage, Scan History, and Settings.
- No external services, registration, API keys, telemetry, tracking, or AI features.
安装:
- Upload the
librizent-media-library-healthfolder to/wp-content/plugins/, or install the plugin ZIP through Plugins > Add New > Upload Plugin. - Activate Librizent through the Plugins screen.
- Open Librizent > Dashboard.
- Select Run Media Health Scan.
- Review findings under Librizent > Media Health.
- Use Librizent > Media Usage to inspect usage signals, and Librizent > Scan History to compare completed scans.
屏幕截图:
常见问题:
Does Librizent optimize or compress images?
No. Librizent is an audit and health tool, not an image optimizer.
Does Librizent delete unused media?
No. It never automatically deletes media. The "Possibly Unused" result is a review signal, not proof that a file is unused.
Does Librizent automatically generate or change ALT text?
No. Librizent has no AI functionality and never writes ALT text automatically. Users can manually save ALT text for a flagged image.
Does Librizent send data to another server?
No. Librizent does not require an external service, API key, registration, telemetry, or tracking.
What does the heavy image file-size check do?
It flags readable local image files above the MB threshold you choose in Settings. It does not compress, resize, replace, or otherwise modify the file.
What does the missing or unreadable files check mean?
It means the attachment record did not resolve to a readable local source file during the scan. This can indicate a broken migration or moved file, but sites that intentionally offload media should verify their storage integration before treating a result as broken.
How are possible duplicates detected?
Readable local files up to a conservative size limit are compared with SHA-256 hashes. Larger files use a metadata-based signature and remain explicitly labeled as possible duplicates.
Why can a file be marked Possibly Unused even if I use it?
Media can be referenced outside standard post content and featured images. Page builders, custom fields, theme options, CSS, JavaScript, ecommerce data, and external integrations may store references in ways this lightweight scan does not inspect.
Does the scan run on every admin page load?
No. Scans are manual and processed in small AJAX batches. Before attachment analysis, Librizent builds a lightweight usage index from common WordPress content references and featured images in batches, then reuses that index during the media scan. Stored scan results are used for review pages until the next scan.
What does the Media Usage page check?
It uses the latest manual scan to classify attachments when WordPress-native usage signals were found or when an item was marked Possibly Unused. Opening Review Usage performs a focused live lookup for attachment relationships, featured-image use, and common post-content references. These checks are intentionally conservative and cannot prove that media is unused everywhere.
What is stored in Scan History?
Librizent keeps up to 10 compact local summaries containing timestamps, scan duration, Health Score, and aggregate counts. It does not duplicate full issue lists in history, and clearing history does not delete media or the latest detailed scan.
更新日志:
- Completed a WordPress.org guideline hardening pass against the current Plugin Directory guidance.
- Added a direct-access guard to the root index file.
- Added the Librizent audit capability check to manual ALT updates in addition to attachment edit permission and nonce verification.
- Added canonical UUID validation for AJAX scan identifiers before state comparison.
- Standardized local file-size reads on WordPress core
wp_filesize()for the declared WordPress requirement. - Removed tier-related ambiguity from public copy and added an explicit local-only privacy disclosure.
- Re-checked remote calls, bundled libraries, update mechanisms, executable downloads, input handling, output escaping, SQL preparation, internationalization, and uninstall cleanup.
- Prepared the package for a clean Librizent WordPress.org submission.
- Verified that the plugin folder, main plugin filename, and text domain all use
librizent-media-library-health. - Removed the unused local translation Domain Path header so WordPress.org language packs can use the canonical plugin slug.
- Hardened the default audit capability to administrators while keeping the capability filter available to developers.
- Re-checked nonces, capability checks, sanitization, escaping, prepared database reads, direct-access guards, and uninstall cleanup.
- Renamed the plugin to Librizent - Media Library Health.
- Updated plugin branding, internal identifiers, admin UI references, file names, and asset handles to Librizent.
- Updated the WordPress.org text domain to
librizent-media-library-health. - Bumped the plugin version to 1.0.1.
- Initial release.
- Added batched Media Library health scanning.
- Added missing ALT, oversized image, heavy image file-size, dimension, filename, duplicate, possibly-unused, and missing/unreadable file detectors.
- Added transparent Media Health Score.
- Added manual ALT editing, settings, usage review, and safe uninstall cleanup.
- Added the polished purple/orange Librizent admin interface.
- Added a dedicated Media Usage workspace with stored usage classification, filters, pagination, and focused live review.
- Added compact Scan History with up to 10 local summaries, score trends, issue totals, scan duration, and protected history clearing.
- Expanded the professional Librizent menu to five destinations: Dashboard, Media Health, Media Usage, Scan History, and Settings.
- Improved large-library scan performance by building WordPress-native usage signals in batches instead of running content and featured-image lookups separately for every attachment.