| 开发者 | adamgreenwell |
|---|---|
| 更新时间 | 2026年4月30日 00:56 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/listenup directory, or install the plugin through the WordPress plugins screen directly.Yes, but you'll need separate API keys for each site or ensure your Murf.ai plan supports multiple domains.
The plugin supports MP3, WAV, FLAC, ALAW, ULAW, PCM, and OGG output from Murf.ai. MP3 is the default because it works well across browsers and supports chunked audio downloads without requiring FFmpeg.
Yes, the plugin includes CSS classes that you can customize in your theme's stylesheet.
For posts that exceed Murf.ai's API character limits, the plugin automatically breaks the content into smaller chunks. Each chunk is processed separately and saved as an individual audio file. The frontend player seamlessly plays all chunks in sequence, and supported formats can be downloaded as a concatenated file.
ListenUp serves all audio files through a secure PHP proxy instead of allowing direct file access. Each audio URL includes a WordPress nonce for authentication, preventing unauthorized access and hotlinking. The system supports HTTP range requests for smooth audio seeking and includes proper caching headers for performance. This protection works automatically without requiring any server configuration.
Yes! For additional security, you can configure your web server to block direct access to the audio directory. Here are example configurations:
For Apache (.htaccess):
Add this to /wp-content/uploads/listenup-audio/.htaccess:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [F,L]
</IfModule>
For Nginx:
Add this to your server block configuration:
location ~* ^/wp-content/uploads/listenup-audio/ {
return 403;
}
After implementing server-level blocks, audio will still play normally through the WordPress player because the plugin reads files directly from the filesystem, bypassing the web server's URL routing entirely.