Note that there are some explanatory texts on larger screens.

plurals
  1. PORedirects in Ektron 8.6.1
    primarykey
    data
    text
    <p>Has anyone played with the new redirect feature in Ektron 8.6?</p> <p>We tested it (in 8.6.0) before upgrading and were happy with it. But when it came time to do the upgrade, Ektron had released 8.6.1, so we upgraded directly to that. Now we are having trouble with the redirect feature. (Yes, we should have tested everything again in 8.6.1 before upgrading)</p> <p>Now if we try to add a redirect rule for an existing page in the CMS, it does not work. But if we create a redirect rule for a page the does not exist, then try to hit that address, the redirect works fine. We need the redirects to work for existing pages in the CMS.</p> <p>To clarify what "working" and "not working" means...</p> <p>If I have an existing page in the CMS with manual alias of "/erc/lucien.apsx", I can create an entry in the redirect table like this... <img src="https://i.stack.imgur.com/9eVDn.gif" alt="enter image description here"></p> <p>Adding this entry generates no errors, but when I visit the page, all I see is the regular old page I created. <em>NOT</em> the Google site it should be redirecting to. I <em>do not</em> get any 404 errors. </p> <p>But if I create a redirect entry for a page that <em>does not</em> already exist, like this... <img src="https://i.stack.imgur.com/4jg5u.gif" alt="enter image description here"></p> <p>It works perfectly. If I try to visit the /erc/fake.apsx address, I end up on the Google site, as expected.</p> <p>(FYI, we create a "fake" page in the CMS for external content so we can attach metadata to it and make it searchable in taxonomies, but then provide a link to the "real" page. I want to use redirects here so users don't have to do this extra click)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload