Dreamweaver Library Item Problem

Library Item Issue within a subfolder

[woemlavy]

I am having a problem with some library items and I can't figure it out. I am using Dreamweaver 4.

1. I have a Header that is a library item...I use it on all pages.
2. I have the links within this library item set to a relative path - example ( index.html)
3. I have created a subfolder on the root level and I added this library item to an .html page inside this subfolder.
4. When I view this .html page, Dreamweaver shows the paths in my Header links as [sitename.com...]
5. I solved the problem by detatching the library item on the page in the subfolder. But, this is causing way to much work when a page needs to be updated.
6. I also tried to change the library item's link paths to ( /index.html) & (../index.html) but they just take me out of the subfolder and back to the root level.

7. So...in a nutshell...I want to use a library item on an .html page in a subfolder. While, staying relative to that subfolder.

Any one have an thoughts?
Thanks in Advance,
Christian :)

[treeline]

If absolute links don't work for this site, you could have 2 library items, identical to each other but in the same directory as their files.

This would be easy to update.

I'd also take a careful look at all the links in the library item, and how they're linked (absolute/relative).

[vkaryl]

Well, woemlavy, I had exactly this problem with the large non-prof site which is my only reason for owning DW4. I must have tweaked the *.lbi files a hundred times in the course of a weekend, and never ever got it "fixed". I finally in desperation downloaded from the site and overwrote EVERY file, then overwrote the "new" *.lbi files with the backup I'd made prior to starting on it, THEN recreated the new *.lbi files. When the program updated all 257 files after all that, it all worked perfectly. NONE of the link info had changed in any way; it was all still exactly the same, with only additions linked as per the old stuff. Gremlins.

A few weeks later, a friend of mine who's a DW guru of sorts was here for a couple of days, and during a conversation about why I'm NOT happy with DW this situation came up. She basically said it's a fault with that version of DW and suggested (like big surprise here!) that I shell out several hundred dollars for MX. Thank you, no. I'll just keep using DW4 for this one site, and TSP for everything else. Should this particular situation occur again before I have permission to use real code on this site, I'll just reapeat the above "non-fix"....