Article #1097
Subject: Moving an Xpress core? Persistent login page.
Author: Mark O'Neil
Posted: 3/23/2001 07:45:16 AM

I am working with the enCore/Xpress core here.

I have an experimental server/core(A) which is serving its own Xpress core
fine.

I have moved a 'production' core(B) from another machine which is not using
the Xpress bits (no web-server installed).

When I start the production core(B) I set the configure bits to match those
of core(A). I then kill it's process and restart the server using core(B).

I can connect and login on core(B) only with Moose/telnet clients - the
Xpress interface merely kicks back the login page.

I am apparently getting authenticated as I am being sent a cookie with the
appropriate player number.

It was suggested that perhaps there was a date conflict. My Mac and the
server match within seconds for the time and have the same date setting.

I have created a new player on core(B) and set its parent to be $player (so
the Xpress props are there) to no avail still no Xpress success.

Any suggestions?

-m

Article #1098
Subject: Re: Moving an Xpress core? Persistent login page.
Author: Mark O'Neil
Posted: 3/23/2001 10:44:38 AM

on 3/23/01 8:45 AM, Mark O'Neil at Mark.A.ONeil@nospam wrote:

> I am working with the enCore/Xpress core here.
..
> Any suggestions?
>
> -m
>

Heh heh silly me, the name was DartMOO(cobweb) and the ()'s were choking the
openXpress() javascript....

So problem solved.

Too long since I have fiddled with javascript I guess....

-m