01:40:56 PM
3I30TBSF0
It kind of sounds like the you have maybe the .wc extension set up for the module and your app scriptmap set to the ISAPI extension? It's possible the .wc extension is not mapped properly.
FWIW, re: changes to admin page - I'm making those changes now.
There will also be changes in the new version that default to using the .NET module for new applications to simplify configuration making script map configuration much easier and less error prone.
So I'm curious to hear what might be causing your problem...
+++ Rick ---
Bummer. I just tried EditConfig and it has the same error. In fact, the only link that does work is the Show and Manage ISAPI Settings.
The app works without any problems.
~bob
Bob,
That request is no longer valid. There are a number of issues with this but mainly since we've removed wwDhtmlForm from Web Connection this request is no longer used. If you need to edit settings the only way to do it now is to edit through the EditConfig link.
I may add this back in in the future using a standard Web Connection form, but for the moment that feature is gone.
Still not sure why that wouldn't work though - the .config parsing should work just fine... Does the app otherwise run - which indicates that the Web.config file is valid.
+++ Rick ---
After I upgraded to v5.62, wwMaint no longer works. Perhaps it was some other change I made at the same time, but I am unable to track it down. This is the error message.
Processing Error - wwMaint~ServerStatus
Error: 1943
Message: Member DOCUMENTELEMENT does not evaluate to an object.
Code: loNode = loXml.documentElement.selectSingleNode(lcSection + "/add[@key='" + lcKey + "']")
Program: getwcinivalue
Line No: 885
Debug shows:
lcSection = WebConnectionConfiguration
lcKey = AdminPage
Here is the line in Web.Config:
<add key="AdminPage" value="/admin/Admin.asp" />
That file does exist.
~bob
West Wind Technologies
Making waves on the Web
from Maui, Hawaii
