I updated our site to DNN 5.6.3 last night, and it seems this has broken the Active Social Login. It's giving an "Object reference not set to an instance of an object"

If I remove the Active Social Login module and make the standard DNN login control visible, it works fine. I can't see an obvious workaround to make the AS login module work again. The rest of the site seems to be working fine.

Here's the relevant log entry;

AssemblyVersion: 5.6.3
PortalID: 0
PortalName: AuTechHeads
UserID: 6
UserName: AuTechHeads
ActiveTabID: 102
ActiveTabName: Social Login
RawURL: /social-login
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.autechheads.com/social-login
UserAgent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: f5212957-8efb-4bb2-8090-ed7c2e90d16d
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.Util.StringUtil.GetStringHashCode
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at System.Web.Util.StringUtil.GetStringHashCode(String s) at System.Web.UI.ClientScriptManager.EnsureEventValidationFieldLoaded() at System.Web.UI.ClientScriptManager.ValidateEvent(String uniqueId, String argument) at System.Web.UI.WebControls.RadioButtonList.LoadPostData(String postDataKey, NameValueCollection postCollection) at System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: ALANWEB

Found another instance of this, when trying to save a change to my Forum Signature within my Active Social profile.

Could be the update to the Telerik controls?

I am getting this error on AS pages :

Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
Please contact the website owners to inform them of this problem.

Also, noticed that all summary activity has disappeared!

Also manifests with uploading a new profile picture.

Just tested these three things with a brand new site running DNN 5.6.3, AS 1.9.3 AF 4.3.5 and I did not get any errors.

Can I suggest that you test against an upgrade rather than a brand new site? There is already at least one blog post on the DNN site relating to issues with the 5.6.3 upgrade package. Equally, this was the only change made, and previous DNN upgrades have not had the same issues.

I'm trying to think of things that may be different between your site and my default configuration. Do you have any other modules on the same page as the login module? Have you customized it at all?

Cross-post. Yeah I'll test that now.

No worries. I'll also send you the host login for you guys so you can take a look.

No errors on the 5.6.2 > 5.6.3 upgraded site either. I got the host info, so I'll check that out in a sec.

No worries. I only get issues within Active Social instances, all the others are working fine. I got around the worst of it by switching back to the standard DNN login for now.

Off to bed for the night, nearly 1am here :-)

I just did DNN 5.6.3 upgrade without issue. I haven't done complete regression testing, but so far I am not seeing any abnormalities. Will let you know if I do have issues.

Ben,

Any luck with this? Still only the Active Social functionality broken. Is it worth Will taking a look?

Cheers,

Matt

Ok. I have tried a suggestion from http://social.msdn.microsoft.com/Fo...7c8ca2981c

By setting enableEventValidation="false" in web.config, I am able to reinstate the Active Social login, and I can test the other cases successfully.

Naturally I do not want this as a permanent solution. It is clear that there is some kind of issue between DNN 5.6.3 and ActiveSocial with this event validation. It may be that this is not occurring in your tests because I use ActiveSocial controls as skin objects, or something similar, but of course I'm clear on this being with ActiveSocial since it occurs only within AS module instances.

I suspect the best way forward is to ask Will to take a look as I'm sure he would be able to find and fix the exception condtion, or if it's an issue with DNN that needs correction, push the issue forward to get that updated too.

Cheers,

Matt

From what I've read, in 5.6.3 Event Validation has been enabled by default. Seems Module vendors will have to update their code. In the meantime, we'll have to set it to false in the web.config as Matt has done.

http://www.dotnetnuke.com/Resources...eased.aspx

Ben and I have done a lot of testing this week and still can't reproduce the problem. Also, we have been testing and working with our modules every day over the past months in DNN 6, which has had event validation enabled by default. It is possible there is a conflict on the page some where that is causing event validation to fail, but we haven't found it yet.

Actually, the error points to a radio button list that is causing the problem. We don't use radio button lists.

No radio button lists on the pages in question, either :-S

That said, I accept that it must be something site-specific. It's just that the login page in particular is very minimalistic in what it has enabled. Perhaps it could be an interaction with fatgeorge Who's Online :-|

Appreciate the confirmation that it's a change in 5.6.3, Jeff.

Also, thanks for the reply Will :-)