Post/Cancel Click Does Nothing

Topics: User Forum
May 18, 2006 at 6:13 PM
I'm having a strange issue with the new topic page. Clicking 'Post' and 'Cancel' has no effect. It doesn't cause a postback. I'm not getting a javascript error, either. This occurs from two different machines, so I don't think it's a browser setting.

Anyone else seen this? Any ideas what it could be or how to even debug it?
May 18, 2006 at 6:19 PM
It works for me. I have added about 20 topics without any errors what so ever.
Coordinator
May 18, 2006 at 6:29 PM
Sounds a little strange. If there was a javascript error, I could understand it might doing something wrong but not sure what this might be. I haven't heard anyone else report it and not sure how I could reproduce it but I'll look into it and see what I can do (maybe provide you with a build with extra logging turned on so we can see what's happening).
May 18, 2006 at 8:22 PM
Ok, here's another possible symptom. Immediately after uploading and adding the web part to a site, I get the SharePoint 'webpart error' page with the link to the 'Web Part Maintenance' page. When I return to the home page, the Forums web part is there and functional (except for the post\cancel problem). Could this be related somehow?
Coordinator
May 18, 2006 at 8:29 PM
This sometimes happens with portal areas or WSS sites, but should only happen once. After that everything should be fine.
May 18, 2006 at 9:19 PM
Ok, still trying. :)

I did figure out that the submit works fine on the admin config page used to change the forums title. I assume it uses a different postback mechanism than the post\cancel links.

Are there any other pages that use a javascript-based href hyperlink to do the postback?
Coordinator
May 18, 2006 at 9:24 PM
Everything uses the same postback (it's ASP.NET, nothing special). The only thing might be state and redirection which it does differently, depending on the context. Need to take a look at it later tonight still or over the weekend. Thanks.
May 22, 2006 at 5:37 PM
Any thoughts on this? Ideas for debugging? What would cause a hyperlink to fail with no javascript error?
May 22, 2006 at 7:26 PM
Could someone with a working deployment open the raw 'New Topic' page html (Right-click->View Source) and post the hyperlink rendered by ASP.NET?

Mine looks like this:
<a class="" href="javascript:ProcessOwsForm('Left$g978f1827ecb340348a08_40e4d212d2eb$ctl00$btnPost', 'Click');" >Post</a>

This is driving me crazy -- I don't understand why it just doesn't do anything. I'd expect at the very least to get a javascript error.
May 23, 2006 at 6:17 PM
Hi Spoons,

Are you sure you are not getting a JavaScript error anyway? Check the lower-left corner of the screen for a yellow triangle and click it to raise the error thrown.

My URL looks reasonably similar to yours. I am not sure you posted it correctly, though. I don't see any dollar signs in my URL.

The HREF portion of the hyperlink should read "javascript:ProcessOwsForm('Left:g underscore the GUID of your List which may contain some underscores : underscore ctl0:btnPost','Click');"

Michelle
May 24, 2006 at 2:15 PM
Ok, now we are getting somewhere. Yes, I've turned on everything to notify me about JavaScript errors - I get nothing.

When trying to search to see if maybe this was a general ASP.NET or SharePoint problem, it seems like I remember coming across a post somewhere that talked about having dollar signs instead of underscores in the postback string. Maybe had something to do with the location of the <form> tag? Now if I can just find it again.
May 24, 2006 at 2:31 PM
I found something interesting here:
http://support.microsoft.com/kb/817779/

Sounds similar. The only thing is, we are running WSS SP2 with .Net 2.0.

I assume I'm not the only one trying to run Bil's web part using this configuration?
Coordinator
May 24, 2006 at 2:43 PM
I haven't tested it running on WSS v2 with ASP.NET 2.0 so it might have some problems.
May 31, 2006 at 1:06 PM
Any ETA on the code? I'd be more than happy to debug\test the forums with this configuration.
Coordinator
May 31, 2006 at 9:45 PM
I'm just getting through the woes of trying to check code in via team explorer (or some other means) without having to convert the project to a 2005 one. There's very little documentation and/or the process is painful. By the looks of the command line tool I have to check each file in separately but I think I can write a NAnt build file to do it. Just need to get it done (hopefully this weekend if I can).
Jun 8, 2006 at 3:05 PM
"I haven't heard anyone else report it and not sure how I could reproduce it but I'll look into it and see what I can do (maybe provide you with a build with extra logging turned on so we can see what's happening)."

Is this still an option? Is the web part buildable in VS.NET 2005? I'd be interested to see if an ASP.NET 2.0 build does the same thing since that's the configuration I have.
Jul 5, 2006 at 5:04 PM
FYI, 1.1.0.0 exhibits this same behavior for WSS 2.0 on ASP.NET 2.0.
Coordinator
Jul 5, 2006 at 5:06 PM
As I wrote somewhere, the web part does not support ASP.NET 2.0 (in any capacity, WSS v2 or v3) at the moment.

While I did compile it under VS2005 at TechEd for a demo of it running on MOSS 2007, I noticed the postbacks did not work so it's probably the same problem.

Until the August release, you won't be able to run the web part on a WSS site running ASP.NET 2.0.
Jan 14, 2009 at 5:15 PM
Edited Jan 14, 2009 at 5:16 PM
Hi,

I am getting the exact same problem running MOSS 2007 and ASP.NET 3.5... Any ideas? If I removed ASP.NET 3.5, and used only 3.0 would this make a difference?
Thanks for your time!