Why does contribute re-write link paths?

[joan-i]

Most of the links in my Dreamweaver site are root-relative. Contribute is
re-writing these into document-relative links. Many links are in the nav bar
which is controlled by a Library item. Inconsistent link paths makes it
difficult to do global find/replace with any confidence. I had hoped I could
control this by creating templates with editable regions, but that doesn't seem
to help.

Some of my .asp files live in a virtual directory elsewhere on the server.
There I prefer to use document-relative links and Contribute is re-writing them
as absolute links. This breaks the pages so I have to fix them every time
someone edits a page. It's counter-productive.

If nobody is editing these links directly, Contribute should just leave them
alone. I don't understand why Contribute feels it is necessary to rewrite
code. If re-writing is unavoidable, then administrators should be allowed to
set preferences for it.

Is Adobe addressing this issue?

[Dominic Michael]

Are you following this scenario
1. Create a template (dwt) in Dreamweaver CS3
2. Insert a Library item (lib) in the template and upload it to the server.
3. Launch Contribute CS3 and create a page using same template
4. Click "Send for Review" to send it to a reviewer.
5. Reviewer publish the page.
Then the path is changed or Without sending for review on editing the page
Contribute changes relative path to absolute path for library items?

[joan-i]

Yep. I followed the procedure you outlined and it still changed the links. It
changed all links beginning with "/xxx" to "../xxx" in the supposedly
non-editable regions of the document. This occurred for both new pages from
template and editing an existing page.

I found a workaround, though. When I open the document in Dreamweaver and
select Modify > Templates > Apply Template to Page, it changes all the template
code back to the original.

I guess that'll work as long as I remember to do it.
*j