Gary Oberbrunner wrote:
Sarah George wrote:
I've been working on the same thing: Getting trac 0.11 usable. Two of
your problems might be solved by knowing there seems to be a new
setting in trac.ini called "base_url"... try making sure that's set.
What should this be set to in 0.11? Complete URL including protocol &
host?
In our case that would not work, since our trac is accessible via two
different hostnames; trac-generated URLs have to preserve the correct
one.
Well, the base_url is used only for generating some absolute URLs
outside of the scope of a client request, like when creating
notification mails.
The problem with the "my account" link that Dave mentioned is probably
related to a plugin using the old API for generating the URL (*)
-- Christian
(*) For generating URLs, one should do req.abs_href (absolute URLs) or
req.href, instead of env.abs_href or env.href, as the latter will use
the base_url setting. By using req methods, the protocol/hostname/base
which was used by the client to access Trac will be correctly reused.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
