On 5/31/02, John VanDyk said:
>Error: Can't evaluate the expression because the name "adrObjectToServe"
>hasn't been defined. Time: Fri, 31 May 2002 19:44:08 GMT
>Please report this error to the Webmaster. ["Hard
>Since I chose the "more compatible" installation of Conversant (i.e., I
>also want to run Manila) shouldn't the Conversant responder just be
>getting out of the way?
>I can fix this temporarily and use Manila by changing the IP address at
>ConversantData.hosts but obviously that's not a solution.
The available options for the responder were to make Conversant's the
default, use Conversant's "smart" responder (which is actually just a
smart responder condition), or turn off Conversant's responder and use
Which option did you choose: the second, or the third?
The smart responder looks for a match in ConversantData.hosts, so that
you can have one (or more) hosts which are served by Conversant (a host
can be an ip address, a real host name, or a combination of a either of
those two with a specific port number like 127.0.0.1:81).
You can serve Conversant entirely via MainResponder if you want to by
choosing "Off" in the responder section of the installer. If that's what
you want to do then just delete Conversant's responder from the table at
user.webserver.responders. You'll also have to set something up in
Config.mainresponder.domains, but how you do that depends on whether
you're already using a sitetree or if you just want to assign a host name
(or multiple host names) to Conversant.
I hope that helps...