tag:help-archives.hannonhill.com,2010-02-09:/discussions/how-do-i/16323-publishing-relative-links-when-the-base-site-url-contains-a-folderCascade CMS: Discussion 2015-03-11T19:24:05Ztag:help-archives.hannonhill.com,2010-02-09:Comment/359124062015-01-30T14:55:45Z2015-01-30T14:55:45ZPublishing relative links when the base site url contains a folder<div><p>Hi John,</p>
<p>You shouldn't need to worry about this issue if we're dealing
with cross-site links, so it sounds as though these Sites may need
some tweaking. How are each of these Sites set up? That is, what is
their Site URL and what does the top level folder structure look
like (feel free to attach a screenshot of this)? What do the
Destinations look like as far as what directory they are publishing
to?</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/359124062015-01-30T19:08:03Z2015-01-30T19:08:03ZPublishing relative links when the base site url contains a folder<div><p>Each site is actually just a sub-folder of a single site. The
site URLs are: <a href=
"http://www.domain.com/site1">www.domain.com/site1</a>, <a href=
"http://www.domain.com/site2">www.domain.com/site2</a>, <a href=
"http://www.domain.com/site3">www.domain.com/site3</a> but "site1",
"site2", and "site3" folders don't existing in each cascade site.
The destinations for each point to the site1, site2, and site3
folders, and everything publishes properly. The issue isn't even
with cross site links, because those all get prepended with the url
for the site they point to. Linking within the site however is what
is becoming the problem. We're trying to create shared assets that
can be included on multiple pages without having the content exist
on all those pages, and since the assets can be included all over
the site we can't use relative paths the relative path from the
location the shared asset publishes to might not be correct for the
page it then gets included on. The problem with using absolute
links, is that when cascade publishes an asset that links to
"widgets" folder in site1, the absolute path is "/widgets..."
instead of "/site1/widgets...". so I added the logic above to find
those links, and prepend the site folder, in this case "extra" but
it creates a broken link.</p></div>johnvinebtitag:help-archives.hannonhill.com,2010-02-09:Comment/359124062015-03-04T21:01:43Z2015-03-04T21:01:43ZPublishing relative links when the base site url contains a folder<div><p>Hi John,</p>
<p>My apologies for such a delayed response to your discussion.</p>
<p>I wanted to follow up to see if you had a chance to resolve your
linking issue. If not, I was trying to picture how you have your
"sites" and Destinations set up, but I'm not sure if I'm following
correctly. Starting at the Site's base folder, do you have a folder
for each sub-site? For example:</p>
<pre>
<code>- Base Folder
-- site1
-- site2
-- site3</code>
</pre>
<p>If so, can you describe in more detail what you mean by the
following:</p>
<blockquote>
<p>The site URLs are: <a href=
"http://www.domain.com/site1">www.domain.com/site1</a>, <a href=
"http://www.domain.com/site2">www.domain.com/site2</a>, <a href=
"http://www.domain.com/site3">www.domain.com/site3</a> but "site1",
"site2", and "site3" folders don't existing in each cascade site.
The destinations for each point to the site1, site2, and site3
folders, and everything publishes properly.</p>
</blockquote>
<p>Thanks!</p></div>Ryan Griffith