That's no good. Two things:
1) The suggested "Python Option TracUriRoot /" should be PythonOption
to be accepted
2) When I add that to my conf file, trac does not work at all - it
gives an error message.

Here's the relevant parts of the Apache conf if that helps:

LoadModule python_module modules/mod_python.so
...
<Directory ..../trac>
        SetHandler mod_python
        PythonInterpreter main_interpreter
        PythonHandler trac.web.modpython_frontend
        PythonOption TracEnv "...\trac"
</Directory>
....
<Location /trac>
                Require group Trac
</Location>

Adding your suggested directive in the Directory is what I tried.


On Oct 19, 12:53 am, Noah Kantrowitz <[email protected]> wrote:
> You probably need to add "Python Option TracUriRoot /" to your config.
>
> --Noah
>
> On Oct 18, 2009, at 1:48 PM, Jake Stone wrote:
>
>
>
> > Hello again,
> > Does anybody have a response on this? No idea what to do here...
> > Thanks!
>
> >> Hello!
>
> >> I'm running Trac on Windows with Apache 2.2 and mod_python, and while
> >> accessing "/trac/wiki" looks fine, accessing just "/trac" from Apache
> >> does not correctly load the CSS files and other goodies to make the
> >> site look nice. Below are the offending log lines:
>
> >> [12/Oct/2009:03:07:39 -0500] "GET /trac HTTP/1.1" 301 238
> >> [12/Oct/2009:03:07:39 -0500] "GET /trac/ HTTP/1.1" 200 7149
> >> [12/Oct/2009:03:07:39 -0500] "GET /trac/chrome/common/css/trac.css
> >> HTTP/1.1" 404 4099
> >> [12/Oct/2009:03:07:39 -0500] "GET /trac/chrome/common/css/wiki.css
> >> HTTP/1.1" 404 4099
> >> [12/Oct/2009:03:07:39 -0500] "GET /trac/chrome/common/js/jquery.js
> >> HTTP/1.1" 404 4099
> >> [12/Oct/2009:03:07:39 -0500] "GET /trac/chrome/common/js/search.js
> >> HTTP/1.1" 404 4099
> >> [12/Oct/2009:03:07:39 -0500] "GET /trac/chrome/common/js/trac.js  
> >> HTTP/
> >> 1.1" 404 4097
> >> [12/Oct/2009:03:07:40 -0500] "GET /trac/chrome/common/js/search.js
> >> HTTP/1.1" 404 4099
> >> [12/Oct/2009:03:07:41 -0500] "GET /trac/chrome/site/
> >> your_project_logo.png HTTP/1.1" 404 4106
> >> [12/Oct/2009:03:07:41 -0500] "GET /trac/chrome/common/
> >> trac_logo_mini.png HTTP/1.1" 404 4105
>
> >> When accessing "/trac/wiki", those same log lines are:
>
> >> [12/Oct/2009:03:06:56 -0500] "GET /trac/wiki/report HTTP/1.1" 200  
> >> 7651
> >> [12/Oct/2009:03:06:58 -0500] "GET /trac/wiki/chrome/common/js/trac.js
> >> HTTP/1.1" 200 2174
> >> [12/Oct/2009:03:06:58 -0500] "GET /trac/wiki/chrome/common/css/
> >> report.css HTTP/1.1" 200 5341
> >> [12/Oct/2009:03:06:58 -0500] "GET /trac/wiki/chrome/common/js/
> >> search.js HTTP/1.1" 200 2315
> >> [12/Oct/2009:03:06:58 -0500] "GET /trac/wiki/chrome/common/css/
> >> trac.css HTTP/1.1" 200 17028
> >> [12/Oct/2009:03:06:58 -0500] "GET /trac/wiki/chrome/common/css/
> >> code.css HTTP/1.1" 200 4611
> >> [12/Oct/2009:03:06:58 -0500] "GET /trac/wiki/chrome/common/js/
> >> jquery.js HTTP/1.1" 200 31043
> >> [12/Oct/2009:03:06:59 -0500] "GET /trac/wiki/chrome/common/
> >> trac_logo_mini.png HTTP/1.1" 200 689
> >> [12/Oct/2009:03:06:59 -0500] "GET /trac/wiki/chrome/common/
> >> topbar_gradient.png HTTP/1.1" 200 350
> >> [12/Oct/2009:03:06:59 -0500] "GET /trac/wiki/chrome/common/dots.gif
> >> HTTP/1.1" 200 50
> >> [12/Oct/2009:03:06:59 -0500] "GET /trac/wiki/chrome/common/
> >> topbar_gradient2.png HTTP/1.1" 200 342
> >> [12/Oct/2009:03:06:59 -0500] "GET /trac/wiki/chrome/site/
> >> your_project_logo.png HTTP/1.1" 404 4029
>
> >> So clearly, loading from the home page needs to add /wiki/ in there  
> >> to
> >> correctly get the chrome CSS files and other data. I could make  
> >> apache
> >> fix this manually, but that strikes me as inefficient - any ideas?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to