Hi all,

The newest release of the Blog module, V4.0, includes a feature to allow users to tweet when they create or edit a blog post.  However, I can't seem to get it to work.  I've got the right username and password, but find an error in the event log, listed below.

Has anybody else tried this feature?  Did you have to do anything special to get it to work??

Thanks for any help.

Marty



ModuleId: 685
ModuleDefId: 99
FriendlyName: Add blog entry
ModuleControlSource: DesktopModules/Blog/EditEntry.ascx
AssemblyVersion: 5.4.4
PortalID: 6
PortalName: School To Work Colorado
UserID: 91
UserName: mgoldbergs2w
ActiveTabID: 210
ActiveTabName: Blogs
RawURL: /Community/Blogs/tabid/210/ctl/Edit_Entry/mid/685/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://schooltowork.org/Community/B...fault.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; FunWebProducts; GTB6.5; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 3.5.21022; .NET4.0C; .NET4.0E; Media Center PC 5.0; MS-RTC LM 8; OfficeLiveConnector.1.5; OfficeLivePatch.1.3; SLCC1; Tablet PC 2.0; InfoPath.3; AskTB5.4; Qwest 1.0)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: a5279c4d-3694-4e4f-98e5-bf040a5f013f
InnerException: The remote server returned an error: (401) Unauthorized.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Modules.Blog.Business.Utility.Tweet
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: The remote server returned an error: (401) Unauthorized. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized. at DotNetNuke.Modules.Blog.Business.Utility.Tweet(BlogInfo objBlog, EntryInfo objEntry) at DotNetNuke.Modules.Blog.EditEntry.updateEntry(Boolean publish) --- End of inner exception stack trace ---
Source:
Server Name: GENERIC53

I assume that the "remote server" that returned the "Unauthorized" error is Twitter.  Check that you have configured a valid username/password for Twitter in your blog settings.

Hi Joe, Yes, the "remote server" is presumed to be Twitter. I have double-checked the username/password and even tried another Twitter account, all with no luck.

Marty

Your best bet, then, is to take it to the Blog team.

I am not sure when the v4.0 came out nut I know that Twitter recently made some security changes so I am wondering if that is causing the problem. I just tried to use it too with no luck.

Hi Kyle, Yes, the blog team has confirmed it is due to Twitter's change to oAuth authentication. I'm a bit disappointed since the change at Twitter was announced last spring and the blog team didn't consider that. I'm waiting impatiently for a fix...