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/3/2006 3:35 PM
 

Hi flyerstarter,

I was having the same problem as you were, it turned out for me to be the isapi settings.  I would suggest a few things..

1)  Make sure all .net related mappings for your particular site (not just the root site) are pointing to the proper framework isapi dll.  Even though my root web site was pointing to 2.0, my actual dnn site was using the 1.1 framework for some reason  My thread is below

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

2)  If that doesn't help, I would download Fiddler at the URL below (its a MS product), run it while you request your page and then look through the log and see if you notice anything wrong (anything in red would be a problem)  From there you can hopefulyl try to see what the root problem is)

https://www.fiddlertool.com/fiddler/

 
New Post
8/3/2006 4:21 PM
 
STOP THE PRESS!

I was trying to see if Fiddler would deliver some errors, but no. Naturally, being MS, Fiddler seems to only want to debug Internet Explorer.

In the course of my test, I press 'Update' in IE. Guess what: it's fine. The form submits. IT'S A BROWSER ISSUE ARGGGGH.

I have been using the latest Firefox: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 on my desktop to do the dev work. It will not 'Update' from my desktop.

I Remote Desktopped into the server, and tried the Firefox from there, version 1.0.7, and it's fine: the form submits.

Can someone else confirm that the Site Settings form works ok in the latest Firefox? I have noticed the quality of FF has been going down lately, lost bookmarks, weird bugs, maybe it's this, or maybe my install is just jacked?

 
New Post
8/3/2006 10:41 PM
 
If you're running Windows 2003, each site you setup can be configured to use a different framework version and each .NET 2.0 Framework version can be setup to allow .axd or not. 

Excluding the "compression" software you were using, I'd go and compare the mappings again on each site.

Or, how about setting up a whole new web site in the IIS console, installing DNN 4.3.3 on that, and allow .axd and see if a new web site works.

Another possible troubleshooting step is to see if trace.axd works after you enable it in the web.config for the dnn site.  Add the following xml after the <system.web> node:

    <!--  APPLICATION-LEVEL TRACE LOGGING
          Application-level tracing enables trace log output for every page within an application.
          Set trace enabled="true" to enable application trace logging.  If pageOutput="true", the
          trace information will be displayed at the bottom of each page.  Otherwise, you can view the
          application trace log by browsing the "trace.axd" page from your web application
          root.
    -->
    <trace enabled="true" requestLimit="10" pageOutput="true" traceMode="SortByTime" localOnly="false" />

If pageOutput="false", you will need to access trace.axd by adding it the url, e.g. http://localhost/dnn/trace.axd

Assuming .axd is enabled for that site, you should see the trace output at the bottom of the page.

If that works, I'd guess that there is some other issue besides enabling .axd for the site.

 
New Post
8/9/2006 3:02 PM
 

Hey, my solutions was the .axd mapping.

I have my DNN install pointing to a virtual directory (which points to my DNN install).

I went to the default website properites and checked the .dll mapping and the .axd extesion was in there and mapped to the .NET 2.0 Aspnet_isapi.dll file. 

But when I went to my virutal directory and went to properties . . there was no .axd mapping ??

I then added the .axd mapping and  . . stopped and restarted IIS  . . recycled the application pool and it worked.

No more Javascript errors.

SOOOO . . check your virtual directories and/or separate applications for .dll mapping.

This got mine working.

 
New Post
12/5/2006 6:20 PM
 

Hi All,

I would request core team to help me on this. I created a DNN site and it works fine until I enable windows authentication. Once it is enabled, I am not able to user UPDATE buttons as it give javascript error. I ran fiddler and it shows me error 500 for webresource.axd. The stack trace is -

NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Security.Authentication.Configuration.GetConfig() +16
   DotNetNuke.HttpModules.AuthenticationModule.OnAuthenticateRequest(Object s, EventArgs e) +25
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

It seems like window authetication is stopping webresource.axd to down to temporary files. I don't know how to solve this and would appreciate your help ASAP.

Cheers,

Sanjay

 

 
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