Closed GoogleCodeExporter closed 9 years ago
Could you please let us know the exact steps you took for the configurations...
Please send the screen-shots as well
Original comment by tsg.bric...@gmail.com
on 14 Sep 2011 at 7:00
Hi,
Are you still facing this issue. Can we help you out in the resolution. Please
send us some more details as asked earlier to resolve this issue.
Nitin Gupta
Original comment by tsg.bric...@gmail.com
on 22 Sep 2011 at 12:04
Hi,
Still the issue is same,i am unable to get the feeds under Show Tweets web
part.I have followed the step-step as mentioned in your article .At the same
time,"Tweet" web part is working fine .With this web part i am able to tweet to
other users.Could you please suggest me with some solution?
Original comment by pearlpiy...@gmail.com
on 23 Sep 2011 at 5:14
Hi It would be better if you can provide us the api keys and few screenshots.
you can mail me details at ashutoshs@brickred.com to reproduce the same
scenario at our end.
Original comment by ashuto...@brickred.com
on 23 Sep 2011 at 10:02
Hi Pearl,
Is this issue resolved or you are still facing?
Nitin Gupta
Original comment by nitingup...@gmail.com
on 26 Dec 2011 at 12:18
I experience the same issue since version 2. In version 3 there's no change. i
think i can locate the problem: on our testserver everything works fine. for
the first 3-5 minutes it also works on our live system (screenshot
"success.png"). after this period in version 2 our twitter account was blocked
by twitter itself. in the most current version it's just the webpart that
doesnt' work anymore (screenshot "error.png" says: the object reference has not
been set to an instance). very interesting: when i configure the twitter
settings leaving the access tokens blank sharepoint doesnt show an error (of
course the twitter webpart tells me that it still needs properties). but when i
fill out the access tokens sharepoint throws an error (screenshot:
"ConfigurationException.png" says: Unexpected Exception). Nevertheless it works
for 3-5 minutes. As i see the webpart refreshs every 10-20 seconds. since our
users have their intranet open for the hole day, there are running 100
instances of this webpart which is refreshing every 10 seconds. i think this is
the problem because as i mentioned: on our testsystem everything works fine.
could you update the wiki how i have to setup the app in twitter? i'm also
wondering why i need to fill out the access while i just want to show the
tweets (i just use the show tweet webpart!).
if you like to i can send you our tokens.
kind regards,
Uli
Original comment by uli.armb...@heco.de
on 31 Jan 2012 at 3:45
Attachments:
by the way: i'd really like to get a version that doesn't need twitter api
access. the webpart just needs to show a tweet of a user so you wouldn't need
the twitter api, do you?
Original comment by uli.armb...@heco.de
on 31 Jan 2012 at 3:57
Hi,
The error that you are facing at your environment is because of the Rate Limit
from Twitter. In your case the number of requests are very high which twitter
is not permitting.
The default rate limit for calls to the REST API varies depending on the
authorization method being used and whether the method itself requires
authentication.
Unauthenticated calls are permitted 150 requests per hour. Unauthenticated
calls are measured against the public facing IP of the server or device making
the request.
OAuth calls are permitted 350 requests per hour and are measured against the
oauth_token used in the request.
Please read following link for the better understanding
https://dev.twitter.com/docs/rate-limiting
Nitin Gupta
Original comment by tsg.bric...@gmail.com
on 6 Feb 2012 at 8:55
Original comment by tsg.bric...@gmail.com
on 7 Feb 2012 at 7:50
[deleted comment]
@Nitin Gupta: So who would be able to use this webpart besides a company with
2-5 co-workers?
we solved the problem by using the content editor webpart referencing our
website. we created a php site which uses a typo3 plugin...works fine. which
way do common websites use to show their tweets, for example wordpress?
Original comment by uli.armb...@heco.de
on 24 Feb 2012 at 6:03
I completely understand your concern here and we are looking into the
alternatives on how we can provide this functionality to enterprise customers.
Will keep you posted on this.
Nitin
Original comment by niting@brickred.com
on 19 Mar 2012 at 7:11
We are going to implement caching of 10 minutes to resolve this problem. Will
update you guys once the new package is available.
Nitin
Original comment by niting@brickred.com
on 20 Mar 2012 at 8:08
Hi All,
Please download new package 3.1 that will resolve your issue. We have
implemented a cache of 15 minute duration so that we can avoid a limit of 350
calls per hour to twiiter. The only concern with this cache is that data will
be refreshed after every 15 minutes and would not be the instantaneous. So if
you are tweeting with the webpart then please wait for 15 minutes to refesh it
on show tweets webpart.
Nitin
Original comment by niting@brickred.com
on 21 Mar 2012 at 10:56
[deleted comment]
Nice, i will give it a try in the next few days
Original comment by uli.armb...@heco.de
on 23 Mar 2012 at 11:38
Original issue reported on code.google.com by
pearlpiy...@gmail.com
on 13 Sep 2011 at 11:32