Am I to understand that when Tourweaver outputs a tour published for the web, that the format and subdirectories are not directly usable? I tried publishing directly to a subdirectory on the website, and I also tried saving it locally and uploading the structure via FTP. Either way, the tours do not work. Usually nothing happens. Sometimes I can get it to come up. But either way, customers aren't able to bring it up.

HELP? I was looking at the other posts, but I wanted to get clarificaiton on this first: Should it work as published?

You should keep all files generated by TW in on file and link to the tw.html. TW's output is designed to asct as an html page. If ur tours do not work then u should do the above, ensure that u have no non english letters in ur file names and ensure that u have no spaces in file names eg kitchen picuture.jp is wrong kitchenpicture.jpg is correct.

If u want, I'll send u a tour including the vtp file for u to look at.

Phoenix if it is at all possible could I have that too?

Im using netobjects fusion and Im new to web design. My tours arent designed for the web but it would be useful to have the knowledge.

Many thanks

forresthowie@aol.com

I still can't get it to work right with TW 1.3. I just made a mockup, safed it local and uploaded everything just as TW generated it to my website at: www.klamath.net/wr

I had saved the file as index, so it should come up. The automatically generated splash page comes up, but the index link seems to upen up aother window, but the skin and tour does not show up.

I can send anyone the whole thing for analysis, because I can't determine what I did wrong, if anything. I've had other people try to open it and they can't either.

I always use DOS file naming conventions and there are no non-ascii characters. I left all structures exactly as they came out of TW. Has anyone else had these problems with 1.3?

I tested your link with Internet Explorer 6.0 and Microsoft JVM and loaded and worked AOK.

You have used the chromeless window option which is useless and will only cause problems. You do not have to use both windows if you like you can just use the window that the tour is on. Look up it's name and then either use it as the initial link or rename that page to whatever it is you would like it called.

You should when requesting people to help you with testing/viewing your tours get them to tell you what browser and what version of java they are using to help diagnose your issue.

Regards, Smooth

STILL PROBLEMS

Today the previous link won't work. This happens more often than not. Using Explorer 6.0. Cant' get it to open in AOL either. It seems to create a window for the tour but doesn't follow through with running it. There is buton on the windows bar at the bottom of the screen for it, but clicking on it won't oepn it up.

I also tried copying the default tour link code into a new page and that seems to have a different problem. Just get a page error. This is a new page with tourweaver's default code: www.klamath.net/wr/tour.htm

Why doesn't this one work? Is there a reference somewhere for the anatomy of the link syntax? I couldn't find anything of the sort in Easypano's TW help file. I want to know exactly what that link code requires and in what syntax. For example, I'd like to configure it to start the tour in the existing window, not a new one. There are probably a lot of people out there with popup blockers who's system blocks the tour window from popping up. It is not realistic to ask them all to turn off their software in order to view the tour.

The lack of information on something that should be simple like a tourlink is very frustrating.

I just got the page error message to go away by copying the corresponding javascript header code from their default output into the new page. See the before and after:

www.klamath.net/wr/tour.htm

After:

www.klamath.net/wr/tour2.htm

Which brings up a couple of questions:

1) How are people getting links to work? Are they modifying the sample page, or is everyone else copying the javascript like I just did?

2) Why doesn't the TW sample page output say anything about needing the javascript code? It gives instructions for using a default link that do not work!

ARGH!!!