Links in Related Links

Hi,
I've moved Navigation Panel from left to content area, now i got a problem when i click the link in related links i am getting two windows for that same link, can anybody help me how could i solve this prob.??
Thanks

Hi
I have assigned entire farmework page to another page and i made only navigationn panel visible..??
Thanks

Similar Messages

Qualified links to Relative links

Hi All-
I have created a course with links to pdfs in two if the
scos. They work fine when tested on my computer but when tested in
the LMS the pdfs won't come up: I need to change it from being a
fully qualified link to my hard drive, to being a relative link
pointing to the file in my course folder (in this case, it would
need to be ../Power_Handle_Training1a.pdf as the PDF exists in the
root of the overall course folder). I am not sure how to do this.
Please help.
Many thanks,
Rita

Simply set your button to open url or file and put the name
of the file in the box without any other info for ex.
Power_Handle_Training1a.pdf .
then make sure that everything including a copy of the pdf is
in the same floder after you publish. this should do it.

Converting absolute links to relative links

Using RH 7 HTML our corp wants to have help files able to function as "standalone" files on local PC's without network or server for business continuity. Presently most files have 150 or less topics and are published to a server. External files are in sub folders within the folder where the published file is located. Links to external attachments (.doc, .xls, .pdf, etc.) are absolute links and need to be changed to relative. An example existing link would be: HTTP://server.com/help/attachments/fname/sample.doc. Help is the foler where tje published file is located and Attachments is the folder where the external files to be linked are located. When link is changed to: ../Attachments/ some links work and some don't. I discovered that some links require: ../../Attachments/ to function correctly. It appears that links that are not in the root path of the project manager require additional ../'s. I am trying to find out how RH7 reads the links and how to back out of a directory and when. Any help is appreciated. Thanks.

The easiest, and most efficient, way is to replicate the folder environment onto your local machine (all folders and files exactly as they will appear in the destination area), and let RH do the heavy lifting.
Therefore, to link to anything outside the current RH project, the method is:
Select Link to: File in the Hyperlink dialog.
When you select your link destination from the Select File dialog and click Open, the Link to: field initially displays the absolute path.
Click OK.
Now, double click the link to reopen the Hyperlink dialog; RH has magically transformed the link into a relative path.
(You'll get an info message about linking to an external file...when you initially create the link and every time you open it...just ignore it.)
We use this method in a 42-project merged project, and it's never failed us. The only time that your links will break is when you copy or move a file to another location. Since the relative paths are no longer valid, RH will automatically assign the links to within the current topic; you'll need to re-assign the link manually.
Good luck,
Leon

Km document iview as a related link in a page

I have created a KM document iview which points to a pdf, assigned the iview to a page, it works fine. But if i try to assign it as a related link to another page, go to the page and click on the link in related links area the document does not come up, and says page cannot be found. Right now i have set the launch in new window property to open in new window. Weird thing is if i set this property to open in portal content area and click on the related link it opens the pdf. Problem occurs only when i set the property to open in new window.
Any ideas Gentlemen?
Any suggestions or help will be greatly appreciated.
Thanks,
Firasath Riyaz.

Ville,
Thanks a ton for taking your time to post a reply.
Yeah, I am able to preview from the pcd navigation structure and it works. The issue is only when I try to open it as a realted link.
I was experimenting a little bit, and found that if I add the iview to a page and add that page as the related link, it works.

Remote and testing server don't see root relative links the same

My site works fine on my testing server (Apache, MYSQL,
PHP). I use root relative links in a library
file (include file) so that it will work with all pages. For the testing server these links look like this:
/my_sites_root_folder/aaa/bbb/ccc etc.
If I use these same links on the remote server they won't work. To get hem to work I have to change all these links to the form
/aaa/bbb/ccc etc.
When dreamweaver uploads files to the remote server, the site name folder (my_sites_root_folder) doesn't go along for the ride--just the files in it. So on the remote all the site files are stored in htdocs. On my testing server, the files are stored in htdocs/my_site_root_folder.
I think it must have something to do with the way I'm setting up the remote and testing servers, but I'm read a hundred pages of instructions without being able to figure it out. I think I'm just seeing something wrong, but I've already spent days on this. Can someone please point me in the right direction?
I'm using DWCS5. Internet explorer 8, Windows 7.

Thank you for your prompt response. I'm afraid I'm still totally puzzled here. It sounds like you're very knowledeable about your comments, but I would like to know more. I accept that using the local site root in links would be bad, but I'm not clear WHY. Structuring the links as I have doesn't cause any links to break. I've structured them this way because it's the only way I can find that everything works. But I still do not understand WHY I have to do it. Using different libary include files doesn't seem like a good way to go, though
You suggest that if I use any root relative links at all, I need to use vitual hosts. I'm not finding any good coverage of what these are, and especially why they are necessary. If this is the case, does that imply that templates (which use root relative links) also will not work on the test server (at least without vitual hosts)? The conclusion I'm coming up with, given your remarks, is "Dreamweaver doesn't work with root relevant links when you're trying to test a site with a test server." Is this right?

Root-relative links & local testing server

Yesterday I figured out that I'd have to use root-relative links in an included SSI file so that it would work from both templates and pages in my main directory (or other directories, for that matter), e.g., 'src=/image/picture.jpg'. However, since my site is PHP, in order to test the pages or even to use Live View, I have to make use of a "testing server". I did this without much trouble using a package called EasyPHP, which sets up a local web server as well as the PHP module, MySQL support, etc. This all works very well.
The problem is that, in order to support several web sites, I have to use a "virtual directory" spec to direct the web server to the correct location for my site's files. In the setup for the testing server, I therefore have to specify a URL prefix such as 'http://localhost/corinthian' for this particular site. That has worked previously, but breaks when using root-relative links since the server sees the "root" as being the main "localhost" directory instead of "localhost/corinthian". So now my SSI doesn't display correctly because it's not being resolved to the correct directories.
I don't think that this is fixable unless someone else has run into it and can think of some gimmick I could try. Anyone? Breaking out some of my code into an SSI has definitely been more of a challenge than I expected!

I use 1&1 Internet as my hosting service. They apparently have my site set up in a virtual directory / virtual host fashion. Going to http://corinthian241.org, the root directory for root-relative links would have to be the directory pointed to by the URL. However, running phpinfo.php on the site shows the following result for $_SERVER['DOCUMENT_ROOT']: '/kunden/homepages/29/d246935068/htdocs/corinthian'.
So I'm pretty sure that a link from a page in my site home directory using this as a prefix would definitely not work, since the first "/" implies starting in the "corinthian" subdirectory -- not the real root of the server itself. Correct?
Doug

Site-relative links fail on local testing server

Using CS4/WAMP/XP, I have a testing server set up. All works well except that when I specify site-relative links, on the testing server they go back to localhost, not localhost/Frances. They work fine on the live site, but not on my testing server.
This prevents me from using (well, testing) 'include' files for things like menus when parts of the site are in different folders.
I have my site setup as follows:
Local Info
Site name "FFG2009"
Local root folder C:\wamp\www\Frances\
Default images folder C:\wamp\www\Frances\images\
HTTP Address: http://localhost/Frances/
Testing Server
Server model: PHP/MySQL
Access: Local/Network
Testing Server Folder: C:\wamp\www\Frances testing\
URL Prefix: http://localhost/Frances/
In my Apache config file I have a virtual directory set up like this
Alias /Frances/ "c:/wamp/www/Frances/"
<Directory "c:/wamp/www/Frances/">
    options all +includes
    AllowOverride all
    Order allow,deny
    Allow from 127.0.0.1
</Directory>
I have been advised that I could temporarily change the Apache webroot folder to my "Frances" folder, but that stops other things like PHPMyAdmin from working. Also I have other sites within my www directory and I'd rather not have to change the Apache rootweb directory every time I need to work on a different site.
Is there a way to set up my site in CS4 so that site root links go to localhost/Frances rather than just localhost?
Thanks
Tone'z

Many thanks Mark.
I fact I spent all yesterday coming to the same solution. Finally at around 12:30am this morning it worked!
Early in the day I found the same reference you mentioned in an on-line copy of David Power's book where he exactly described the very problem I had - and with the VH solution.
However, I had a problem with an obscure syntax error in the virtual hosts include file. I still don't know what it was. The flag to perform a syntax check on HTTPD startup didn't discover it. The problem actually prevented the Apache service from starting at all but that little point escaped me for a long time because the WAMP system tray icon is so small I didn't spot that it was telling me "some services are running" (half yellow) instead of "all services are running" (white).
It wasn't until I ran (in desperation!) Apache Monitor that it became obvious that Apache was tripping over this virtual host definition and failing to start.
It also seems that if you have any virtual host directive in an include file, then it negates the localhost directive in the Apache config file. So when I define the Frances virtual host, I also need to have localhost defined in the include file.
It was this localhost directive that was causing the problem. I found it by having Apache Monitor running so I can see the true state of the Apache service and, after pointing the config file 'include' directive to a vhosts file...
empty the vhosts file - Apache starts - 'localhost' works, frances doesn't - makes sense.
add the frances virtualhost definition to the vhosts file - Apache starts - 'frances' goes to the frances site, 'localhost' does too (dam')
add the localhost virtualhost definition to the vhosts file - Apache fails to start - "IE cannot display this page"
pull out the localhost definition - Apache starts... hmmmm... .
find an example localhost definition from somewhere else - to all intents and purposes identical to mine - add it in - Apache starts!
Both localhost and frances now work! Maybe there was a space where no space should be - I don't know.
Of course I also had to add entries into windows/system32/drivers/etc/hosts to point to 127.0.0.1.
Oh yes, virtualhosts are fussy about folder names. You cannot have spaces in a folder name.
Thanks
Tone'z

Issues with using relative links in Captivate 8

Is anyone else having issues with using relative links in Captivate 8? These links all used to work in the previous version of Captivate. And I could have sworn this was fixed already once in Captivate 8 but it's popping up again for us. Here is the situation... We have courses that are made up of multiple lessons which as separate Captivate files. Within those lessons are buttons to link to external documents (which live in a shared document folder), demonstrations, etc. We use relative links because we post these to our amazon servers and we also sell them to clients where they can post them on their own web servers or in their LMS. SO we can't put in full paths for the links or we'd have to change them constantly. So an example is that the link for a button might be "../Document/nameofdoc.pdf" This would be going to a user guide or something that is posted in the "Document" folder that lives at the same level as the lesson's folder. But now, all of the sudden, none of our bazillion links is working. And I've tried buttons, hyperlinks, and even the old click box. Nothing works with relative links. And I did check the permissions on every file and folder on our Amazon server to verify nothing changed there as well. Any suggestions?

I have the same issue with relative links using Captivate 8. I am trying to load Captivate modules into an LMS using relative links to document files within the LMS. The links work fine during a site page test so not an issue in the LMS, but from the Captivate module they aren't working....
Help?

How to make site root-relative links work in DW and Server both?

See details on buggy DW image link behavior, below. My question is:
1) how to make site root-relative links work in DW and Server both? Or…
2) how to reliably automate the change of several hundred legacy root-relative links of the form
/images/image.jpg to document-relative?
That is, to
../images/image.jpg or
../../images/image.jpg or
../../../images/image.jpg etc…depending on where the directory is.
The old format (/images/image.jpg ) used to work fine in my previous DW 8 configuration but appear grey in DW after “upgrading” to DW cs5.5 mac. (they look fine on the server, but it’s hard to edit image-heavy pages locally when they are all grey).
I tried changing the files to how DW creates root relative links now:
/public_html/images/image.jpg, which is a very easy, attractive root flow since there’s a one-to-one mapping. These look great in DW but are broken on the server!
I looked at the “advanced” site setup, and it looked like it might be possible to nuke the /public_html/ part of my server info…but it also looked like there was the potential for doing damage changing these settings, which are automatically generated from our server connection settings, which seem to work.
The “links relative to document/ site root” toggle…does that change how DW interprets existing links, or just change the default when you are adding a link? I have made 80% of the file links document relative…before wondering if root-relative isn’t better?
It sure seems less ambiguous for all those images if theres a way to make root relative work for DW design view, DW link check, and server.
Summary of buggy behavior: (see test with images here)
"old style" site root link
      /images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: broken (grey w/ broken icon)
      Link check in DW: "external link" (i.e., uncheckable, + file could appear orphaned)
      Browser: good
      Ease of switching: n/a (existing format)
"new style" site root relative link
      /public_html/images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: good
      Link check in DW: good
      Browser: broken
      Ease of switching: easy
Document relative link
      ../../images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: good
      Link check in DW: good
      Browser: good
      Ease of switching: hard (how to automate?)
Absolute link
      http://www.oasisdesign.net/images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: broken (grey w/ broken icon)
      Link check in DW: external (i.e., uncheckable, + file could appear orphaned)
      Browser: good
      Ease of switching: n/a...not a real option
Thanks!
Similar discussion on "/"

Hello again Jon!
Thanks for jumping on this.
All clear and understood about where publc_html is etc.
No contemplation of nuking the actual public_html directory on the server, just the "/public_html" text string at the start of the DW-generated links.
"/public_html" is automatically added to the front of the link in DW if I create the link with any of the GUI tools, if I have "site root relative" selected. And ""/public_html" ends up in the code, and gets uploaded that way to the server, where it (obviously) doesn't work.
Doesn't sound like it is supposed to work this way. Also, what seems to be the usual root relative format (/images/image.jpg) shows as a broken link in the GUI and an external link in the DW link check. All this togther makes me thinkI have some obscure setting incorrect?
The setting that caught my eye is manage sites/ site setup/ advance settings/ local info/ web url, which is automatically set to http://www.oasisdesign.net/public_html/
it gives an option to change it but it makes every effort to make this NOT look like something users should mess with:
Having gone through the more careful thought process during this post, I'm ready to do the experiment of changing the remote server web URL (why is it wrong by default?)...think I'll eat dinner first so there's 45 min to avert disaster if anyone knows this to be a bad idea!
Art
PS--don't have a local testing server...don't think this will solve the GUI broken link/ link shows as external problems.
Is there an easy, automated way to change links sitewide from document to root relative?

How do I code relative links as function parameters within Templates?

I am a newcomer looking for best practices for a "How Do I?" properly code relative links as function parameters within an Adobe template (DWT) which accomodates page creation at 2 different level of folders. Dreamweaver doesn't appear to handle auto-correction of relative links as function parameters as far as I can see. It's not clear to me what the best practice I should be following. While this is not exactly a SPRY question, I am hoping that someone using the Spry.Data.XMLDataSet had already found the best practice to use.
My Site
-- Multiple pages at this level and the parameter needs to be "_includes/UnitSideNavigation.xml"
SubFolder
-- Other pages at this level. and the parameter needs to be "../_includes/UnitSideNavigation.xml"
And this is the particular code snippet within a non edtable template area I would like to work for 2 levels of pages created from the template.
<script type="text/javascript">
var dsItems1 = new Spry.Data.XMLDataSet("_includes/UnitSideNavigation.xml", "/links/firstlevel");
var dslinks = new Spry.Data.NestedXMLDataSet(dsItems1, "secondlevels/secondlevel");
</script>
My environment is Windows/Vista using latest CS4 dreamweaver.
Any pointers appreciated. This is learn time for me. Hope I have made myself clear. Andy

I use serverside includes instead of DWT for exactly that reason. Not only that, if you change anything within the template you must re-upload all of the files affected by the change; only the modified include file needs to be uploaded.

How to remove bullets and spacing for url links in the Related Links iview?

I tried to look for a property that I can edit the look-n-feel of the url links in the Related Link iView using "Theme Editor".
All I need is to remove the bullets and increase some vertical spacing between the links.
Currently, it looks like this:
URL iView A
URL Iview B
I go through the whole section of Related Links properties, none of them seems to do what I want.
Here are the list of properties in Related Link section (of Navigation Panel):
Link Color
Text Decoration of Link
Hover Color
Text Decoration of Hovered Link
Initially, I thought "Text Decoration of Link" should be the right property I should look at. But there are a drop-down with 5 options: None, Underline, Blinking, Overline and Line-Through, which really can't achieve what I want.
Thanks for advice.
Kent
Post with Diagram Illustration:
<a href="http://sapnetweaverforum.blogspot.com/2006/11/how-to-remove-bullets-and-spacing-for.html">How to remove bullets and spacing for url links in the Related Links iview?</a>
Message was edited by: Kent C.

Hi, Kai.
I checked the Related iView properties (URL Template), I don't see what layoutset it is really using. I am not sure, is that a layout set apply to the Related Link Iview?
For the regular KM iView, I will see what Layout Set I want to apply, then I can go and change the properties (of layout coontroller, collection renderer & resource renderer)you mentioned. But for this Related Link iView, I really don't know. I guess it may be in the code itself.
If there is a layout set for Related Link iView (or the place to apply layout set to it), can you point to me which one is that? (I did a search through the layout set names, I only find the AppQuicklinkExplorer (I used this for Dynamic Nav. Link iView before), if I can aply this layout set to Related Link iView, my problem will be solved.)
Thanks for help.
Kent

Moving a SWF containing relative Links no longer work

Hi
I've come to the experts.
I created a Flash Catalyst Project that contains external URL links. I actual want them to be internal relative links.
I've followed the process of using to Flash Builder to edit the Main.mxml file to change to a relative path.
I hit the Project/Export Release Build...
I open the SWF file in Flash Player from with in the 'bin-release' folder and it all works great. However when I move the swf file to another folder that actually contains what would be the same relative path to the files I want to link it no longer works.
If I look at the content of the swf file in a third party editor/viewer app the relative path is correct.
I'm probably missing something very fundamental but just can't 'click' to it, pun intended.
Thanks for your assitance
David

Hi Bear
Thanks for your help.
I've referred to both the references your below. Both were useful but still the issue remains.
When I relocate the swf file with all the associated src files it doesn't work
As a further test I pointed the 'Project Export Release Build' from Flash Builder to the actual folder I wanted the swf file in and again it didn't work
If however I point the 'Project Export Release Build' to //documents/Adobe Flash Builder 4/bin-release it does work
Any thoughts would be greatly appreciated.

My Relative links no longer work in Captivate 7

My Relative links no longer work in Captivate 7. They worked in the 5.5 versions of the exact same lessons. But they do not work after saving and re-publishing in Captivate 7. What's up with that? Any suggestions?
Just found out from Adobe it's a reported bug that is not yet resolved...
Bug Number : 3603218

This is typically an issue of setting the web preference in the WINDOWS preferred programs. In Win7 this is accessed from Control Panel>Default Programs>Set Program Access...>Custom. Maybe these options will give you an idea of the problem.

Opening a pdf file in a relative link / local

Maybe this sounds simple.
But I get used to AS2 code to open a pdf file like the code below:
getURL("pdfDocuments/pdfname.pdf","_blank")
As I search uncle Google I'm stuck to this as equivalent to getURL in AS2.
btn.addEventListener(MouseEvent.CLICK, btnClick);
function btnClick(e:MouseEvent):void {
navigateToURL( new URLRequest("pdfDocuments/pdfname.pdf"), "_blank");
But still it did'nt work.
Before in AS2 getURL working on mailto, pdf on a relative link and a typical url's.
But as to AS3 navigateToURL function only works on mailto and typical url.
Any tweaks to the code above, to get it to work? will much appreciated.
Thanks,

There's numerous examples if you google "call javascript from actionscript".
Here's 1 that sums it up pretty simply, just import flash.external.ExternalInterface; then use it statically via its call() method to call javascript. Then in the javascript simply do what you want.
http://www.hardcode.nl/archives_155/article_334-call-javascript-function-from-as3-and-vice versa.htm
e.g. ACTIONSCRIPT:
import flash.external.ExternalInterface; // call javascript function passing to load relative URL "pdfs/some.pdf"ExternalInterface.call("loadPDF","pdfs/some.pdf");
e.g. HTML
<html><head><script type="text/javascript">// </script><body> </body></html>
Nothing really much to it.
Here's a reference to window.open() if you want to customize the opened window:
http://www.w3schools.com/jsref/met_win_open.asp

New From Template Changes Relative Links to Local Root?

Thank you for taking the time to read and understand my plight with Dreamweaver CS3 for Mac. I apologize for the lengthy question, but in the effort to provide detail I shall go. First the background:
I'm updating, editing, and appending an existing site that was previously created with Dreamweaver.
I'm new to Dreamweaver but have a pretty good understanding of things
I created a new site on the local drive on my MacBook Pro and then downloaded the entire site via FTP (live site: domain.com)
I then replicated the site and exact file structure using FTP to a staging server (staging.domain.com)
There are three existing .dwt templates. I've successfully updated the template file and auto updated all other pages that were based on this template.
But my problem comes from creating new pages FROM the template. It appears that while the .dwt template file shows relative links (../xxxx) in the code, when create a new file from the template the url of these links is replaced by the path to the file on my local drive... I want non of this (.../xxxx) is fine.
What is happening is that a javascript drop down menu is disappearing when I create new from template. I am assuming it's because of the path changes.
This is the ORIGINAL (good) code from the .dwt:

<tr>
     <td height="31">
          <table width="718" border="0" cellpadding="0" cellspacing="0">
               <tr>
                    <td width="24"><img src="../images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
                    <td width="342" style="background-image: url(../images/Header-BG.gif);"><img src="../images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
But when I create a NEW page from the above template the code is changed to the local path:

<tr>
     <td height="31">
          <table width="718" border="0" cellpadding="0" cellspacing="0">
               <tr>
                    <td width="24"><img src="file:///Grasshopper/Users/allan/Documents/clients/site/site staging master/images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
                    <td width="342" style="background-image: url(file:///Grasshopper/Users/allan/Documents/clients/site/site staging master/images/Header-BG.gif);"><img src="file:///Grasshopper/Users/allan/Documents/clients/site/site staging master/images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
To be sure all links in the template file are changed too.
This is the .dwt file itself
This is a random page created from the above template.
And this page was created by simply altering the .dwt template file linked above and then SAVING AS. You can see the relative links remained and the navigation bar looks and operates as normal.
To provide easier visual reference I offer the following:
This is the .dwt file when opened in dreamweaver:
Note the black area where the javascript drop down menu is in the top navigation when the page is correct:
But when I create a NEW page from template this is what I get in the top navigation bar:
And then this is what it looks like when posted:
Ultimately what I'm trying to do is:
1) work on site files on my local drive
2) sync the local drive with staging.domain.com so my client can proof and approve
3) sync to the actual live site at domain.com
I assume I could simply do this by changing the ftp info and given the site structure and all files are same and ideally all links are relative this should be accomplished easily.
Though perhaps my problem stems from the fact my local site is buried several layers deep on my local drive Local Drive/Users/Me/Clients/Client.... etc... but I haven't checked this yet.

Great... Thanks for your patience....
Here are links to all questioned files on the staging server:
This is the .dwt file itself
This is a random page created from the above template that shows the image/navigation incorrect.
And this page was created by simply altering the .dwt template file linked above and then SAVING AS. You can see the relative links remained and the navigation bar looks and operates as normal. (obviously the wrong thing to do.
And this page is one that was created prior to my working on the site and was based on the subpage template and displays correctly.
Now bear with me here as I notice this behavour too.
In the code snipped taken directly from the DW .dwt template (linked above)
<td width="24"><img src="../images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
                    <td width="342" style="background-image: url(../images/Header-BG.gif);"><img src="../images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
you'll notice there are two images L-Header-Corner.gif and one that is Header.BG.gif.
The difference here is that the BG gif has a style attributed to it "Background-Image) which is followed by some strange code that says (url)../
Opening that file Background Image and it's a tiny slice of what I think is part of the entire missing gray bar:
In a page that displays correctly the code looks like this:
<td width="24"><img src="../images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
                    <td width="342" style="background-image: url(../images/Header-BG.gif);"><img src="../images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
And in a page that is displaying incorrectly the code appears like this:
<td width="24"><img src="../images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
                    <td width="342" style="background-image: url(file:///Grasshopper/Users/allan/Documents/clients/koolfog/koolfog website staging/images/Header-BG.gif);"><img src="../images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
So you can see that the link in this case (with the URL and style) has actually been converted to a site (my hard drive) relative link when saving.
So the pressing question stands: Why doesn't dreamweaver convert that URL link when saving a page created from a template back to the same directory?
Also, it appears that in that .DWT all the links have the leading periods and therefore are document relative... since I didn't set this up, how do you think this happened?

Links in Related Links

Similar Messages

Maybe you are looking for