AAM Protected Media Files

描述

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.

Few Facts

  • It requires a simple manual steps in order to configure a webserver to protect direct access to /wp-content/uploads folder. 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. .svg, .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.

螢幕截圖

  • Restrict access to media file with AAM UI
  • Restrict access to media file while editing it

安裝

  1. Upload aam-protected-media-files folder to the /wp-content/plugins/ directory.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.
  3. Configure your webserver to redirect all media request to access handler as described in installation guide.

評價

閱讀全部2個評價

貢獻者及開發者

“AAM Protected Media Files” 是一個開源的軟體。以下的人對這個外掛作出了貢獻。

貢獻者

將 AAM Protected Media Files 外掛本地化為台灣繁體中文版。

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄

修改日誌

1.2.2

1.2.1

  • Changed: Renamed the 401 redirect option to “Use Access Denied Redirect For Restricted Media Items”

1.2.0

1.1.7

1.1.6

1.1.5

1.1.4

  • Fixed Bug: Incorrectly computed file path on NGINX servers

1.1.3

  • Fixed Bug: Incorrectly computed physical path to a file when website is located in subfolder

1.1.2

1.1.1

  • 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

1.1.0

  • Fixed Bug: AAM URI Access access options were not honored for stand-alone files in the uploads folder
  • Added New: Introduced new AAM settings that enables Access Denied Redirect service when access is denied to protected files

1.0.0

  • Initial version