tag:help-archives.hannonhill.com,2010-02-09:/discussions/how-do-i/230-redirectsCascade CMS: Discussion 2012-12-03T20:31:27Ztag:help-archives.hannonhill.com,2010-02-09:Comment/36493712010-11-11T20:59:25Z2010-11-11T20:59:25ZRedirects<div><p>You should be able to achieve this via a Symlink within the CMS. If your use case differs please let me know.</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/36493712010-11-17T17:05:19Z2010-11-17T17:05:19ZRedirects<div><p>Clarification:<br />
Symlinks are non-publishable assets that are useful when wanting to add External Links to dynamically driven content (navigation, sitemaps, etc). Because they are non-publishable, they can not really be used to communicate directly with your server with regards to creating redirects on it.</p>
<p>There are however two ways that I have found to implement this:<br />
1) Create a Content Type that will utilize a Data Definition that users can enter groupings of redirect information into, this page can have a block and format combo that output the content as a .htaccess file. This allows for the management of redirects in one location.<br />
2) Create a Content Type for Page Redirects that utilizes a scripting language (PHP, .net, Coldfusion, JS, etc) that will actually perform the redirect. This means that you will need to have one page for every redirect that you want. There are a couple ways that these can be contained in Cascade. The first being that they all be contained in a separate site so as not to confuse users who just want to manage content within Cascade. The other being within your site structure depending on where you want content redirected from.</p>
<p>If anyone else has any suggestions on other ways of doing this, I would be really interested in hearing them.</p></div>Penny