In-Portal Issue Tracker - In-Portal CMS
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Type: | Reproducibility: | Date Submitted: | Last Update: |
360 | [In-Portal CMS] Front End | feature request | always | 2009-10-06 14:20 | 2011-07-17 05:28 |
|
|||||
Reporter: | alex | Platform: | |||
Assigned To: | OS: | ||||
Priority: | normal | OS Version: | |||
Status: | active | Product Version: | 5.0.1 | ||
Product Build: | Resolution: | open | |||
ETA: | none | Fixed in Version: | |||
Reference: | |||||
Change Log Message: | |||||
Estimate Points: | 0 | ||||
|
|||||
Summary: | 0000360: Section renaming tracking | ||||
Description: |
Section names are used in url building, e.g. "http://www.site.com/sample/path" consists of two sections: "sample" and "path". In case, when one of them is renamed, then url to the page is changed, and previous page url is no longer accessible for example to "http://www.site.com/another-sample/path". This is not good in case, when google or other spider has already indexed previous url to the page. I propose to track such type of renaming and it will act as FriendlyURL field: when all page url matches renamed page url, then redirect is made to new url with 301 (Moved Permanently) code, so spiders will be happy. It should also work in case, when page will be renamed more then once. But it's possible, that problem could occur in case, when in time some pages will be renamed to same name or worse. So there is need for some testing here. |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: | |||||
|
|||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2011-07-17 05:28 | alex | Description Updated | bug_revision_view_page.php?rev_id=766#r766 | ||
2009-10-06 14:20 | alex | Target Version | => Icebox | ||
2009-10-06 14:20 | alex | New Issue |
There are no notes attached to this issue. |