[Trac] Re: Problems after upgrade to HEAD
Sarah George [EMAIL PROTECTED] writes: 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. You're right; that helped, thanks! Now to solve the other issues... -- Dave Abrahams Boost Consulting www.boost-consulting.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
David Abrahams wrote: Christian Boos [EMAIL PROTECTED] writes: David Abrahams wrote: Noah Kantrowitz [EMAIL PROTECTED] writes: span class=c_wordint/span span class=c_identifiersomething_result/span span class=c_operator=/span span class=c_identifiermodel/ span ... Do you have the most recent Genshi? Should be 0.3.6 I think. I'm using a recent snapshot of their head, I think. It reports version '0.4'. ... and that can be anything between r317 and the latest. You must use at least r461 of the trunk, or the released 0.3.6. I pulled it from the svn HEAD on January 15. If you install the package by first creating an egg, or at least by doing a `python setup.py develop`, then you'll be able to see the actual version used by Trac in the About page (provided you have the CONFIG_VIEW permission, e.g. when you're logged as the Trac administrator). You should see something like 0.4dev-rXXX, please check that the XXX is = 461. -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
Christian Boos [EMAIL PROTECTED] writes about genshi: You should see something like 0.4dev-rXXX, please check that the XXX is = 461. It's 485 -- Dave Abrahams Boost Consulting www.boost-consulting.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
David Abrahams wrote: Christian Boos [EMAIL PROTECTED] writes about genshi: You should see something like 0.4dev-rXXX, please check that the XXX is = 461. It's 485 Sorry for the trouble, I can reproduce the issue now. I also realized that there was already a ticket filed about that, http://trac.edgewall.org/ticket/4505 I happen to use the Pygments highlighter those days, and this one works flawlessly with Trac 0.11, that's why I've missed the issue. But it happens for anything else than Pygments... -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
Christian Boos [EMAIL PROTECTED] writes: David Abrahams wrote: Christian Boos [EMAIL PROTECTED] writes about genshi: You should see something like 0.4dev-rXXX, please check that the XXX is = 461. It's 485 Sorry for the trouble, I can reproduce the issue now. I also realized that there was already a ticket filed about that, http://trac.edgewall.org/ticket/4505 I happen to use the Pygments highlighter those days, and this one works flawlessly with Trac 0.11, that's why I've missed the issue. But it happens for anything else than Pygments... Is that something I can install and easily configure trac to use? I'm not particularly attached to whatever highlighter it is currently using. -- Dave Abrahams Boost Consulting www.boost-consulting.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
David Abrahams wrote: Christian Boos [EMAIL PROTECTED] writes: ... I happen to use the Pygments highlighter those days, and this one works flawlessly with Trac 0.11, that's why I've missed the issue. But it happens for anything else than Pygments... Is that something I can install and easily configure trac to use? I'm not particularly attached to whatever highlighter it is currently using. ... but you probably will once you've tried Pygments :-) It's very easy to install and there's no setup configuration to do in Trac, as it will preferentially use Pygments. See http://pygments.pocoo.org/download/ Pygments version 0.6 or 0.7dev should work fine with recent Trac 0.11. Before giving a try to Pygments, you should also try out my fix for the issue (r4597). -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
David Abrahams wrote: Christian Boos [EMAIL PROTECTED] writes: ... but you probably will once you've tried Pygments :-) It's very easy to install and there's no setup configuration to do in Trac, as it will preferentially use Pygments. See http://pygments.pocoo.org/download/ Pygments version 0.6 or 0.7dev should work fine with recent Trac 0.11. Before giving a try to Pygments, you should also try out my fix for the issue (r4597). Works. But now, why should I try pygments? Pygments already supports more languages than the other highlighters. It also knowns about a bunch of templating languages (e.g. JSP) and can highlight not only the markup but also the embedded code expressions. Plus there's the possibility to select your favorite highlighting theme in the Trac preferences ;) -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
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. I tried just the part after the host, like /trac, but still had some problems... -- Gary --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
On Wednesday 17 January 2007 3:07 pm, Christian Boos wrote: 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. Besides the fact that this is currently not working reliably for trac trunk , see http://trac.edgewall.org/ticket/4287 ;) Links in RSS feeds from my site e.g. are all relative (missing the host and protocol part), despite having set base_url. - Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
Noah Kantrowitz [EMAIL PROTECTED] writes: span class=c_wordint/span span class=c_identifiersomething_result/span span class=c_operator=/span span class=c_identifiermodel/ span ... Do you have the most recent Genshi? Should be 0.3.6 I think. I'm using a recent snapshot of their head, I think. It reports version '0.4'. -- Dave Abrahams Boost Consulting www.boost-consulting.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
David Abrahams wrote: Noah Kantrowitz [EMAIL PROTECTED] writes: span class=c_wordint/span span class=c_identifiersomething_result/span span class=c_operator=/span span class=c_identifiermodel/ span ... Do you have the most recent Genshi? Should be 0.3.6 I think. I'm using a recent snapshot of their head, I think. It reports version '0.4'. ... and that can be anything between r317 and the latest. You must use at least r461 of the trunk, or the released 0.3.6. -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
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. -- Sarah On 1/17/07, David Abrahams [EMAIL PROTECTED] wrote: David Abrahams [EMAIL PROTECTED] writes: David Abrahams [EMAIL PROTECTED] writes: This was added in trunk as a new handler at /export that handles the raw formatted stuff. Hi Noah, Could you give me a little more detail, please? Updating to the latest development version of Trac on my FreeBSD server is likely to be nontrivial, so I'd like to get a clearer picture of what you mean before I make the investment. Well, what the heck; I just went ahead and did it. I had to fool my ports system into thinking trac-0.11dev came from its usual sources, and there were a few anxious moments while I had to find and install genshi, but all is well now. Looks like I spoke too soon... Naturally I can't expect everything to be perfect with unreleased software, but I would really appreciate a hand with this because we need the new feature that we upgraded for :). We have found 4 problems so far, only one of which we know how to address (the old Admin module needed to be removed). The others are: - Syntax highlighting is broken. It seems like all the HTML generated by the syntax highlighter is getting rendered literally, so, e.g., I see this in my browser: span class=c_wordint/span span class=c_identifiersomething_result/span span class=c_operator=/span span class=c_identifiermodel/span ... - Links to tickets in emails are presented relative to the server root, e.g., as /ticket/51#comment:1 instead of the more useful https://boost-consulting.com/trac/company/ticket/51#comment:1 - The my account link leads to /account rather than $TRAC_ROOT/account. IOW, for the trac above, it takes me to https://boost-consulting.com/account but it should lead to https://boost-consulting.com/trac/company/account Any help you can offer would be greatly appreciated! Thanks in advance, -- Dave Abrahams Boost Consulting www.boost-consulting.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: Problems after upgrade to HEAD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 16, 2007, at 7:17 PM, David Abrahams wrote: David Abrahams [EMAIL PROTECTED] writes: David Abrahams [EMAIL PROTECTED] writes: This was added in trunk as a new handler at /export that handles the raw formatted stuff. Hi Noah, Could you give me a little more detail, please? Updating to the latest development version of Trac on my FreeBSD server is likely to be nontrivial, so I'd like to get a clearer picture of what you mean before I make the investment. Well, what the heck; I just went ahead and did it. I had to fool my ports system into thinking trac-0.11dev came from its usual sources, and there were a few anxious moments while I had to find and install genshi, but all is well now. Looks like I spoke too soon... Naturally I can't expect everything to be perfect with unreleased software, but I would really appreciate a hand with this because we need the new feature that we upgraded for :). We have found 4 problems so far, only one of which we know how to address (the old Admin module needed to be removed). The others are: - Syntax highlighting is broken. It seems like all the HTML generated by the syntax highlighter is getting rendered literally, so, e.g., I see this in my browser: span class=c_wordint/span span class=c_identifiersomething_result/span span class=c_operator=/span span class=c_identifiermodel/ span ... Do you have the most recent Genshi? Should be 0.3.6 I think. - Links to tickets in emails are presented relative to the server root, e.g., as /ticket/51#comment:1 instead of the more useful https://boost-consulting.com/trac/company/ticket/51#comment:1 - The my account link leads to /account rather than $TRAC_ROOT/account. IOW, for the trac above, it takes me to https://boost-consulting.com/account but it should lead to https://boost-consulting.com/trac/company/account Any help you can offer would be greatly appreciated! Thanks in advance, -- Dave Abrahams Boost Consulting www.boost-consulting.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFrbL4A9fEp2eRsU8RAuLlAJ4or0sLfx2+9s58vfEU4rP9+XYwFQCgzWN6 iY+qAf9MUb2CTwXbkmW2DN0= =l2fT -END PGP SIGNATURE- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
