In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

View Revisions: Issue #360 All Revisions ] Back to Issue ]
Summary 0000360: Section renaming tracking
Revision 2011-07-17 05:28:27 by alex
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.
Revision 2009-10-06 14:20:58 by alex
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 302 (Permanently Moved) 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.



Web Development by Intechnic
In-Portal Open Source CMS
In-Portal Open Source CMS
Copyright © 2000 - 2009 MantisBT Group

Powered by Mantis Bugtracker