The WordPress XSPF Player Plugin
放上代码<?php xspf_player::start(‘category-tag’); ?>
下面在工具里面的XSPF Player 里面添加音乐吧
首页刷新 看看自己的播放器吧 O(∩_∩)O~
I wanted my WordPress site to have some MP3 background music, but didn’t found any suitable plugin for it:
My webhosting server has little space, and cannot store tracks online. I just wanted a flash player or alike to be embedded into my pages which reads mp3 files via HTTP anywere on the internet. The XSPF web player does exactly that, and is licensed GPL.
I have developed this tiny plugin to allow WordPress pages to have background MP3 music embedding this player. You can see the player on the right sidebar. Just press play and music should start playing.
Works under Linux and Windows (and probably on every PC with a flash-compatible browser).
Plays local and remote MP3 music (HTTP)
Autostart playing and autorepeat if desired.
Song and Categories database managed from the Options menu
3 player modes selectables.
Track order defined by user.
Inline (on the fly) parameter customization. New!
Hope you enjoy it.
Slim mode. Just an horizontal bar. Clicking on the little arrow on the right jumps to the artists page (when available).
Wide List mode. A list-box with the tracks. Clicking on the photo jumps to the artists page (when available).
[Download] Current version of XSPF Player plugin
A nice online tutorial. Please, contribute to the Wiki.
* Bugfix: Possible security vulnerability. XSPF Player setup could be changed by a CSRF / XSS attack. Fixed.
+ Feature: URL and category description can now have up to 255 chars long.
+ Feature: Version displayed in config menu, and other cosmetics.
+ Feature: Better directory protection.
+ Feature: Button to CLEAR all SQL xspf tables.
* Bugfix: Category edition not shown when no tracks on database. Fixed.
* Bugfix: When no default player mode selected, the player may not work. Fixed.
* Bugfix: The [XSPF] button does not work on WP 2.1. Fixed (Thanks, Renato Alves).
* Bugfix: Cleanup database songs tables when installing for first time.
+ Feature: Now it’s possible (and preferred) to use [XSPF] … [ /XSPF] instead of <xspf>…</xspf> tags.
Other: Everything is in one folder now (source code rearranged)