We have had a few clients that have recently been integrating Dynamic Login with Facebook, Twitter, and Linked In and these clients have faced a few issues getting everything to work… This can be difficult to debug because a lot of the functionality is happening behind the scenes.
First – Make sure you are running on 04.00.30 of Dynamic Login or above. We had several patches that were necessary to make sure the module works with new requirements for Facebook.
Compare your settings below for Facebook, Twitter, and Linked In with ours for both the module settings and then also (and probably more importantly) for the app settings page for each specific social networking site.
Note: There are a few limitations within some of the social networking sites (Twitter and Linked In) compared to some of the features of Facebook (Silent Post options and also if the email can be used etc…). We are still working on some of these for future versions and hope to offer the most features possible for all of the different social networking integration options!
Facebook Login Integration (Facebook Configuration Area)
https://developers.facebook.com/apps
Facebook Login Integration (Dynamic Login Configuration Area)
Twitter Login Integration (Twitter Configuration Area)
Twitter Login Integration (Dynamic Login Configuration Area)
LinkedIn Login Integration (Linked In Configuration Area)
Linked In Login Integration (Dynamic Login Configuration Area)
Hopefully you will find these settings and configuration options useful. If you are trying to implement other features within the configuration area (such as alternate fields, username prefix’s, or other options and they are not working, at least make sure you have reviewed these settings compared to your settings to determine if the module is functionality properly with the basic and general settings trying to use some of the more advanced features.
If you would prefer to have our team handled it, we also can implement these services via our Premium Support services. You can find out more and/or pick up Premium Support hours at http://www.datasprings.com/PremiumSupport.
Quick Update (01/25/2012): Our module currently requires the web.config setting “EnableEventValidation” to be set to “False” within your web.config file:
Well it looks like it has changed recently but it sounds like you can enable the feature again based on this setting:
http://www.dotnetnuke.com/Resources/Wiki/loc/print/Page/Event-validation.aspx
So you might at least modify this setting to determine if it then works… I honestly don’t think the security setting mentioned would affect most typical sites but if we can review ways of allowing the feature without having this setting enabled then we will try to do that.
Basically here is what you need to do:
1. Go to Host, Manage Configuration
2. Edit the Web.Config File
3. Search for the phrase “EnableEventValidation”
4. Change the value of this setting from “True” to “False”
Thanks!
-Chad