You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When moving (cut/pasting) a page from one area of the website to another, it would be useful if a dialogue box were presented to the editor (person), prompting them to add a redirect for any visitors going to the old URL.
If the editor chooses to add such a redirect, the CMS would send an HTTP 301 (Moved Permanently) response back to the visitor's browser when they request an old URL.
This feature would also require an additional check on new page creation, to ensure that any new pages placed on top of a pre-existing redirects, deleted said redirects (or warned the editor).
Given that Composite.Tools.LegacyUrlHandler and CphCloud.Packages.UrlAlias share similar functionality, it might be a good idea to get both of these packages to store data in the same location and/or merge functionality.
When moving (cut/pasting) a page from one area of the website to another, it would be useful if a dialogue box were presented to the editor (person), prompting them to add a redirect for any visitors going to the old URL.
If the editor chooses to add such a redirect, the CMS would send an HTTP 301 (Moved Permanently) response back to the visitor's browser when they request an old URL.
This feature would also require an additional check on new page creation, to ensure that any new pages placed on top of a pre-existing redirects, deleted said redirects (or warned the editor).
Given that Composite.Tools.LegacyUrlHandler and CphCloud.Packages.UrlAlias share similar functionality, it might be a good idea to get both of these packages to store data in the same location and/or merge functionality.
Copied from Codeplex issue 1818.
The text was updated successfully, but these errors were encountered: