Wrenio Media Offload
| 开发者 |
wrenio
freemius |
|---|---|
| 更新时间 | 2026年6月2日 19:17 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Uploads new media to R2 as attachments are added (via scheduled background sync).
- Uploads existing media in batches via the Bulk Sync page.
- Rewrites attachment,
srcset, and in-content image URLs to the R2 (or CDN) origin. - Optionally deletes the local file after a successful upload to save disk inodes.
- Fills in thumbnail metadata for attachments whose local file has been deleted.
- Reconciles R2 object keys with local paths if they have drifted.
- Repairs filename-level mismatches between WordPress and R2.
- Identifies orphan R2 objects that are no longer referenced by any attachment.
wp-config.php:
define( 'WRENIO_R2_ACCOUNT_ID', 'your-account-id' );
define( 'WRENIO_R2_ACCESS_KEY_ID', 'your-access-key' );
define( 'WRENIO_R2_SECRET_ACCESS_KEY', 'your-secret-key' );
define( 'WRENIO_R2_BUCKET_NAME', 'your-bucket-name' );
define( 'WRENIO_R2_PUBLIC_URL', 'https://media.example.com' );
Constants take priority over values stored in the database.
The reconciliation tool
R2 object keys are derived from the stable _wp_attached_file meta. If keys drift away from an attachment's physical file path — for example, due to external tooling or imported content — the Reconcile page detects the drift and previews the realignment plan.
Run Wrenio Media Offload → R2 Reconcile → "Start Dry Run" to scan and preview a fix plan. (Live realignment that moves R2 objects to their correct keys is available in the Pro version — see below.)
Cleanup tools
- Filename Cleanup detects attachments where the filename portion of
_wp_attached_filediffers from the R2 key (typically caused by double-dot or similar normalization mismatches) and repairs the WordPress meta to align with R2. - Orphan Cleanup walks the bucket via ListObjectsV2, builds the set of keys referenced in post meta, and offers a reviewable list of R2 objects that aren't referenced anywhere. Deletion is opt-in per batch.
安装:
- In WP admin → Plugins → Add New, search for Wrenio Media Offload.
- Click Install Now, then Activate.
- Go to Wrenio Studio → Wrenio Media Offload, open the Settings tab, and enter your Cloudflare R2 credentials. (Recommended: define them in
wp-config.phpinstead — see the "Credentials" block in the Description above.) - Click Test Connection to verify the bucket is reachable, then Test Write Access to verify your API token can PUT and DELETE.
- Enable URL Rewrite once both tests pass.
- Open the Bulk Sync page and run a bulk sync to migrate your existing media.
- Only after bulk sync reaches 100% and spot checks pass, consider enabling Delete Local Files under the Features tab.
屏幕截图:
常见问题:
What happens to the local file when upload succeeds?
By default, nothing. The local file stays on the server as a backup. Enable Delete Local Files under Features to delete after a successful upload — but only once you've fully verified your R2 copy.
What file types are allowed?
Images (jpeg, png, gif, webp, svg, bmp, tiff, avif), video (mp4, mov, avi, mpeg, webm, ogv), audio (mp3, ogg, wav, m4a, flac, aac), and PDF. Files up to 50 MB are supported.
Does it work with multi-site?
Yes, on a per-site basis. Each site stores its own settings and syncs to its own bucket.
What if reconciliation fails partway through?
The tool processes attachments atomically: for each item, it copies, verifies, updates meta, then deletes the old objects. If any step fails, the attachment is left in a recoverable state — re-running reconciliation picks up where it left off. A retry cap (3 attempts per attachment) prevents a single bad item from blocking the rest; capped items appear in the Status table and are skipped on subsequent runs. (Resetting the retry counter to re-attempt a capped item is a Pro feature.)
Is this safe to run on a production site?
The reconciliation and orphan-cleanup tools are destructive (Reconcile deletes old R2 objects after copying; Orphan Cleanup deletes objects it determines are unreferenced). Always:
- Take a database backup.
- Take (or accept loss of) an R2 bucket backup.
- Run in Dry Run mode first (Reconcile) or Scan + Preview first (Orphan Cleanup).
- Review the log output and/or spot-check preview URLs.
- Only then run the live operation.
Will ERROR logs always be written?
Yes. ERROR and WARNING entries are always logged regardless of the Debug Logging setting. INFO and DEBUG require Debug Logging to be enabled.
更新日志:
- Initial release.