Broken relative links after upgrade to FMU and WSC

[seanc]

Hi All,

After upgrading from FMP to FMU and now using the WSC, I have found one minor problem I don't quite understand.

My web site consists of a few pages in the root level folder, and there is also a folder inside that which contains images for use as buttons. My pages use relative linking to call the objects inside these foldes. eg. <IMG SRC="images/clearspacer.gif">

All worked (and still works) perfectly while I was using NAT to access the databases, but if I use the WSC, none of the images load.

Can anyone help me fix this? I realise I could move all the images or stop use relative links, but I don't think either of those is the best answer.

Possibly I have the WSC setup incorrectly, or IIS. In order to see the instant web publishing page I have to type in http://mydomain.com/FMPro?

Cheers,

Sean.

PS. I've just been re-reading the docs, and I guess this behavior is by design.

"store static elements such as image files on the web server, and bypass the Filemaker Pro Web Companion for pages that do not need to intereact with the database."

I guess I do need to move all that stuff after all...

[Steve T.]

Hi! I'm not familiar w/WSC yet and this may not apply exactly to your situation but I thought I'd mention it anyways...

Relative links are kinda tricky sometimes. It took us a while to figure them out when we published multiple db's in various subfolders of the root Web folder. In FMP 4.x, we could only specify host (no directory) but in FMP 5+ you can specify directory.

<FORM ACTION="http://mydomain.com/FMPro"

<FORM ACTION="http://mydomain.com/subfolder/FMPro"

The relative links would be based on the FORM line we used. It got confusing because we used both kinds. Stealing code from our other projects didn't work right and we didn't know why. Over all, the 2nd is better.

[seanc]

Hi sktajiri,

I've never had problems with the relative links before, but I do understand what you mean. I have always specified the subfolders.

In any case, I moved the images onto my IIS machine and they work fine again. Seems a little perverse to have the website split over 2 different machines, but I guess in the interests of max speed I can deal with it. It seems I need to have a virtual directory on the IIS machine with the same name as the folder in the web directory.

Funny setup, but it is working.

Now if I can work out how to make a machine with WSC stable I'll be happy. I've had it running on 3 different machines and it always seems to introduce new levels of flakiness. The blue screen of death strikes again... Doesn't seem to like W2K Server.

Cheers,

Sean

[Anatoli]

Try NT4.

IMHO -- much better stability for IIS and WSC.

Our last reboot was on 25th of May

[seanc]

Hmmm. I could do tha, but it would be a last resort. I'm not a big fan of NT4 (it was fine in its day, but seriosly long in the tooth now, and so many things it just can't do).

Further, it would mean yet another machine added into the equation, because I'm not going to ditch my active directory, domain controller or exchange server 2000. Possibly exchange server (and particularly OWA) is giving the WSC a hard time. I already have 3 machines running as servers for a fairly small (at this point) business, and I'm not keen to put in another unless its really necessary.

I think rather than doing that, I'd prefer to ditch WSC and access my filemaker web content directly using NAT instead. It may be marginally slower, but until my site gets a whole lot busier I don't think that would matter.

By the way, is there any real difference or improvement in WSC6 over WSC5? Maybe they've fixed this flakiness...

I noticed you asked this question Anatoli back on the May 31st using somewhat colorful language, and never got an answer... Did you sort your issues out back then?

Cheers,

Sean.

[Anatoli]

IMHO -- if you will use NT just for FM/WSC outside of your network, it will be fine.

FM never replied to any criticism or question from me They are not interested...