On Monday, April 8, 2019 at 11:04:23 AM UTC-4, pcottrill wrote:
>
> Ryan,
>
>  
>
> Thanks for your response.
>
>  
>
> We actually do us a virtualhost configuration, with each project having 
> its own location.
>
> We also have an alias for htdocs/common and htdoc/shared, but plugins are 
> not included in that configuration. 
>
>  
>
> Below is an example of the virtualhost configuration.
>
> I was not sure about the TracEnvParentDir configuration; would that make a 
> difference in what we are experiencing?
>
>  
>
> <Location /project_a>
>
>            SetHandler mod_python
>
>            PythonInterpreter main_interpreter
>
>            PythonHandler trac.web.modpython_frontend
>
>            PythonOption TracEnv /home/trac/project_a
>
>            PythonOption TracEnvParentDir /home/trac
>
>            PythonOption TracUriRoot /project_a
>
>            PythonOption TracLocale en_US.UTF8
>
>            PythonOption PYTHON_EGG_CACHE /home/trac/python_egg_cache
>
>            Order allow,deny
>
>            Allow from all
>
>         </Location>
>
>         <Location /project_a /login>
>
>           AuthType Basic
>
>           AuthName "New Trac Project"
>
>           AuthUserFile /home/trac.htpasswd
>
>          # Require valid-user
>
>         </Location>
>
>  
>
> -- Patty
>

You'll want to remove "PythonOption TracEnvParentDir /home/trac" for a 
configuration block that just serves a single project. Setting TracEnv is 
sufficient. I don't think that change will fix your plugin loading issue, 
but give it a check after making that change just in case.

I don't have much experience with mod_python, so maybe someone else will 
chime in here.

What is your mod_python version? This option looks applicable to your 
situation:
http://modpython.org/live/current/doc-html/directives.html#pythoninterpperdirective
It looks like that option should be specified at server config scope, i.e. 
outside the Location directive, and then remove "PythonInterpreter 
main_interpreter" within your Location directives.

Or, it might be sufficient to just give a unique name to each 
PythonInterpreter directive. Such as:

PythonInterpreter project_a

See also: 
http://modpython.org/live/current/doc-html/pythonapi.html#pyapi-interps

I don't know the history behind using "PythonInterpreter main_interpreter" 
in the configuration samples on the ModPython page, and whether that is 
entirely due to the issue described here:
https://trac.edgewall.org/wiki/TracModPython#Subversionissues

After making any changes to the python interpreter configuration, we'll 
need to be on the lookout for any undesirable behavior.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to