exponentcms
commented
4 years ago (from [bc425e517f9591c5f3e7cacf5665b901e7a9dfac]) initial implementation of optional page redirection support; must be turned on in site configuration, then managed by manage all pages; corrects calls to expCore::encode; adds support for non-search paginationCallback() to allow formatting of paginated data after sorting/paging, but before output (think human readible date/time) [#1392 state:resolved] https://github.com/exponentcms/exponent-cms/commit/bc425e517f9591c5f3e7cacf5665b901e7a9dfac
It would be nice to have some sort of redirection management to include logs of missed 'pages', and the ability to assign alternate names to pages, and another log of page requests that have been redirected. Useful if you rename a page so you don't have to go into Google Tools to setup a 301 redirect manually. There are plugins which do this in WP.
This could be accomplished in expRouter->routePageRequest() after we fail to find the page (by name), the store product (by sef_url) or store category (by sef_url) and before we return 'false'. It would probably require up to 3 tables where each 'missed page' (404) would be logged into the table, a 2nd table would contain the redirect mapping, and a 3rd table would contain a record of the page (requests) actually redirected (301) through the mapping table (might be included in table 1)
This might be further extended to include redirection of a local sef_url to an external (long) link, but we wouldn't want to pass a 301 redirect in that case.