Prevent direct access to the unlimited number of media library items either for visitors, individual users or groups of users (roles). This plugin does not modify a physical file’s location or URL.
The AAM Protected Media Files plugins is the official add-on to the free Advanced Access Manager (aka AAM). While this plugin actually manages physical access to the media files, AAM provides the UI interface to define access to files.
- It requires a simple manual steps in order to configure a webserver to protect direct access to
/wp-content/uploadsfolder. For more information, please check our installation instructions;
- It does not change a physical file’s location, content or URL. Upon deactivation, everything goes back to normal;
- It protects all the allowed by WordPress core file types and those that are extended with third-party plugins (e.g.
.sketch, etc.). For the list of all allowed extensions, check official WP documentation for the wp_get_ext_types() core function;
- It allows you to manage access to any media file for visitors, any individual user, roles or even define the default access to all media files for everybody (this one is available with premium add-on for AAM plugin);
For more information about how properly install and use it, refer to our documentation.
aam-protected-media-filesfolder to the
- Activate the plugin through the ‘Plugins’ menu in WordPress.
- Configure your webserver to redirect all media request to access handler as described in installation guide.
Contributors & Developers
“AAM Protected Media Files” is open source software. The following people have contributed to this plugin.حصہ پاوݨ آلے
ڈیویلپمنٹ وچ دلچسپی ہے؟
- Fixed: Deprecated PHP warning https://github.com/aamplugin/aam-protected-media-files/issues/12
- Fixed: Handle files with encoded characters https://github.com/aamplugin/aam-protected-media-files/issues/13
- Fixed: NGINX hard redirect issue https://github.com/aamplugin/aam-protected-media-files/issues/15
- Added New: Allow the ability to override the ABSPATH https://github.com/aamplugin/aam-protected-media-files/issues/14
- Changed: Renamed the 401 redirect option to “Use Access Denied Redirect For Restricted Media Items”
- Fixed Bug: Fails to serve files with special characters https://github.com/aamplugin/aam-protected-media-files/issues/7
- Added New: The ability to verify that file was served by the plugin https://github.com/aamplugin/aam-protected-media-files/issues/9
- Fixed Bug: SVGs are blocked by default https://github.com/aamplugin/aam-protected-media-files/issues/6
- Fixed Bug: Incorrectly path comparisson on Windows servers https://github.com/aamplugin/aam-protected-media-files/issues/3
- Added New: Allow to hook into media search for other AAM add-ons https://github.com/aamplugin/aam-protected-media-files/issues/4
- Fixed Bug: URI Access service does not work on NGINX servers https://github.com/aamplugin/advanced-access-manager/issues/33
- Fixed Bug: Incorrectly computed file path on NGINX servers
- Fixed Bug: Incorrectly computed physical path to a file when website is located in subfolder
- Fixed Bug: Incorrectly returned image size https://forum.aamplugin.com/d/448-wrong-image-sizes-are-returned-with-aam-protected-media-files-plugin-enabled
- Fixed Bug: User was not redirecting properly when access was denied. Incorrectly handled HTTP redirecting
- Fixed Bug: Incorrectly managed file search when media file’s name follows reserved naming convention
- Fixed Bug: AAM URI Access access options were not honored for stand-alone files in the
- Added New: Introduced new AAM settings that enables Access Denied Redirect service when access is denied to protected files
- Initial version