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!

Dependency Graph View Issue ] Relation Graph ] Horizontal ]
related to child of duplicate of

Viewing Issue Simple Details
ID Category Type Reproducibility Date Submitted Last Update
0000445 [In-Portal CMS] Other bug report always 2009-12-16 10:40 2011-03-14 02:10
Reporter alex View Status public  
Assigned To alex
Priority normal Resolution fixed  
Status closed      
Summary 0000445: Enable Mod-rewrite for Front-end in Admin
Description Currently mod-rewrite mode (on/off) is ignored, when Front-End is viewed via
right frame in administrative console. This is no big deal, because all url
building methods build urls, that will work in both cases (with and without
mod-rewrite). But, with new rewrite listener approach (added in 5.0.1) we
could came across situation, when developer could create such rewrite
listener, that must be always present for customized urls to work. See
example provided below:

Example #1:
mod-rewrite off:
mod-rewrite on:

In example #1 such transformation to url happens:

   - "-2-" is language id, which is transformed to "/russian/";
   - "m555" is category id, which is transformed to "/path/to/category/";
   - "path/to/template" is just added to url's ending without

In this scenario url parser/builder always could determine what url part is
transformed/parsed to what ID or any other environment variable ("env"
variable in non-mod-rewrite url) part.

Example #2:
mod-rewrite off:
mod-rewrite on:

In example #2 only one transformation happens: real template named
"path/to/template" is replaced with nice (to create SEO urls) name
"completely/different/template", which of course doesn't exist on disk.
Using this approach only rewrite listener (which made transformation) knows
what real templates should be used for each of given virtual urls.
If mod-rewrite is turned off, then such url won't work (in case if someone
placed direct link to it). Based on my experience I could say, that, when
mod-rewrite is enabled on site, that it's never going to be disabled.

So, for large projects, when there is very complex url building/parsing
schemes it's hard to always track url compatibility between mod-rewrite and
non-mod-rewrite modes.

Based on all above I propose to use mod-rewrite urls even, when Front-End is
viewed in right frame in administrative console (see attached patch).
Additional Information

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

Powered by Mantis Bugtracker