CMS MADE SIMPLE FORGE

TweetMadeSimple

 
Back Back to List

[#5790] Fatal error every 4th page refresh

avatar
Created By: Ryan Foster (RytoEX)
Date Submitted: Fri Dec 03 04:50:36 -0500 2010

Assigned To:
Version: Twitter 1.2.1
CMSMS Version: None
Severity: Major
Resolution: None
State: Open
Summary:
Fatal error every 4th page refresh
Detailed Description:
Sometimes the 3rd, 4th, or 6th refresh would cause one of two fatal errors. 
However, while the failure didn't happen "like clockwork", it did happen often.


    Twitter
Fatal error: Uncaught exception 'EpiTwitterServiceUnavailableException' with
message '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head>
<title>503 Service Temporarily Unavailable</title> </head><body> <h1>Service
Temporarily Unavailable</h1> <p>The server is temporarily unable to service your
request due to maintenance downtime or capacity problems. Please try again
later.</p> <p>Additionally, a 403 Forbidden error was encountered while trying
to use an ErrorDocument to handle the request.</p> </body></html> ' in
/modules/Twitter/lib/epi/EpiTwitter.php:269 Stack trace:
#0 /modules/Twitter/lib/epi/EpiTwitter.php(218):
EpiTwitterException::raise(Object(EpiCurlManager), false)
#1 /modules/Twitter/lib/epi/EpiTwitter.php(119):
EpiTwitterJson->__get('response')
#2 /modules/Twitter/lib/epi/EpiTwitter.php(36): EpiTwitter->request('GET',
'/statuses/user_...', Array)
#3 / in /modules/Twitter/lib/epi/EpiTwitter.php on line 269


OR


    Twitter
Fatal error: Uncaught exception 'EpiTwitterException' in
/modules/Twitter/lib/epi/EpiTwitter.php:271 Stack trace: #0
/modules/Twitter/lib/epi/EpiTwitter.php(218):
EpiTwitterException::raise(Object(EpiCurlManager), false)
#1 /modules/Twitter/lib/epi/EpiTwitter.php(119):
EpiTwitterJson->__get('response')
#2 /modules/Twitter/lib/epi/EpiTwitter.php(36): EpiTwitter->request('GET',
'/statuses/user_...', Array)
#3 /modules/Twitter/Twitter.module.php(291):
EpiTwitter->get('/statuses/user_...', Array)
#4 /modules/Twitter/Twitter.module.php(230): Twitter->getUserTimeline(Array)
#5 /modules/Twitter/action.default.php(21): Twitter->getTimeline('user', Array)
#6 /lib/classes/class.module.inc.php(2024): include('/modules/Twitte...')
#7 /modules/Twitter/ in /modules/Twitter/lib/epi/EpiTwitter.php on line 271


History

Comments
avatar 
Date: 2012-10-23 11:04
Posted By: Tristan (tristan)

Same problem over here but just with the limit of 350 requests an hour:

Fatal error: Uncaught exception 'EpiTwitterBadRequestException' with message
'{"request":"\/1\/statuses\/user_timeline.json","error":"Rate limit exceeded.
Clients may not make more than 350 requests per hour."}' in
/modules/Twitter/lib/epi/EpiTwitter.php:254 Stack trace: #0
/modules/Twitter/lib/epi/EpiTwitter.php(219):
EpiTwitterException::raise(Object(EpiCurlManager), false) #1
/modules/Twitter/lib/epi/EpiTwitter.php(120): EpiTwitterJson->__get('response')
#2 /modules/Twitter/lib/epi/EpiTwitter.php(37): EpiTwitter->request('GET',
'/statuses/user_...', Array) #3 /modules/Twitter/Twitter.module.php(355):
EpiTwitter->get('/statuses/user_...', Array) #4
/modules/Twitter/Twitter.module.php(228): Twitter->getUserTimeline(Array) #5
/module in/modules/Twitter/lib/epi/EpiTwitter.php on line

maybe you could introduce a cache function, but be sure to catch these errors
first.
avatar 
Date: 2012-10-23 11:15
Posted By: Jean-Christophe Cuvelier (totophe)

The problem happen on shared hosting, most of the time.

Anyway, Twitter is releasing his API 1.1 soon with many requirements, and I
think the Twitter module will not be able to be really fixed...