Well, liquilife, since you are using the Magpie plugin and not some other plugin, if you want to send me FTP information, Control Panel access, and the location of this tag…I can take a quick look and see what I can find out.

Sorry Paul, I didn’t mean to disappear. (school has been nuts).

Anyways, I am using the builtin EE Magpie RSS Parser (v.1.3.2)

I checked the cache directory, it’s set to 777, I deleted the files in the cache and reloaded. It pulled in the new information, but it does not appear to be deleting/updating the cache file correctly.

This the refresh line I am using:

I am not going to assume you want my FTP/EE info, so I’ll wait (if) until you ask

xxdesmus, here is what I found out about the audioscrobbler feed directly from paul via PM’s:

Seems that if the If-Last-Modified header is too recent, their server returns a 404 response.  Currently, the value for that feed is ‘Mon, 09 Apr 2007 17:26:10 GMT’ and that was what happened.  I moved it back an hour and I get a 200 OK response but no data.  Move it back another hour, and I get the full feed again.  So, I think this is more of a problem with their server doing things incorrectly and confusing Magpie.  If there is no data they should be sending a 304 response not a 404 *or* no data at all.

The Magpie Library probably could be modified to not get confused with such random results, so I will make a note to check into that for the next version or 2.0.

It seems the audioscrobbler feed contains a few bugs. I’ve got the same issue as you.

^^ Thanks for the quick reply, and the excellent info

No problem. It’s always good to be in the know Glad I could help for once and not be asking for help, heh.

Based on the description above (I was far too tired last night to comprehend what you told me), shouldn’t we just increase the refresh time to prevent the If-Last-Modified header from being too recent? I just bumped mine up to 60 (minutes) and I’ll report back. Granted, this is not really an ideal solution because the point of a “recent tunes” would be to have it update every few minutes…but maybe this could be start to it at least sort of working.

The refresh=”” parameter does not influence that header.  That is a header that the Magpie Library sends on its own based on the last time it refreshed the cache file.

Hrm. Seems I’m a little behind on the times. I am having the exact same problem as liquilife. Ours are set up the exact same way (go team! hehe).

So then it seems like last.fm broke something?
Those buggers :( My set up USED to work *grumble*

I have a strange idea, and I don’t have the time to try it right this second, but here it goes:

What about passing the Last.fm RSS feed (the user feed with the recent track info) through something like Yahoo Pipes, then using MagPie on the RSS feed Yahoo Pipes spits back out?

I don’t know how bad the lag will be if I use Yahoo Pipes, but I’ll give it a shot on Tuesday when I get some time. I’ll report back if I have any luck.

I have this same problem and I tried this Pipes hack. Didn’t work for me. Any other solutions?

Looks like there hasn’t been any new developments on this, was wondering if anybody came up with a solution. I’m not using FeedGrab but just the included Magpie parser. It’s showing nothing in my template. Any ideas?

Just stumbled on this thread, thought I would throw out that sometimes I have feeds break on me using both these plugins. Usually it is when a feed gets changed by the provider, like changing a node name or layout of the xml. The easiest way to fix a feed is to run it through yahoo pipes. - http://pipes.yahoo.com/pipes/

Forgot to post back here with a followup. Lisa helped me get audioscrobbler parsing correctly with Magpie. Here was her solution.