sonnyt / tweetie

Simple jQuery Twitter feed plugin
https://sonnyt.com/tweetie
312 stars 117 forks source link

Tweetie no longer works #22

Closed Isacco71 closed 10 years ago

Isacco71 commented 10 years ago

Hi Sonny, thank you for your very useful script.

I had installed Tweetie on my site a month ago, and everything worked fine ... but now something is wrong. I downloaded and added the latest version of all files, but the problem remains. Could you tell me what has changed?

Here the test page on my website: http://www.subaquadive.it/js/tweetie/index.html

The box that needs to accommodate the feed is in the footer on the site, at this address: http://www.subaquadive.it/en/index.php

kostasx commented 10 years ago

Can you have a look at the server logs for any clue? You probably, ought to check if curl_init() is enabled on your server's PHP: return function_exists('curl_version'); The twitter OAuth files depend on this function.

Isacco71 commented 10 years ago

Hi Kostasx, yes curl_init appears to be active... One month ago,when I've installed Tweetie for the first time, everything worked fine.

kostasx commented 10 years ago

What about the server logs? Have you checked them? You need to find out what causes the 500 (Internal Server Error).

Isacco71 commented 10 years ago

Here a line from the server log 78.15.174.213 www.subaquadive.it - [10/Jun/2014:13:57:14 +0200] "GET /js/tweetie/api/tweet.php?username=isaccocurreli&list=&hashtag=&count=1&exclude_replies=false HTTP/1.1" 500 351 "http://www.subaquadive.it/js/tweetie/index.html" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36"

kostasx commented 10 years ago

This seems to be the access log. Can you check the error log? Try to connect from the site, watch for the 500 error on the browser console, check the time, and then check the server's error log.

Isacco71 commented 10 years ago

Ok, I don't know if this can help...

78.15.174.213 www.subaquadive.it - [10/Jun/2014:14:40:17 +0200] "GET /js/tweetie/index.html HTTP/1.1" 200 4869 "-" "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0" 78.15.174.213 www.subaquadive.it - [10/Jun/2014:14:40:17 +0200] "GET /js/tweetie/tweetie.js HTTP/1.1" 304 - "http://www.subaquadive.it/js/tweetie/index.html" "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0" 78.15.174.213 www.subaquadive.it - [10/Jun/2014:14:40:17 +0200] "GET /js/tweetie/api/tweet.php?username=isaccocurreli&list=&hashtag=&count=1&exclude_replies=false HTTP/1.1" 500 351 "http://www.subaquadive.it/js/tweetie/index.html" "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0" 78.15.174.213 www.subaquadive.it - [10/Jun/2014:14:40:18 +0200] "GET /js/tweetie/api/tweet.php?username=isaccocurreli&list=&hashtag=&count=10&exclude_replies=false HTTP/1.1" 500 351 "http://www.subaquadive.it/js/tweetie/index.html" "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0"

Isacco71 commented 10 years ago

SyntaxError: Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead jquery.min.js:1 Error: http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js is being assigned a //# sourceMappingURL, but already has one

kostasx commented 10 years ago

500 Internal Server Error. "More information about this error may be available in the server error log." The problem is in the api/tweet.php file of the tweetie plugin. Try searching for the server error logs. Something breaks when this file is executed on the server side.

Isacco71 commented 10 years ago

OK, thank You very much! I will try... It is strange because the file is the original tweet.php, I did not make any changes.

sonnyt commented 10 years ago

@Isacco71 Hey Man, it seems like the tweet.php file is not being found.

Currently it's trying to fetch from http://www.subaquadive.it/en/api/tweet.php?username=isaccocurreli&list=&hashtag=&count=10&exclude_replies=false but it's returning 404.

Make sure the file path is correct and accessible.

Sonny, P.S @kostasx thanks for the help :)

kostasx commented 10 years ago

That's on the 2nd link, sonnyt. In the first one (Demo: http://www.subaquadive.it/js/tweetie/index.html), the tweet.php is found but crashes on the server side.

kostasx commented 10 years ago

Are you running an apache webserver (linux)? If so, try and adding an .htaccess file in the /js/tweetie/api/ folder in your server, and browse to http://www.subaquadive.it/js/tweetie/api/tweet.php again. If everything works fine, you should see an error report on the page that can lead us to the root of the problem. The contents of the .htaccess file are:

php_flag display_errors 1 php_value error_reporting 30719

P.S. @sonnyt thanx for the plugin :)

Isacco71 commented 10 years ago

OK, I did it... but the script already returns 500... not error report

kostasx commented 10 years ago

hmmmmm. The error reporting depends on the server configuration. I guess it doesn't work with the current configuration. It seems like you have to dig a little deeper into the server's error logs. Good luck.

Isacco71 commented 10 years ago

@sonnyt I've fixed the wrong url returning 404 in the website...

Isacco71 commented 10 years ago

@kostasx Thank U so much!

kostasx commented 10 years ago

@Isacco71 Hey, one last try. Try replacing the tweep.php file with this one: http://pastebin.com/Bgd2JDna It encloses the code inside a try catch statement. Let me know if it produces a different output. ( Be sure to keep the .htaccess on the api/ folder. ) ...and visit: http://www.subaquadive.it/js/tweetie/api/tweet.php

Isacco71 commented 10 years ago

OK, I did it... but not yet :( thank you anyway ;)

jenbuzz commented 10 years ago

Maybe you copy-pasted a bad character somewhere. That was the only way I could get the same error. Try downloading the plugin again and overwrite all files. Or at least take a look at your config.php; maybe that's where you did something wrong. It could be as simple as a missing semicolon or something like that.

Isacco71 commented 10 years ago

Hi @dan-lyn! I already tried to replace all the files, I also changed the api-keys...but nothing. The strange thing is that it worked before, and that has stopped without any intervention on the code.

jenbuzz commented 10 years ago

@Isacco71 did you ever take a look in the error_log as previously suggested? What you copy-pasted here was from the access_log

Isacco71 commented 10 years ago

I cannot find the error log on the server, I wrote to the customer care for help... waiting for it :(

sonnyt commented 10 years ago

I will close this because it's more of hosting error and not plugin. Please contact your hosting provider, if anything come back to us :)