The feed is updating correctly, and I haven’t even touched the magpie plugin or code in a few months, but I noticed the other day it just stopped updating.
Here is the code I am using (and have been using for months now):
Ive got what appears to be the same issue. I use the Feedgrab plugin (which utilizes the magpie plugin core) and all of a sudden, my code for retrieving info off a last.fm rss feed has stalled.
After upgrading the feedgrab plugin to .7, the feed list did change, but it’s stuck again. Perhaps there is something going on with caches? Makes no sense to me since I haven’t touched this code in months.
Same versions as above (EE 1.5.2, Magpie 1.3.2), also running feedgrab .7
Go into your system folder via FTP and double check that the cache folder has 777 permissions. Then, delete the contents of the cache directory. Sounds like a cache file is getting stuck, likely because of permissions.
Go into your system folder via FTP and double check that the cache folder has 777 permissions. Then, delete the contents of the cache directory. Sounds like a cache file is getting stuck, likely because of permissions.
The cache directory did indeed have 777 perms, deleting the items in the cache folder did allow feedgrab to update the info. As the feed is a last.fm feed based on music played at home, I’ll see if the cache continues to stick or if this was a random occurrence.
Go into your system folder via FTP and double check that the cache folder has 777 permissions. Then, delete the contents of the cache directory. Sounds like a cache file is getting stuck, likely because of permissions.
As mentioned before, the cache directory did have 777 permissions.
Running version .61 of Feedgrab, I deleted the contents of the Magpie cache directory, and the plugin worked. Once. Then was restuck. Manually deleting the contents of the directory allows the plugin to update a single time.
Running version .7 of Feedgrab, the cache isn’t an issue. I can’t run .7 however because it won’t process the long dash in my feeds properly.
Since I seem to have narrowed down the problem with Feedgrab to a magpie issue, would it be best to keep asking questions in a Magpie thread or in a Feedgrab thread? Also, are you aware of any server side change that could cause suck a problem with cache files getting stuck?
Go into the magpie_cache directory. There is going to be a file in there, does it have 777 permissions. If PHP is unable to modify the file, then that would cause it not to update. Also, what value do you have for the refresh=”” parameter?
Go into the magpie_cache directory. There is going to be a file in there, does it have 777 permissions. If PHP is unable to modify the file, then that would cause it not to update. Also, what value do you have for the refresh=”” parameter?
Magpie Cache dir = 777
Current 3kb cache file = 777
Current “track grabber” template that populates blog:
I just downloaded the FeedGrab plugin and I see it includes its own version of the Magpie library and not the one included in ExpressionEngine. So, this is officially a problem with it and since it is a third party plugin you should contact the author. They should probably first make sure the download is happening and then whether the script is processing the data correctly.
I just downloaded the FeedGrab plugin and I see it includes its own version of the Magpie library and not the one included in ExpressionEngine. So, this is officially a problem with it and since it is a third party plugin you should contact the author. They should probably first make sure the download is happening and then whether the script is processing the data correctly.
Thanks Paul, I work with the feedgrab author to resolve this.
I have had the same problem using the included magpie plugin with Expression Engine. I have a last.fm rss feed as well updated by Winamp that has worked beautifully for months and months. Not long ago the EE magpie plugin stopped updating. I’ve confirmed the RSS feed is updating so it’s an issue with Magpie. Oddly enough I’ve made no changes to bring about this issue.. it just sort of happened on it’s own.
I have verified the cache folder for magpie is set to 777. I can delete out the cache and the RSS list will forcefully update, but then it’s stuck again.
Are any of you using Dreamhost by chance? Perhaps Dreamhost made a global change by chance affecting how this works?
I have had the same problem using the included magpie plugin with Expression Engine. I have a last.fm rss feed as well updated by Winamp that has worked beautifully for months and months. Not long ago the EE magpie plugin stopped updating. I’ve confirmed the RSS feed is updating so it’s an issue with Magpie. Oddly enough I’ve made no changes to bring about this issue.. it just sort of happened on it’s own.
I have verified the cache folder for magpie is set to 777. I can delete out the cache and the RSS list will forcefully update, but then it’s stuck again.
Are any of you using Dreamhost by chance? Perhaps Dreamhost made a global change by chance affecting how this works?
I am also using dreamhost. I suspect it may some problem with the specific version of magpie being used. As documented above, I’m actually using a plugin that has incorporated magpie code in it, so my problem isn’t identical but similar.
I’ve worked around the problem by running a cron job that deletes the magpie cache files every 10 minutes (my code that utilizes the magpie cache updates every 15 minutes). Sloppy kludge like fix, but the only way I could get around the problem.
If you find out about any dreamhost changes, I’d be interested in hearing about them.
I’m not on Dreamhost, and I’m having the same problem. I just deleted the FeedGrab plugin from my site (it’s never worked well for me), and cleared my magpie cache. Should that solve the problem, or am I going to have to run a chron to automate the ?
And, if I have to use chron, can anyone explain to me how it’s done? I feel stupid every time I look at the instructions. Do I just put the code into any old template? Does the template have to be accessed in order for the chron to run?
The Magpie plugin, that is distributed with ExpressionEngine, should delete the cache automatically as long as the permissions are set to writable for the /system/cache/ folder *and* your server does not have special restrictions. If one is using another plugin script that is using the Magpie library, then I cannot guarantee that it has been written correctly and will automatically delete the cache files correctly.
Using the Cron plugin in ExpressionEngine is likely not to make much of a difference, as it is still PHP trying to delete or overwrite the cache.
Paul, I had only checked the magpie folder within the cache folder for the correct permissions. Your post prompted me to check the permission of the ‘cache’ folder and it was indeed set to 755. Now set to 777.
That being said, it is still not updating. I have ensured that the cache folder and the magpie folder is set to 777. Heck, even the temp files created in the magpie cache folder are created with 777 permissions. I’m completely lost here.
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.
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.
