| 开发者 | forgestudio |
|---|---|
| 更新时间 | 2026年10月29日 03:10 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
uploads/forgedbi-media-organizer/, wherever WordPress says uploads are), under a randomly named subfolder. Many web servers serve everything in uploads, so every file held there is encrypted (libsodium, or OpenSSL where libsodium is missing), and so is the record of where each belongs. The encryption key is kept in your database, never in that folder, so the files cannot be read even if someone finds and downloads them. The folder also carries deny rules and an empty index for servers that honour them. If the server cannot encrypt, or the folder cannot be written, new quarantines are switched off and anything already held stays restorable.
Privacy
The plugin makes no request to any outside service. The only request it sends is from your site to itself, to check whether the web server would serve the quarantine folder (whose contents are encrypted either way). Nothing about your media leaves your server.
Source code and build
The admin interface in build/ is compiled from the TypeScript and React source shipped with the plugin in admin/src/. To rebuild it: install Node.js 24, run npm ci, then npm run build. PHP dependencies are declared in composer.json; the only runtime dependency is Action Scheduler (GPL-3.0), bundled in vendor/.
forgedbi-media-organizer folder to wp-content/plugins.No. Folders are labels in the database. No file is moved, renamed or copied by organizing.
No, and the plugin says so wherever it shows that result. A scan reads the sources listed under Scan & Usage → Coverage. Theme templates, plugin settings, emails, other websites and anything else it does not read may still use a file. That is why cleanup is a quarantine you can undo, not a deletion.
Its files are moved out of the uploads folder and its addresses stop working — a page that used it shows a broken image until it is restored. Its record, metadata, folder and every reference stay as they were. Restoring puts the files back byte for byte, verified by checksum. A file is only ever permanently deleted when an Administrator asks for that, after the recovery window, by typing its name.
No. Nothing in this plugin deletes a file on its own. The window ending only makes permanent deletion possible for an Administrator to request.
They are kept under uploads, which most web servers will serve to anyone who knows the address. Encrypted, they are useless to anyone without the key. The key is in your database (so in every database backup), or in wp-config.php if you define FORGE_MEDIA_QUARANTINE_KEY. Keep your backups: without the key, held files cannot be restored.
Folders, scans, smart views and protection work. Quarantine, restore and permanent deletion are switched off while a known offloading plugin is active, because they move local files and the remote copy would keep being served.
The block and classic editors, featured images, galleries, site identity and core widgets, Elementor layouts and saved templates, and ACF image and gallery fields (including inside groups and repeaters). Others are not read, and the scan's coverage screen lists what was and was not checked for each scan.
ForgeDBI Media Organizer is the same plugin under its new name. Deactivate the old copy first (activation is refused while it is active, and the old copy is left running); then activate this one, and your folders, settings, activity and quarantined files carry over as they are. Files quarantined by the earlier build stay where that build put them and can still be restored or permanently deleted from there; nothing new is written to the old folder. Then delete the old copy from the Plugins screen. Its uninstall routine removes nothing.
No. Deactivating or deleting the plugin leaves your folders, the activity log, quarantined files and their manifests in place, so nothing is lost by removing it. The runbook in the plugin's documentation explains how to put held files back by hand.
forgedbi-media-organizer). Data from the earlier build carries over unchanged.wp_upload_dir(), and are always stored encrypted, their manifests included. The key is never written to that folder.