Thread

Hello all -

Well my site has started giving me a new error and I’m pulling my hair out trying to track it down. I hope it’s something simple and I’m just missing something.

This was all working fine up until about Jan 27th.

Basically I’m using Magpie to pull in a Twitter feed on EE 1.6.6, Magpie plugin version 1.4.

The page is…
http://jamtopia.com/phishtwit-new/

The feed URL is…
http://search.twitter.com/search.atom?q=Phish&rpp=25&page=1

The error is…
Warning: MagpieRSS: Failed to fetch http://search.twitter.com/search.atom?q=Phish&rpp=25&page=1. (HTTP Response: HTTP/1.1 301 Moved Permanently ) in FILESYSTEM_PATH_REDACTED/plugins/pi.magpie.php on line 1416

Again, this was working perfectly up until recently.

I know my hosting company moved my server to a different spot on their file system, but per the error above Magpie is correctly locating this new spot.

I don’t believe Twitter has changed the search API at all, and when I try to pull up the RSS feed directly in the browser it works fine.

And fwiw, I believe this may have something to do with the magpie caching. I say this b/c up until tonight it would work for searches I had previous tried, but it would diplay old Tweets that were from the latest cache. If I tried a new search, I’d get this error. When I noticed it was displaying old Tweets for the previously used searches, I cleared the magpie cache, and now it’s doing it for all searches. (Note: sorry if that didn’t make sense… best explanation I can muster right now.)

Huge thanks in advance for any help you may be able to provide on this.

Take care,
TL

P.S. I removed the exact path to my admin folder in the error message above but if you need to see it to help please shoot me a private message.

Oh yeah, one more thing… not sure if this will help anyone figure this out, but it works perfectly for this feed… http://twitter.com/favorites/22603994.atom?page=1

Todd,

First off, it is a recommendation that you upgrade to the latest version of EE 1.6.8

I can pull that Twitter feed no problems using the following code. What have you got?

{exp:magpie url="http://search.twitter.com/search.atom?q=Phish&rpp=25&page=1" limit="10" refresh="720"}
<ul>
{items}
<li><a href="http://{link}">{title}</a></li>
{/items}
</ul>
{/exp:magpie}

Check the permissions on your cache folder is still set to 777

Todd,

First off, it is a recommendation that you upgrade to the latest version of EE 1.6.8

I can pull that Twitter feed no problems using the following code. What have you got?

{exp:magpie url="http://search.twitter.com/search.atom?q=Phish&rpp=25&page=1" limit="10" refresh="720"}
<ul>
{items}
<li><a href="http://{link}">{title}</a></li>
{/items}
</ul>
{/exp:magpie}

Check the permissions on your cache folder is still set to 777

John -

Thanks so much for the quick reply.

I double-checked the permissions and created a brand new template which includes nothing but your sample code…

http://jamtopia.com/site/magpietest

Same result :(

Please note that since I have it set to only show PHP/MySQL errors to superadmins you won’t see the error message on that test page.

I can try upgrading ro 1.6.8 tomorrow but this was all working fine on this version of EE so I’m not sure how / why that would fix the issue. Plus the fact that the other URL works fine (http://twitter.com/favorites/22603994.atom?page=1) is really throwing me for a loop and leads me to believe that it’s not the caching thing and not really a function of the EE version I’m using.

Let me know if you think it’s worth the effort to upgrade with respect to this issue.

Again, thanks.

TL

I thought of something that may explain the issue… it’s possible my server has been blacklisted from using the Twitter search API!

I just sent and email to Twitter’s API support in hopes that they can provide a response.

That MIGHT explain why the favorites thing works on my site, and the search API call works on your site but not on mine.

Apologies for not thinking of this sooner, and will post a reply as soon as I hear back from them. If you can think of anything else that may be causing this in the mean time please do drop a reply.

And if this does turn out to be the case, sorry for sending you on a goose chase.

TL

Todd,

I cleared the magpie cache, and now it’s doing it for all searches.

Did you do this manually by FTPing in and deleting all folders in system/cache/ ?

Let me know if you think it’s worth the effort to upgrade with respect to this issue.

It is recommended but not related to your issue I believe

I see you are using a htaccess. Can you disable this temporarily and see if that makes a difference?

Todd just saw your other reply.Let us know what you find out

Haven’t heard back from Twitter so I’m still trying to troubleshoot and noticed something interesting… the sample code works fine on another site that sits on the exact same hosting package.

I had always thought Twitter whitelist / blacklist was based on IP address so this would seem to rule that out.

Still hoping to hear back from them and in the mean time going to try the suggestions above… upgrading to 1.6.8 and temporarily disabling my .htaccess.

ARGH.

TL

Let us know how the upgrade goes 😊

Let us know how the upgrade goes 😊

Not only did the upgrade go perfectly, for whatever reason it fixed the bug.

I have no idea why, not do I care. Just ecstatic to be back in business!

Here’s the link to the live site in case anyone’s interested…

—> http://phishtwit.com <—

Thank you John for suggesting I upgrade and thank you EE team for your excellent work. This software (and this forum) have continually proven to be fantastic.

Take care all,
TL

You are welcome. Feel free to start a new thread if you have any more questions.