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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...'Site Settings' Update in 4.3.3 won't submit
Previous
 
Next
New Post
8/2/2006 6:34 PM
 
I found an answer to your problem with ASP.NET.  Well, a co-worker of mine found it actually. 

.NET 2.0 Framework sites use WebResource.axd to enable posting from page to page without all the issues presented in the 1.0 and 1.1 Framework.  The javascript it inserts does not work because the WebResource.axd .axd is not mapped for ASP.NET 2.0 (something like that).  This replaces the aspnet_client folder, too.  So. 2.0 sites should not have that folder.
 
This gets embedded at the top of the page sent to the user's browser:
 
<script src="/WebResource.axd?d=Nt3Z42KfPOraV6JTUYmd0Q2&amp;t=632900403625890082" type="text/javascript"></script>
but, this code does not exist until the mapping is created--WebResource.axd did not work correctly:
Clicking Register or other buttons on site attempts to submit this; WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions(&quot;dnn:ctr:ManageUsers:User:dshPassword:imgIcon&quot;, &quot;&quot;, true, &quot;&quot;, &quot;&quot;, false, false))"
The mapping for .axd has to be added to the .NET Framework 2.0 aspnet_isapi.dll for the web application ... uncheck verify that file exists because it's not a real file.
 
  • In the Properties for the web site, select Home Directory tab, click Configuration...
  • On the Mappings tab in the Application Configuration dialog, click Add...
  • Navigate to and select:
  • C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
  • Limit verbs to: GET, HEAD, POST
  • Uncheck verify that file exists
  • Click OK

See Cross Page Posting section
http://msdn.microsoft.com/msdnmag/issues/05/09/CuttingEdge/
 
Cross-Page Posting

ASP.NET 2.0 offers a new built-in mechanism to override the normal processing cycle and to allow a page to post back to another page. In general, postbacks occur in one of two ways: through a Submit button or through a script. Submissions through a button typically point automatically to the address that the posting form indicates. More flexibility is possible when the post occurs through a script. In ASP.NET 2.0, you can configure certain page controls—in particular, those that implement the new IButtonControl interface—to post to a different target page. This is referred to as cross-page posting.

 
 
New Post
8/3/2006 11:46 AM
 

I had the same problem but a different solution (problems with .net 1.1)  You can see my thread here

http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/118/threadid/59032/threadpage/2/scope/posts/Default.aspx

 
New Post
8/3/2006 1:49 PM
 
I am giving this a shot, sounds like the best explanation yet. One thing missing from your steps, I believe; the dialog has an input for the Extension. If left blank, an error notice pops up upon pressing 'OK'.

I'm taking a wild guess that this input should be '.AXD', is this correct?

  • In the Properties for the web site, select Home Directory tab, click Configuration...
  • On the Mappings tab in the Application Configuration dialog, click Add...
  • Navigate to and select:
  • C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
  • Limit verbs to: GET, HEAD, POST
  • Uncheck verify that file exists
  • Click OK
 
New Post
8/3/2006 1:55 PM
 

 

Yes, the extension should be .axd


DotNetNuke Modules from Snapsis.com
 
New Post
8/3/2006 1:58 PM
 
I added "Extension: AXD" to the instructions.  

I found an answer to your problem with ASP.NET.  Well, a co-worker of mine found it actually. 

.NET 2.0 Framework sites use WebResource.axd to enable posting from page to page without all the issues presented in the 1.0 and 1.1 Framework.  The javascript it inserts does not work because the WebResource.axd .axd is not mapped for ASP.NET 2.0 (something like that).  This replaces the aspnet_client folder, too.  So. 2.0 sites should not have that folder.
 
This gets embedded at the top of the page sent to the user's browser:
 
src="/WebResource.axd?d=Nt3Z42KfPOraV6JTUYmd0Q2&t=632900403625890082" type="text/javascript">script>
but, this code does not exist until the mapping is created--WebResource.axd did not work correctly:

Clicking Register or other buttons on site attempts to submit this; WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("dnn:ctr:ManageUsers:User:dshPassword:imgIcon", "", true, "", "", false, false))"

The mapping for .axd has to be added to the .NET Framework 2.0 aspnet_isapi.dll for the web application ... uncheck verify that file exists because it's not a real file.

 

  • In the Properties for the web site, select Home Directory tab, click Configuration...
  • On the Mappings tab in the Application Configuration dialog, click Add...
  • Navigate to and select:
  • C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
  • Extension: axd
  • Limit verbs to: GET, HEAD, POST
  • Uncheck verify that file exists
  • Click OK

See Cross Page Posting section
http://msdn.microsoft.com/msdnmag/issues/05/09/CuttingEdge/
 
Cross-Page Posting

ASP.NET 2.0 offers a new built-in mechanism to override the normal processing cycle and to allow a page to post back to another page. In general, postbacks occur in one of two ways: through a Submit button or through a script. Submissions through a button typically point automatically to the address that the posting form indicates. More flexibility is possible when the post occurs through a script. In ASP.NET 2.0, you can configure certain page controls—in particular, those that implement the new IButtonControl interface—to post to a different target page. This is referred to as cross-page posting.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...'Site Settings' Update in 4.3.3 won't submit


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