tag:help-archives.hannonhill.com,2010-02-09:/discussions/velocity-formats/5356-extension-is-not-added-in-pathCascade CMS: Discussion 2013-08-27T19:56:55Ztag:help-archives.hannonhill.com,2010-02-09:Comment/284658882013-08-27T18:22:18Z2013-08-27T18:24:18ZExtension is not added in path <div><p>I was able to resolve this issue by using <code>link</code>
instead of <code>path</code></p>
<pre>
<code>#set($link = $departmentLink.getChild('internal-link').getChild('link').value)</code>
</pre>
<p>I still don't understand what magic cascade is using to allow
paths to work for non-cross site links. I don't know why it adds
the extension when linking in the same site, but not cross
site.</p></div>blakeplumbtag:help-archives.hannonhill.com,2010-02-09:Comment/284658882013-08-27T19:45:33Z2013-08-27T19:45:33ZExtension is not added in path <div><p>Hi,</p>
<p>Glad you were able to resolve this. As you mentioned, using
<code>path</code> will work for links to assets within the same
Site but you'll need to use the <code>link</code> element when
writing links to assets in other Sites. The reason for this is that
the <code>link</code> element includes the information that tells
Cascade Server the asset you are linking to is in another Site.
When you use the <code>path</code> element, Cascade Server will
attempt to locate the asset by using that relative path. So, if it
doesn't exist in the current Site, it will fail to rewrite the link
properly (because the relative path in the Index Block is relative
for that specific Site rather than the Site you are in).</p>
<p>Let me know if this makes sense.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/284658882013-08-27T19:55:22Z2013-08-27T19:55:22ZExtension is not added in path <div><p>That makes sense. Thanks Tim!</p></div>blakeplumbtag:help-archives.hannonhill.com,2010-02-09:Comment/284658882013-08-27T19:56:53Z2013-08-27T19:56:53ZExtension is not added in path <div><p>You bet. Have a good one!</p></div>Tim