Quote:
Originally Posted by DrO
it's hard to give support when support is not around aka i'm not a robot and needed a week off.
to my knowledge the handling of the api's shouldn't have changed with the other changes which have been made though i'm not 100% on that area. will raise the issue though if you can confirm exactly what you were using beforehand then that will make it easier to compare against.
-daz
|
Thanks for replying daz, but I thought you had a dedicated dev team reading the forums. I can only guess but before it was regex matching mt parameter, therefore &mt=audio would match both 'audio/mpeg' and 'audio/aacp' and &mt=mpeg would only match 'audio/mpeg'. Now you need to specify the whole thing &mt=audio/mpeg if you want to match 'audio/mpeg' but the wiki specification still says &mt=mpeg is enough, which is false as this is what broke.
I can guarantee you that API changed as the result of the changes.