Birim Private Files – Protect Uploads & Private Pages
Protect media files, PDFs and uploads in WordPress so they open only for the people allowed to see them, even by direct link. WordPress stores uploads in /wp-content/uploads/ , and every file there is a public URL. Making a page private, or putting your site behind a login, does not protect the file
Protect media files, PDFs and uploads in WordPress so they open only for the people allowed to see them, even by direct link.
WordPress stores uploads in /wp-content/uploads/ , and every file there is a public URL. Making a page private, or putting your site behind a login, does not protect the files on it: anyone with the link can open them.
Birim Private Files routes every request for an uploaded file through WordPress and only serves it to people who are allowed to see it.
- Three ways to decide who opens files : any logged-in user, only the roles you choose, or only the people each file is shared with (the uploader, people you add in the file’s “Shared with” field, editors and administrators).
- Private pages too : a “Who can view” box in the page editor (block editor and classic editor) sets each page or post to Everyone, Logged-in users or chosen roles. Restricted pages send logged-out visitors to the login page, and their text is hidden in search results, archives, feeds and the REST API, and left out of the sitemap.
- Files follow their page : in per-file mode, files uploaded to a restricted page open for whoever can view that page.
- A “My files” list : put [birim_my_files] on a page and each person sees the files they uploaded or that were shared with them.
- Direct links are protected , not just pages. Logged-out visitors who open a file link are sent to the login page and come back to the file after logging in.
- It checks that protection really works. After you turn it on, the plugin requests a test file from your site as a logged-out visitor and tells you the result: Protected, Not protected, or Could not check. Until protection is confirmed, administrators see a warning. Many file protection setups fail silently on nginx servers; this one tells you.
- Apache : rules are added to wp-content/uploads/.htaccess automatically, and removed when you deactivate the plugin.
- nginx : the settings page shows the exact two-line rule to add for your site.
- Public exceptions : keep chosen files public, such as a logo, with simple patterns like public/* .