publishing problem (one host OK, the other not)

[Mike Jacoubowsky]

I've finally started to maintain my website locally (on my laptop, running
IIs) and publishing to the ISP as the remote. Except that something screwy
is going on with the formatting. Here's the goofed-up page (check out the
bottom) at

www.ChainReaction.com/diary.htm

That's using XO Communications for a webhost. Front Page extensions in
place.

But publishing the exact same file to LunaPages at-

www.ChainReactionPhotos.com/diary.htm

And everything comes out just fine. Any ideas what might be going on?

Thanks-

PS: And yes, it's entirely likely that I'll just move everything over to
Lunar Pages in the near future. This isn't the first time I've had issues
with XO, just the weirdest. I really thought the problem was at my end,
until I tried to Lunar and it worked just fine.

--Mike Jacoubowsky
Chain Reaction Bicycles
www.ChainReaction.com
Redwood City & Los Altos, CA USA

 

[MD Websunlimited]

Hi Mike,

I believe this is caused because the first does not have all the SP packages installed. Contact the host and ask them what version
of the FPSE they are running.

 

[Mike Jacoubowsky]

I've finally started to maintain my website locally (on my laptop,

Hi Mike,

I believe this is caused because the first does not have all the SP
packages installed. Contact the host and ask them what version of the FPSE
they are running.

Mike: Thanks for the idea; of course, XO says nothing of the sort is true.
In fact, they kept insisting that there was no way the issue was at there
end, because there was no way there server could be producing the "extra"
code found on the faulty page. Eventually it got through to them that I was
publishing the *identical* file to two different servers/ISPs, one of which
was handling it just fine, the other (them) choking on it.

I have definitely found the part of the file that's messing things up for
them; it's this included page- www.ChainReaction.com/menuwide.htm. There's
something in that code they're having real trouble with; I'll try to
simplify things until I get to the absolute-minimum code that causes the
issue. Of course, the guy I was talking to told me "That's why I hand-code
everything." Gee, thanks! But my job is running a bike shop, not knowing (or
even having the time to) how to do everything by hand.

Interestingly enough, the drop-down boxes (produced by a WebsUnlimited
product!) are so far the minimal code required to cause the problem.

--Mike-- Chain Reaction Bicycles
www.ChainReactionBicycles.com