Title: Custom Fields?
Last modified: August 21, 2016

---

# Custom Fields?

 *  Resolved [jberg1](https://wordpress.org/support/users/jberg1/)
 * (@jberg1)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/custom-fields-122/)
 * Hello. I upgraded to v1.8.8 and suddenly all my audio stopped working. I use 
   custom fields to define the mp3 track and then call that track in the post with
   the shortcode.
 * custom field
    `name: 1 mp3 ; value: Song Title@audio/file/location.mp3` then 
   use shortcode `[mp3-jplayer track="1" width="550px" list="n" style="text nolistbutton"
   dload="y" pn="n" stop="n"]`
 * After upgrade all I see is a 1 in the song title, and it doesn’t play any file(
   just says connecting). Is there a new way to do this with custom fields in the
   new version? I downgraded back to v1.8.7 for now. Hoping I don’t need to go back
   and rewrite all my shortcodes.
 * Thanks for any help.
 * [https://wordpress.org/plugins/mp3-jplayer/](https://wordpress.org/plugins/mp3-jplayer/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [simon.ward](https://wordpress.org/support/users/simonward-1/)
 * (@simonward-1)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/custom-fields-122/#post-4868750)
 * Hello,
 * took a sec to realise what was going on here, explanation as to why it used to
   work, why it bugged, and how to fix it as follows:
 * Firstly there are 2 errors in your shortcode –
 * 1) The correct param name is `tracks` (with an ‘s’) not `track`.
 * 2) Playlist players have never supported picking-off of the custom fields by 
   using a number (this is a feature of single file players only).
 * The reason it used to work for you is because of that error in the tracks parameter
   name. The param was ignored so you basically weren’t specifying any tracks. Therefore
   asking the player to look in the custom fields to try find something to play.
 * Last update I made it so it doesn’t matter whether you use `track` or `tracks`
   in any of the shortcodes (it was fussy and annoying that the singles and playlisters
   had a different param name) so suddenly your ‘track’ parameter came to life and
   gave the shortcode a track (an unplayable one!).
 * To fix it simply remove the ‘track’ (or ‘tracks’) param completely from your 
   shortcodes (or you could leave it blank eg. track=””), it shouldn’t really be
   there if you intend to pick up custom fields using the playlisters.
 * Simon
 *  Thread Starter [jberg1](https://wordpress.org/support/users/jberg1/)
 * (@jberg1)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/custom-fields-122/#post-4868783)
 * Ah! My typo is revealed.
    I converted from a Playlist player to a single file
   player a while back when setting them up in a custom post type. Thought I was
   doing it right.. guess not.
 * I will update my shortcodes.
    Thanks for your response and help.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Custom Fields?’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/mp3-jplayer_c3a59d.svg)
 * [MP3-jPlayer](https://wordpress.org/plugins/mp3-jplayer/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mp3-jplayer/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mp3-jplayer/)
 * [Active Topics](https://wordpress.org/support/plugin/mp3-jplayer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mp3-jplayer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mp3-jplayer/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [jberg1](https://wordpress.org/support/users/jberg1/)
 * Last activity: [12 years, 1 month ago](https://wordpress.org/support/topic/custom-fields-122/#post-4868783)
 * Status: resolved