Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogTwitter IntegrationTwitter Integration
Previous
 
Next
New Post
3/24/2011 8:19 AM
 
Why was twitter integration taken out of blog module 4.0.1, it worked fine in 4.0.0?
How do we get it back?
 
New Post
3/24/2011 8:34 AM
 
@Don - Last spring, Twitter changed their Terms of Service to require OAUTH authentication for applications posting to a users twitter account.  Unfortunately, Blog was relying the old Username/Password authentication method.  When we evaluated the effort need to updated the twitter feature to support the new authentication method, it was determined that we didn't have the time in that release to do it properly. 



Realistically, Blog should be able to post a status update to any social network and not just Twitter and it was felt that it would be better to use a core service to enable this feature.  This will allow blog to become much "lighter" and to leverage core functionality rather than re-inventing the wheel for each module that would like this ability.  With the recent acquisition of Active Modules and their Active Social platform, this is close to becoming a reality.  Active Social's Journaling feature will allow Blog to publish to the Active Social Journal which will in turn handle posting to the appropriate social networks.

Joe Brinkman
DNN Corp.
 
New Post
3/31/2011 1:35 PM
 
@Joe



Any idea how the ConsumerKey/ConsumerKeySecret part of OAuth might be handled? We have the same issues with our own application. Seems the only way for us to go is to create this key and hardcode it into the module, which is not best practice for distributing a module. Could this be something that Dotnetnuke could publish to module developers. The relevant "how-to" bit in the TwitterVB api documentation is below. Basically you send the application key and secret when requesting an authentication and get back your OAuth Token. Definitely seems like this could be done in the core to populate the portal settings?



    Public ConsumerKey As String = "CONSUMERKEY"

    Public ConsumerKeySecret As String = "CONSUMERKEYSECRET"



    Protected Sub Page_Load(ByVal sender As Object, ByVal e As EventArgs) Handles MyBase.Load

        Dim tw As New TwitterAPI

        If Request("oauth_token") Is Nothing Then

            '' Send the browser to Twitter, and send the URl of the page to come back to after authentication

            Response.Redirect(tw.GetAuthorizationLink(ConsumerKey, ConsumerKeySecret, "http://localhost/default.aspx"))

        Else

            '' Exchange the rquest token for an access token

            tw.GetAccessTokens(ConsumerKey, ConsumerKeySecret, Request("oauth_token"), Request("oauth_verifier"))

        End if

       ...


Colm Ryan Director
3rd i IT and Business Services Limited

www.actravia.com
Registration and Booking Solutions for Dotnetnuke
www.3rdi.ie
IMCA Registered Management Consulting Practice. Business and IT Strategy, IT Project Management and Product Development
 
New Post
4/1/2011 12:47 PM
 
With DNN 5.6.1 and blog module 4.0.0 using Oliver Hine Twitter authitication Provider. OAuth in the login provider takes care of ConsumerKey/ConsumerKeySecret as part of OAuth. Add the secret and key in the web config.
Even though the blog module uses username and pass it still works. Or use feedburner or twitter feed and tweetmeme for the same functionality, but better twitter integration and internet positioning of blog posts.
The team should know this and should have never taken it out of blog module 4.0.1.
 
New Post
4/6/2011 1:51 PM
 
The removal of functionality was definitely a poor decision - and very disappointing. Why was this not mentioned in the release notes?. The ability to accommodate OATH for this module was definitely something you could have turned to the DNN community for help.

Please make wiser decisions in the future.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogTwitter IntegrationTwitter Integration


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out