tag:help-archives.hannonhill.com,2010-02-09:/discussions/general/97-internal-managed-links-not-respecting-site-url-on-publishCascade CMS: Discussion 2018-10-18T20:36:01Ztag:help-archives.hannonhill.com,2010-02-09:Comment/26856642010-08-25T14:13:37Z2010-08-25T14:13:37Zinternal managed links not respecting site url on publish<div><p>Hi,</p>
<p>Really the only way you can do this is by creating a <em>content</em> folder in your Cascade Server instance and then moving your site assets underneath that folder.<br />
</p>
<p>It looks to me like the page on <a href="http://www.hannonhill.com/kb/Sites/index.html">Sites</a> needs to be updated -specifically the portion about the Site URL. This value is not used for publishing. It is used for:</p>
<ul>
<li>Cross-site links (so that Cascade knows how to create a link to another Site in your instance)</li>
<li>Live pane (so that Cascade knows the location of the corresponding asset on the web server)</li>
<li>Twitter Connector (so that the link generated in the tweet is correct)</li>
</ul>
<p>Hope this helps to clear things up.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/26856642010-08-26T19:47:57Z2010-08-26T19:47:57Zinternal managed links not respecting site url on publish<div><p>Hmm , ok it seemed like it should be possible judging from this comment ...</p>
<p><a href="http://help.hannonhill.com/discussions/how-do-i/111-losing-asset-links-after-publish">http://help.hannonhill.com/discussions/how-do-i/111-losing-asset-li...</a></p>
<p>but i guess having cascade mimic the actual site structure is just as good a solution.</p>
<p>it still kind of bugs me that cascade assumes its always publishing to the root of your site though ...</p></div>pkhalil