#2866: TracEnvParentDir breaks when using a particular project name
------------------------------------------+---------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  jonas
     Type:  defect                        |       Status:  new  
 Priority:  normal                        |    Milestone:       
Component:  general                       |      Version:  0.9.4
 Severity:  normal                        |   Resolution:       
 Keywords:                                |  
------------------------------------------+---------------------------------
Old description:

> 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).

New description:

 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).

Comment (by cmlenz):

 (description fixed)

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/2866>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets

Reply via email to