You can now inspect a single file by name. The Protection status tab has a field where you paste a file URL and get back whether a logged-out visitor can reach it — and which setting decided that.
Now that the protection scope can be expressed three ways — by extension, by folder, or by the post a file is attached to — it had become hard to tell from the settings screen alone why a particular file was public. This answers that directly.
- Accepts a file URL, an attachment ID, or a path relative to the uploads directory. A URL copied straight from the browser works, query string and all, even if the scheme differs.
- The verdict names the rule responsible — for example “Served to everyone: it is inside the excluded path public“.
- The parent post and its status are shown too, so decisions made in the “follow the post” scope are just as traceable.
- The same check is available from the command line as
wp medifence inspect <file>.
📦 Download Medifence 1.9.0 (zip)
