symlinked public web assets conflict with mod_rewrite rules if frontControllerScript is suppressed

there was start of a discussion on a solution here http://groups.google.com/group/seagull_general/browse_thread/thread/271d5aa8e23b87b4/7e35be4f0c0509ed?lnk=gst&

I can see and tested 2 possible solutions, which should work fine for windows users (that was the pb mentioned in above discussion).

1. have the symlink (or copy for Win users) prepended by an "_", e.g.

/path/to/sgl/www/_foo > /path/to/sgl/modules/foo/www

and modify appropriate calls in code to reflect this path.

2. add a placeholder file called e.g. norewrite.txt in each module's web assets folder and modify add a RewriteCond to check if this file exists

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d [OR]
RewriteCond %{REQUEST_FILENAME}norewrite\.txt -f
RewriteRule ^(.*) index.php [L]

This second solution works pretty fine as well, and I would recommend it for existing projects (thus you don't have to upgrade to next SGL version).

I would implement first solution in sgl 0.6.5.

Juju, isn't it easier to place .htaccess file to /path/to/sgl/www/module with following content:

RewriteEngine off

fixed in 0.6.5 [3805]

see TroubleShooting/RemovingIndex.php

moving too 0.9.x

Dima, not it won't work as it will prevent mod_rewrite to work when trying to load your foo module.

fixed in latest .htaccess-cleanUrl