內容簡介
Neutrope Protected Audio Player 讓您在 WordPress 網站上發佈 MP3 音訊，而不會在頁面源碼中暴露真實檔案 URL。音訊檔案儲存在受保護的上傳資料夾中，並透過短期簽名的播放 URL 並串流播放，增加了下載的難度。
【主要功能】
• 提供「受保護音訊」項目類型，方便上傳 MP3
• 將上傳檔案儲存在受保護的資料夾中
• 透過短期簽名 URL 提供音訊串流
• 隱藏瀏覽器的下載按鈕
• 記錄每個項目的匿名播放次數
外掛標籤
開發者團隊
② 後台搜尋「Neutrope Protected Audio Player」→ 直接安裝（推薦）
原文外掛簡介
Neutrope Protected Audio Player lets you publish MP3 audio on your WordPress site without exposing the real file URL in your page source. Files are stored in a protected uploads folder that denies direct access, and the player streams audio through a short-lived, signed playback URL instead of a permanent, guessable link.
This is not DRM. It makes casual downloading harder, but it cannot provide DRM or perfect copy protection. If audio can be played in a browser, it can potentially be captured by determined users. The goal is simply to stop ordinary visitors from finding and saving the MP3 with a right-click or a quick look at the page source.
What it does
Adds a “Protected Audio” item type where you upload an MP3 and get a shortcode.
Stores uploads in wp-content/uploads/neutrope-protected-audio-player/, protected by an .htaccess file.
Serves audio through a signed URL such as /npap-stream/123/.../.../ that expires after 10 minutes.
Outputs an
What this plugin can and cannot do
This is not DRM.
This plugin makes casual downloading harder, but cannot provide DRM or perfect copy protection.
If users can play audio in a browser, advanced users may still capture it.
No external services.
No tracking.
No cookies.
No personal data stored by default.
Apache/LiteSpeed uses .htaccess protection.
Nginx may require additional server configuration.
Privacy
No external services, CDNs, scripts or APIs are used. Everything runs on your own server.
No tracking.
No cookies are set.
No personal data is stored by default. The plugin records only an aggregate play count per item. It never stores IP addresses and never sets cookies.
Server requirements
On Apache and LiteSpeed, direct access to the protected folder is blocked automatically with the .htaccess file the plugin creates.
On Nginx, .htaccess files are ignored. You will need to add server configuration to deny direct access to the protected uploads folder. The admin screen shows a reminder when it detects Nginx.
On some Nginx or reverse proxy configurations, byte-range responses may be buffered or altered by the server. Audio playback can still work, but seeking behavior may depend on server configuration.
Pretty permalinks are recommended. When they are disabled, the plugin falls back to a query-string playback URL.
