TracEnvParentDir breaks when using a particular project name

[michael@…]

This report concerns Trac served by Apache with mod_python. Here is an example for the problem: Suppose you have configured Apache to serve Trac projects at ​http://localhost/trac/parentdirtest/projectname using the TracEnvParentDir directive. The config would look like:

        <Location /trac/parentdirtest>
                SetHandler mod_python
                PythonHandler trac.web.modpython_frontend
                PythonOption TracEnvParentDir /srv/trac/parentdirtest
                PythonOption TracUriRoot /trac/parentdirtest
        </Location>

With this example you would access projects at http://localhost/trac/parentdirtest projectname. When using a non-existing project name or none at all, Trac will show you the project listing.

This works fine as long as the directory containing the Trac projects, /srv/trac/parentdirtest/ in this case doesn't contain a project called parentdirtest. If it does, you can still access the other projects, but instead of the project listing at http://localhost/trac/parentdirtest you will see something like a broken Trac project (see attached screenshot).

[Christopher Lenz]

(description fixed)

[osimons]

Tested this with current 0.11b1+ and can't recreate it. So many things have changed since 0.9.4, that unless someone can recreate this issue with a recent/semi-recent version, I'm going to close this ticket as 'worksforme'.

[osimons]

Closing as 'worksforme' as I can't re-create the problem using a current version.