Archive of UserLand's first discussion group, started October 5, 1998.
Re: Staging Server
Author: Brent Simmons Posted: 1/13/1999; 12:48:34 PM Topic: Staging Server Msg #: 2102 (In response to 2101) Prev/Next: 2101 / 2103
I suspect you're changing your #fileExtension preference. You don't need to do this -- .wsf will work via the website framework responder even if #fileExtension is set to .html or whatever.
In other words, your glossary entries should respect your #fileExtension pref, even when running as .wsf pages, so your glossary entries shouldn't be changed. The glossary lookup mechanism (html.refGlossary) automatically substitutes .wsf as needed in its output, it doesn't touch the actual glossary.
If I'm wrong about what's going on here, let me know. The place to trap the problem is in html.addPageToGlossary: look at the end of the script, where it gets the file extension and adds it to glossary entry.
There are responses to this message:
- Re: Staging Server, Alan German, 1/13/1999; 1:29:51 PM
- RFC: New attribute for glossary entries, Jim Roepcke, 1/13/1999; 1:47:39 PM
This page was archived on 6/13/2001; 4:47:16 PM.
© Copyright 1998-2001 UserLand Software, Inc.