View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000748 | OXID eShop (all versions) | 4.07. Source code, Test | public | 2009-03-26 17:29 | 2012-12-10 13:45 |
| Reporter | marco_steinhaeuser | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.0.1.0 revision 15990 | ||||
| Summary | 0000748: <IfModule> does not work on Suse and other OSses | ||||
| Description | In .htaccess, <IfModule> is used that seems to not work on Suse and diverse other operating systems. http://www.oxid-esales.com/de/resources/forum/installation-und-konfiguration/mod-rewrite#comment-4498 Then need to implement other way how to check if the mod_rewrite is ON or OFF. | ||||
| Tags | No tags attached. | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | 5.2.6 | ||||
| Database Version | 5.0.33 | ||||
|
|
As there are no universal way to assure 100% mod_rewrite detect results i suggest todo this: 1. before setup executes sys req check it should generate custom .htaccess file for admin/ with specified RewriteBase parameter; this file should be deleted after setup is done. Possible tha due to server restrictions this file creation will not be possible; 2. mod_rewrite detection should implement 3 states: green - detection 100% succeded; red - detection 100% proved about disabled mod_rewrite; gray - detection gave no results; in case of red or gray we should provide checkbox when user decides to switch SEO on or off, so in case user wants just to test our software, but server has unknown setup - he still will be able to install. Must be provided info about possibility to switch seo back; 3. if SEO is on and setup succeded custom htaccess must be generated with custom RewriteBase parameter. As we planned to refactor setup (should be task in pipeline) i suggest to implement at once during refactoring. |
|
|
will be fixed during setup refactoring |
|
|
Setup refactoring is planned for Next Major release, and note for solving this issue is added there. So here the bug is closed. |
