Currently, for content types that support display pages, the content can be displayed with its associated display page template by using its friendly URL. However when the friendly URL changes the old URL does no longer work (even if the FriendlyURL service is keeping a history of them).
The goal of this story is to make old friendly URLs work. In particular when an old friendly URL is used a permanent redirect to the new friendly URL should be issued to the browser.
Given a display page URL for a blog entry with friendlyURL. "blog1"
And changed to "newBlog1"
When users access displayPageURL/blog1
Then users will be redirected to displayPageURL/newBlog1
|Test Priority||Test Scenarios||Covered by Backend (Unit/Integration)?||Test to add|
|4||User is redirected to the new friendly URL when he accesses a blog display page URL with an old friendly URL||YES||NA|
|4||User is redirected to the restored friendly URL when he accesses a blog display page URL with an old friendly URL after he restored a friendly URL||NO||BlogsFriendlyURL#CanAcessDisplayPageWithOldFriendlyURLAfterRestoring|