Sent for review: template path changed from relative toabsolute

rubenvasquez · rubenvasquez

On our site we use DW, Contribute and third party code to generate the site
navigation. The workflow is
ckeck out site, download, create page(s), update navigation in template,
update pages, upload, check site in.

If users change and publish a page everything seems to work well. However,
when a user changes content and sends the draft for review CT changes the path
to the template from a relative path: <html lang="en"><!-- InstanceBegin
template="/Templates/myTemplate.dwt" to an absolute path: <html lang="en"><!--
InstanceBegin template="http://www.mysite.com/Templates/myTemplate.dwt"

When we update the template, the pages that were published after being
reviewed still have an absolute path, and thus DO NOT GET UPDATED.

We can reapply the template to a page to solve the problem. But this is not
practical for a site with hundreds of pages and a dozen content updaters.
Would appreciate any suggestions,
Thank you,
Ruben

bobolech · bobolech

Have you figured out this problem yet?

We are suffering from the same problem -- our templates are modified by
Contribute whenever a draft is sent for review and then published. When a page
is simply edited and published, we have no problems. But when a draft is sent
for review and then published, the relative path for a template is turned into
an absolute path!

For example, this:


Becomes this:


Regards

bobolech · bobolech

We just did some more testing of this issue and we noticed a new, more
disturbing aspect of the problem. We noticed that the paths to the templates
were modified when a draft was sent for review and then published. But we also
noticed that the paths to our stylesheets, which use relative paths like this:
<link rel="stylesheet" href="/local_scripts/styles.css" type="text/css"
media="all">
were being converted when published to take this form:
<link rel="stylesheet" href="http://staging.abc.com/local_scripts/styles.css"
type="text/css" media="all">
where staging.abc.com is the domain name of our staging website, which is an
internal server where we post changes to test them -- the changes are then
automatically copied to the live server throughout the day. A page with a
stylesheet declaration that uses a relative path is fine -- it doesn't matter
what site the stylesheet file resides on -- but when a fully-qualified path to
a stylesheet on an internal server is used and then published to an external
server, the page breaks since it is referencing an internal URL it cannot
access.

The bigger question for us isn't why Contribute is taking liberties with our
template paths, but why it's messing around with the path to our stylesheets.
My understanding was that Contribute didn't mess around with content in the
header. Why should it???

This product is so aggravating.

And we've tested this with both version 3.1 and 4.0, which is the first thing
their tech support will insist we try...

Stay tuned...

xarina · xarina

We are also seeing this problem, and not only is it bad for updating templates,
we also use template parameters, so we cannot adjust template params until we
manually change the template path back to "/Templates".

Has anyone been in touch with Adobe Tech support about this one, and if so,
what is the status of the problem?

Sent for review: template path changed from relative toabsolute

Thread Tools

Display

Sent for review: template path changed from relative toabsolute

Similar Questions and Discussions

User control + relative path

Relative Path for Shared Movies

relative path

#25506 [NEW]: <xsl:include> with relative path

File, relative path handling.

Re: Sent for review: template path changed from relativeto absolute

Re: Sent for review: template path changed from relativeto absolute

Re: Sent for review: template path changed from relativeto absolute

Posting Permissions