Thomas,
I used the Web Component | Included Page option, and navigated to the appropriate file (e.g.
header_nav.htm) via the browse option offered by FP 03. I tried this with the DWT files in a
subfolder (with brilliant imagination, I named this folder \dwt) and with the include pages in
that folder as well. The result looked fine on my PC, but when published, the included page with
the header graphic did not show up -- just an empty box.
I believe my next try was with the DWT files in their own folder, and the include pages in the
root, and my recollection is that this did not work either.
When I moved the DWT files to the root, along with everything else, it worked fine. Not as tidy,
but functional.
Did FP have a problem because both the DWT and include files were together in one folder, but
the pages to which the DWT files were applied were in another? Did the same-folder location of
the DWTs and "includes" mean there was insufficient information in the relative links for use of
the DWTs on files away from that location?
Sorry for the entry-level questions. As noted earlier, I am new to DWTs.
Alex
If using the FP Include Page component, all links to the page to be included must be relative,
and if you want FP to manage any of the link on the pages being included, they must be also be
relative.
Examples
href ="../pagename.htm"
or
href ="../foldername/pagename.htm"
or
href ="pagename.htm"
or
href ="foldername/pagename.htm"
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
Ron,
I think you hit it. I tend to use a lot of "include" pages (for headers, nav bars, etc.) to
keep the DWT itself simple. I will try using absolute or root-relative links.
Thanks,
Alex
I have my DWTs in their own folder, use graphics and FrontPage include files
in the DWT, and have never seen that problem.
However, if you are using ASP or SSI includes, then the path to the include
will not be updated, since it is inside an HTML comment. Similarly, any
links that are made using JavaScript[1] will also not be corrected -
FrontPage does not manage scripted links. In both these cases consider
using absolute links or root relative links instead of relative links.
[1] The exception to this rule is when the JavaScript is inserted as a
result of a FrontPage behaviour - the links are (usually) adjusted in this
case.
--
Ron Symonds
Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
I'm early on the learning curve for using DWTs in FP 2003. To keep the
site
easy to manage, I'd planned to put index.htm and other top-level files in
the root folder of the website, with other stuff in sub-folders. It seemed
logical to me that the Dynamic Web Templates for the site should be in
their
own folder as well. Yet when I attempted to build the site this way,
several
pages were "broken" -- a graphic in the header would not show up in the
published pages, for example, or an "include" page would not work. After I
moved the DWT files to the top or root level of the web, everything worked
fine.
Am I missing something, or does FP 2003 not "like" having DWTs anywhere
but
in the root folder of the website?
Alex