|
|
 Posted 25/09/2004 10:06:50 |
|
|
Forum Newbie
Group: Forum Members
Last Login: 27/07/2005 18:54:29
Posts: 7,
Visits: 6
|
|
|
|
|
 Posted 27/09/2004 06:06:28 |
|
|
IF.NET 4.2 Coming Soon
Group: Administrators
Last Login: 2 days ago @ 14:57:33
Posts: 1,949,
Visits: 3,002
|
|
Hi, I've seen this problem a few times before. Could you open controls/logon.ascx and determine if the following lines appear within the page directive. AutoEventWireUp="False". If this text appears you will need to remove this or change this to read AutoEventWireUp="True". Visual Studio.NET can something add this to the control and page directives when including a folder within an existing solution. Please let me know if this helps 
Kindest Regards,
Ryan Healey
Director / Developer
 Explore our products...
http://demos.instantasp.co.uk/
|
|
|
|
| Posted 12/10/2004 06:40:37 |
|
|
Forum Newbie
Group: Customers
Last Login: 18/02/2005 11:48:00
Posts: 1,
Visits: 1
|
|
I had the same problem: Buttons didn't work... no postback. Here's what I did to fix it: At a command prompt:
>cd \WINDOWS\Microsoft.NET\Framework\v1.1.4322
>aspnet_regiis -ea
>aspnet_regiis -c These commands delete, then recreate the aspnet_client folders needed for asp.net postback. Hope this helps, Jon Wolthuis
President
Ascend Systems Inc
|
|
|
|
| Posted 05/04/2005 08:47:37 |
|
|
Forum Newbie
Group: Customers
Last Login: 15/10/2005 17:55:49
Posts: 10,
Visits: 8
|
|
Hello, I'm having the same problem, but I've tried both solutions to no avail. Do anyone know of anything else to try? Why does this happen? Thanks.
- Kylir Horton
 - Web & Graphic Designer
- Azteca Systems || www.azteca.com
|
|
|
|
| Posted 28/04/2005 14:40:29 |
|
|
Support Supremo
Group: Customers
Last Login: 19/08/2008 19:01:11
Posts: 568,
Visits: 2,503
|
|
|
|
|
| Posted 13/01/2006 07:28:48 |
|
|
Forum Newbie
Group: Forum Members
Last Login: 26/06/2006 13:27:25
Posts: 4,
Visits: 9
|
|
For what it's worth, Im having the same issue now. I know that the last update I made was to the web.config, and that the login buttons work on some PC's... but not all. And it seems that the buttons do work on Firefox... so apparently they have the .NET framework down better than Micro$oft  I hope this helps, and if anyone comes across an answer to this, please post... Im going nuts over it.
|
|
|
|
| Posted 13/01/2006 12:43:12 |
|
|
Forum Newbie
Group: Forum Members
Last Login: 26/06/2006 13:27:25
Posts: 4,
Visits: 9
|
|
| Hi Everyone, some folks at work and I were able to resolve this issue. Didnt make much sense since we didnt update the problem file, in fact, we never touched it! We found that the "WebUIValidation.js" file wasn't running correctly. What was really aggrevating was that our localhost version WAS working, but staging and production didnt. The Solution:
What we did was compare our WebUIValidation.js files in development to staging/production, and found that there were some lines 'missing'. I can only assume that they are the same lines that may be missing in your files, but irregardless, here's what we had in production:
LINE 125
function ValidatorCommonOnSubmit() {
event.returnValue = !Page_BlockSubmit;
Page_BlockSubmit = false;
}
We looked in our development .js file and found the following:LINE 125
function ValidatorCommonOnSubmit() {
var result = !Page_BlockSubmit;
Page_BlockSubmit = false;
event.returnValue = result;
return result;
}
So, we added the last 2 lines to the function, ran it, and voila! Hope this helps...
|
|
|
|