| 开发者 | hsojhsoj |
|---|---|
| 更新时间 | 2026年9月28日 02:55 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Yes. This plugin adds a module to the Beaver Builder page editor. Without Beaver Builder installed and active, the module has nothing to attach to. The free Beaver Builder Lite version is sufficient.
Whatever the visitor's browser supports through the native HTML5 <audio> element. In practice that's MP3, AAC, OGG, and WAV across modern browsers. The plugin doesn't transcode — you serve whatever file you upload.
Wherever you put them. The module just stores URLs. Most people upload audio files to their WordPress Media Library and use those URLs, but any publicly reachable URL works.
It tries. The plugin will call audio.play() on page load if autoplay is enabled, but most browsers block autoplay with sound unless the user has interacted with the page first. If the browser blocks it, the player just sits ready and waits for the user to click play — no error is shown.
Yes. Each module instance is fully independent — its own tracks, its own playback state, its own styling. They don't interfere with each other.
No. There are no analytics calls, no third-party scripts, no telemetry. The browser plays the file directly from wherever the URL points.
The module enqueues a small per-instance CSS + JS pair only on pages that contain the module. The total weight per instance is on the order of a few kilobytes; the audio file itself is fetched only when the user starts playback (preload is set to metadata so only the duration is fetched up front).
Open an issue at the GitHub repository: https://github.com/Dependent-Media/dm-audio-playlist
button:hover / :focus / :active — the Beaver Builder theme skin sets a blue background, a border, and position: relative on those states — and button:focus (specificity 0,1,1) outranked the plugin's lone .dmap-lightbox-close class (0,1,0). Because the script focuses the close button when the lightbox opens, it immediately picked up position: relative and moved into the centered flex column above the artwork, only snapping back to the corner once it lost focus on the way out. All lightbox rules are now scoped one level deeper (.dmap-lightbox .dmap-lightbox-close), and the close button restates its position, border, and colors for the hover, focus, and active states.cover-300x300.jpg), which is right for the 80px thumbnail but far too small to enlarge. The size suffix is stripped to recover the original, but only for URLs inside this site's uploads directory and only when that file actually exists on disk — otherwise the stored URL is used unchanged. -scaled images are left alone.button when the lightbox is enabled: keyboard focusable, activates with Enter/Space, closes with Escape, the backdrop, or the close button, and returns focus to the artwork afterwards. It is automatically disabled on tracks that have no artwork.body so builder rows with overflow: hidden, a transform, or their own stacking context cannot clip it.dependent-media-audio-playlist-for-beaver-builder.dm_audio_playlist_sanitize_color) that accepts only valid #hex, hex, rgb(), and rgba() patterns; everything else falls back to the per-field default.<style> block that was being emitted from frontend.php in addition to the framework-rendered frontend.css.php. Styles are now rendered through a single source.<script> previously echoed into wp_footer is now an enqueued JavaScript file (js/editor.js) loaded only when the BB editor is active and the user has edit_posts.License, License URI, Requires at least, and Requires PHP plugin headers required by the WordPress.org Plugin Directory.BBMp3PlayerModule PHP class is registered as an alias of DM_Audio_Playlist_Module, and both the module and its track settings form are registered under their old and new names. Existing Beaver Builder layouts that reference the old class continue to render after upgrade with all settings preserved (track URLs, titles, artwork, colors, volume, autoplay).Requires Plugins: beaver-builder-lite-version header. Beaver Builder Pro has a different slug than Beaver Builder Lite, so that header would block users on Pro from activating the plugin even though Pro fully satisfies the actual dependency. The plugin still checks for FLBuilder at runtime and shows an admin notice if neither Lite nor Pro is active.