Bugzilla – Bug 6722
content type field in tracks table no longer populated with only tokens
Last modified: 2009-09-08 09:16:15 UTC
from discussion on bug 6719 ------- Comment #3 from slim-mail@deane-freeman.com 2008-01-22 12:08 ------- content type has previously been used as a token so that pages like the file types settings can be localised, as well as the song info/track info views in player and web ui. It seems that recently some content types have taken on variants that are expecting to be treated as raw strings, instead of tokens (content_type = MP3 (Live 365) for example). So, in legacy terms, the type was intended to be localised. This is how MOV becomes "Apple AAC for Movie File"
to be clear, what's the bug: that they aren't localised (which would be the current case for jive songinfo), or that they aren't always tokens?
tokens I think. changing summary to reflect that.
The database should still have tokens, the special values such as "MP3 (Live365)" come from protocol handlers.
Ahm... is this still an issue?
Nobody can seem to figure out what this was about. Feel free to reopen if you have a memory.