Closed GoogleCodeExporter closed 9 years ago
I am still not able to send a Tweet but the show WebPart is still working.
Original comment by stormofb...@gmail.com
on 17 Mar 2012 at 4:54
Can you please try the new solution package 3.1. We have implemented caching in
our webpart so once you tweet then you will be able to see the updates in next
15 minute. if you still face unhandled exception then please send me the
sharepoint log file.
Nitin
niting@brickred.com
Original comment by niting@brickred.com
on 21 Mar 2012 at 1:37
I also have the same problem with the new package for Sharepoint 2007.
Original comment by kamaled...@gmail.com
on 23 Mar 2012 at 2:15
Can you send the SharePoint log file after you receive this error?
Nitin
Original comment by tsg.bric...@gmail.com
on 26 Mar 2012 at 6:38
[deleted comment]
Im getting the same error as above.
Sharepoint 2010 and sharepoint-2010-twitter-webparts-3.1
Screenshot and logs are attached
Original comment by Tommy0...@gmail.com
on 30 Mar 2012 at 8:00
Attachments:
Guys,
Can you please send your show tweet webpart settings at my email id
niting@brickred.com. Looks like some environmental issues at your end. We need
to debug the settings so that we can find out the exact problem.
Nitin
Original comment by niting@brickred.com
on 30 Mar 2012 at 8:35
Guys,
Please try new package 3.2 as we have resolved the bugs that you guys are
facing in this release.
Nitin
Original comment by niting@brickred.com
on 9 Apr 2012 at 11:29
thanks man. you rock
Original comment by kamaled...@gmail.com
on 9 Apr 2012 at 2:31
Resolved
Original comment by niting@brickred.com
on 11 Apr 2012 at 9:37
I am getting the same error when I fill out all the options in the web part. it
crashes the whole page.
I am using sp2010 and the latest version of the product.
Original comment by Vectorbo...@gmail.com
on 19 Apr 2012 at 4:38
Are you using version 3.2 because this issue is resolved now and verified by
the users also.
Please send me your twitter details on my email id niting@brickred.com so that
we can check if this is still not fixed for your case.
Nitin Gupta
Original comment by tsg.bric...@gmail.com
on 20 Apr 2012 at 7:24
My issue is the new tweets aren't posting to the webpart. I got my first two
tweets and nothing else. Tweet display limit is set to 10
Original comment by jason.va...@gmail.com
on 7 May 2012 at 9:08
Hi Jason,
There is a cache duration of 15 minutes in the webparts. Are you able to see
your tweets after 15 minutes or not. If not then please send your twitter
webpart settings to niting@brickred.com
Nitin
Original comment by niting@brickred.com
on 14 May 2012 at 9:20
Hi Jason,
Is your issue resolved? If not please send us your twitter webpart settings to
niting@brickred.com or sumitk@brickred.com
Sumit Kanchsn
Original comment by niting@brickred.com
on 1 Jun 2012 at 10:21
Hello, I'm am getting this same issue, with the Show Tweets. I have to remove
the web part after entering in the Twitter Information. This worked fine in my
test environment, but not in my production. I get the following error:
w3wp.exe (0x2078) 0x0EE4 SharePoint
Foundation Runtime tkau Unexpected System.NullReferenceException: Object
reference not set to an instance of an object. at
BrickRed.Webparts.Twitter.ShowTweets.OnPreRender(EventArgs e) at
System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint) b865470c-149d-420e-9315-63b02703b47e
Thanks,
Josh
Original comment by SuchnS...@gmail.com
on 21 Jun 2012 at 5:48
Hi Josh,
Can you please try once in the following order
1. Add web-part to the page
2. Enter the configuration details
3. Click the "Apply" button on the web-part setting section
4. Click the "Ok" button.
As directly clicking on the Ok button is giving the error and we have
identified the issue which will be resolved in our next release.
If this does not resolves the issue then send us your web-part settings at :
sumitk@brickred.com
Original comment by niting@brickred.com
on 25 Jun 2012 at 10:09
Issue resolved in new package version 3.2
Sumit Kanchan
Original comment by niting@brickred.com
on 28 Jun 2012 at 12:17
Original issue reported on code.google.com by
stormofb...@gmail.com
on 17 Mar 2012 at 4:45Attachments: