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 #548		[ All Revisions ] [ Back to Issue ]
Summary	0000548: Automatic mod-rewrite redirecting

Revision	2010-02-03 13:34:15 by alex
Description	1. I propose we redirect with 301 code (moved permanently) in case if user visits non-rewrited url, when mod-rewrite is currently enabled. 2. Also we could redirect to "index" template (maybe with same code) in case if user just types site url without concrete page. This will make google analytics statistics more readable and google will be happy to automatically update it's search index.

Revision	2010-01-29 19:06:06 by alex
Description	1. I propose we redirect with 301 code (moved permanently) in case if user visits non-rewrited url, when mod-rewrite is currently enabled. 2. Also we could redirect to "index" template (maybe with same code) in case if user just types site url without concrete page. This will make google analytics statistics more readable and google will be happy to automatically update it's search index. 3. Don't include any kind of page tracking code (e.g. google analytics), when admin is editing site contents (front-end in a frame) so page tracker won't count any fake visits.