ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Magpie is Stuck

March 20, 2007 1:40pm

Subscribe [0]
  • #16 / Apr 09, 2007 2:33pm

    Paul Burdick

    480 posts

    With all of those permissions, unless you are on a Windows server, which tend to have a different way of doing writing permissions, your cache should be overwritten correctly and based on the parameter you set for the tag.

  • #17 / Apr 09, 2007 2:33pm

    DigiFiend

    41 posts

    I should add that I am running a cron job via my host Dreamhost and not through an ee module or code.

  • #18 / Apr 09, 2007 2:37pm

    Paul Burdick

    480 posts

    Yes, got that, DigiFiend.  Dreamhost could have done only a limited number of things to prevent those files from being rewritten. Their past history does not preclude doing such things, so if you have not emailed them and asked about any changes you might do that now.

  • #19 / Apr 09, 2007 2:38pm

    liquilife

    147 posts

    And I will confirm that I am on a Unix server with the tag set to update every 10 minutes

  • #20 / Apr 09, 2007 2:40pm

    Paul Burdick

    480 posts

    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.

  • #21 / Apr 13, 2007 12:38am

    xxdesmus

    7 posts

    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:

    {exp:magpie url="http://ws.audioscrobbler.com/1.0/user/xxdesmusxx/recenttracks.rss" limit="6" refresh="5"}

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

  • #22 / Apr 13, 2007 12:56am

    liquilife

    147 posts

    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.

  • #23 / Apr 13, 2007 1:00am

    xxdesmus

    7 posts

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

  • #24 / Apr 13, 2007 1:09am

    liquilife

    147 posts

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

  • #25 / Apr 13, 2007 5:32pm

    xxdesmus

    7 posts

    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.

  • #26 / Apr 13, 2007 7:52pm

    Paul Burdick

    480 posts

    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.

  • #27 / Apr 15, 2007 1:31am

    katili

    31 posts

    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*

  • #28 / Apr 22, 2007 8:51pm

    xxdesmus

    7 posts

    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.

  • #29 / Apr 30, 2007 3:31am

    wilmot

    6 posts

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

  • #30 / Jan 06, 2008 4:18pm

    Joey Trimmer

    128 posts

    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?

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases