[Trac] Re: Spacing around TicketQuery()
But no matter where I've tried putting [[br]], I can't get a break after No results that doesn't give an extra break when there are results. I just want one line before each numbered item (headline). Any thoughts? try this plugin https://projects.optaros.com/trac/oforge/wiki/Dashboard for a better UI. --~--~-~--~~~---~--~~ 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: Spacing around TicketQuery()
sorry but i gaved you the internal url, try http://code.optaros.com/trac/oforge/wiki/Dashboard --~--~-~--~~~---~--~~ 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: Spacing around TicketQuery()
Culapov Andrei wrote: sorry but i gaved you the internal url, try http://code.optaros.com/trac/oforge/wiki/Dashboard That looks nice but doesn't directly address my question. --~--~-~--~~~---~--~~ 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: TracNav-4.0pre7-py2.4 with TracEnvisionTheme-1.0-py2.4
2008/9/30 Eric Shubert [EMAIL PROTECTED]: You're right about the bullets. They could be simply omitted in the TOC as far as I'm concerned. I don't see their purpose there. Please let me/us know if/when you come up with something for this issue. As the bullets are inserted by the Envision theme, I don't see a rather unobtrusive way of removing them. Nevertheless, I recently changed TracNav to construct a properly nested tree for the TOC, which should improve the overall look for such a theme. Could you please test the latest TracNav version from SVN (http://svn.ipd.uka.de/repos/javaparty/JP/trac/plugins/tracnav-0.11/) ? Regards, Thomas -- Thomas Moschny [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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: Trac in trouble.
Noah Kantrowitz wrote: Well work that idea out in more detail. How do you share things, and how do you not share things. Things like plugins probably have to be global just as an implementation detail, but what about other stuff. User preferences should be shared between projects? Etc etc. What about UI, how do you handle submitting a new ticket. Start writing up use cases from other multi-project systems, and showing how to implement them (what options to set) in this model. OK, will do. -- 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: Trac in trouble.
There are plugins for much of this. I'm only to speak to a few specific issues as most of these have been addressed by others in this thread: On Wed, Oct 01, 2008 at 08:51:25AM +0300, Jani Tiainen wrote: snip/ Trouble #3: Multiproject/multirepository support. We have few projects that are actually combination of several (separate) repositories but also there is few libraries that should be linked (and again, cross referenced, see trouble #2) together tightly. (Not loose coupling like external links) There is a multirepository branch that is supposedly in good shape (I don't have need [yet] for a multirepository trac so I haven't used it). I'd love to know when/if this is slated for trunk. Trouble #4: Web based environment creation. There are actually a few of these. TracForge does this. I've also written a trac project templating system, th:TracLegosScript, one component of which is a TTW project creator. Its not really ready for prime-time as there are missing features (importantly, DB type and authorization checking) but most of what I care about is there and I'd be happy to elevate ticket priorities if anyone wishes any of the missing features. There are a few more that I can't remember now. Trouble #5: Userinformation retrieval from our LDAP server. Specially active accounts (since sometimes people come and people leave) and e-mail addresses. Personally, I'd like to see an IUserDataProvider interface to make this more flexible. So the LDAP plugin could provide this, OOTB trac could implement what it currently does as an implementation of this interface, and a multi-project solution could implement whatever it wants (possibly delegating to a master environment). I'm also pro keeping the notion of multiple projects out of trac core. What I would like to see is more infrastructure so that it is easier to write plugins that interface between trac projects. I'm happy to ticket this if its generally wanted and not too contraversial. As a note, I think trac's role is as a good infrastructure to build the ideal bug tracking system. I think trying to get trac core to be OOTB an amazing bug tracker is a bad idea, as folks have different needs (and even projects for the same folks have different needs). This has all been discussed before and I think people are starting to work towards making it easier to get OOTB trac to be easily modified to what a trac administrator wants -- a platform that is easily customizable via plugins, etc. Jeff Hammel The Open Planning Project http://topp.openplans.org IRC: jhammel, k0s --~--~-~--~~~---~--~~ 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: Email Notification Error !
Like you had rightly pointed out .. It was some configuration file problem ! Sorry for the trouble ! But there's another problem now : My subject line for the email always remains Re: #id: Am I supposed to add a 'phrase' of any kind in the ticket_subject_template ? the configuration is more or less the same as the previous file .. except for the email ids .. which should not be much of a relevance now ! My requirement is that the ticket subject/heading comes in the email header : Many thanks ! On Oct 1, 5:54 pm, Emmanuel Blot [EMAIL PROTECTED] wrote: 'SMTP Notification Error') my configuration file : [notification] smtp_from = [email-id] smtp_replyto = [email id] smtp_server = [server name] ticket_subject_template = #.id: As I wrote in the ticket commenthttp://trac.edgewall.org/ticket/3654#comment:6 do not obfuscate your notification configuration, or there's little that can be done to understand the issue. -- Manu --~--~-~--~~~---~--~~ 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: TracLocale and eGroupware
Hi Jens. I'm quite new to Trac, so maybe I just don't know something that you consider really obvious. In that case, forget I said anything, but I get the feeling your are asking the wrong question to the wrong people. How is Trac in anyway related to egroupware? To my knowledge, eGroupware doesn't even use python, so I fail to see how changing a PythonOption would have impact. If it's egroupware that fails, and not Trac, I suggest you contact people knowledgeable about egroupware. 2008/10/1 Jens Kubieziel [EMAIL PROTECTED] Hi, are there any known issues with trac and egroupware? A friend of mine uses trac with mod_python and set 'PythonOption TracLocale de_DE.UTF-8'. After this was done, eGroupwares calendar looks weird (It shows only 5 p.m. and group view was also weird/destroyed). Has anyone experienced this or something similar? How can one workaround it? --~--~-~--~~~---~--~~ 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: Email Notification Error !
2008-10-02 09:09:32,561 Trac[web_ui] ERROR: Failure sending
notification on change to ticket #3: title not defined
Traceback (most recent call last):
File /usr/lib/python2.4/site-packages/trac/ticket/web_ui.py, line
992, in _do_save
tn.notify(ticket, newticket=False, modtime=now)
File /usr/lib/python2.4/site-packages/trac/ticket/notification.py,
line 136, in notify
subject = self.format_subj(summary)
File /usr/lib/python2.4/site-packages/trac/ticket/notification.py,
line 222, in format_subj
/notification
for event in stream:
File /usr/lib/python2.4/site-packages/genshi/template/base.py,
line 520, in _eval
result = _eval_expr(data, ctxt, **vars)
File /usr/lib/python2.4/site-packages/genshi/template/base.py,
line 286, in _eval_expr
retval = expr.evaluate(ctxt)
File /usr/lib/python2.4/site-packages/genshi/template/eval.py,
line 180, in evaluate
return eval(self.code, _globals, {'__data__': data})
File string, line 1, in Expression u'title'
File /usr/lib/python2.4/site-packages/genshi/template/eval.py,
line 306, in lookup_name
val = cls.undefined(name)
File /usr/lib/python2.4/site-packages/genshi/template/eval.py,
line 405, in undefined
raise UndefinedError(key, owner=owner)
UndefinedError: title not defined
I get the above error in the trac.log file !
after i made the change :
ticket_subject_template = $prefix #$ticket.id: $title
On Oct 2, 1:01 pm, Erik Bray [EMAIL PROTECTED] wrote:
On Thu, Oct 2, 2008 at 12:51 PM, Nishanthi [EMAIL PROTECTED] wrote:
Like you had rightly pointed out .. It was some configuration file
problem ! Sorry for the trouble !
But there's another problem now :
My subject line for the email always remains Re: #id:
Am I supposed to add a 'phrase' of any kind in the
ticket_subject_template ?
the configuration is more or less the same as the previous file ..
except for the email ids .. which should not be much of a relevance
now !
My requirement is that the ticket subject/heading comes in the email
header :
Many thanks !
On Oct 1, 5:54 pm, Emmanuel Blot [EMAIL PROTECTED] wrote:
'SMTP Notification Error')
my configuration file :
[notification]
smtp_from = [email-id]
smtp_replyto = [email id]
smtp_server = [server name]
ticket_subject_template = #.id:
Not sure what you're trying to achieve with ticket_subject_template,
but what you have there isn't going to do anything. It should look
something like this:
$prefix #$ticket.id: $title
Which happens to be the default. This will display something like
[Project Name] #123: Ticket subject
--~--~-~--~~~---~--~~
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: Email Notification Error !
i guess it should be :
ticket_subject_template = $prefix #$ticket.id: $summary
thanks anyway for the tip !
On Oct 2, 1:22 pm, Nishanthi [EMAIL PROTECTED] wrote:
2008-10-02 09:09:32,561 Trac[web_ui] ERROR: Failure sending
notification on change to ticket #3: title not defined
Traceback (most recent call last):
File /usr/lib/python2.4/site-packages/trac/ticket/web_ui.py, line
992, in _do_save
tn.notify(ticket, newticket=False, modtime=now)
File /usr/lib/python2.4/site-packages/trac/ticket/notification.py,
line 136, in notify
subject = self.format_subj(summary)
File /usr/lib/python2.4/site-packages/trac/ticket/notification.py,
line 222, in format_subj
/notification
for event in stream:
File /usr/lib/python2.4/site-packages/genshi/template/base.py,
line 520, in _eval
result = _eval_expr(data, ctxt, **vars)
File /usr/lib/python2.4/site-packages/genshi/template/base.py,
line 286, in _eval_expr
retval = expr.evaluate(ctxt)
File /usr/lib/python2.4/site-packages/genshi/template/eval.py,
line 180, in evaluate
return eval(self.code, _globals, {'__data__': data})
File string, line 1, in Expression u'title'
File /usr/lib/python2.4/site-packages/genshi/template/eval.py,
line 306, in lookup_name
val = cls.undefined(name)
File /usr/lib/python2.4/site-packages/genshi/template/eval.py,
line 405, in undefined
raise UndefinedError(key, owner=owner)
UndefinedError: title not defined
I get the above error in the trac.log file !
after i made the change :
ticket_subject_template = $prefix #$ticket.id: $title
On Oct 2, 1:01 pm, Erik Bray [EMAIL PROTECTED] wrote:
On Thu, Oct 2, 2008 at 12:51 PM, Nishanthi [EMAIL PROTECTED] wrote:
Like you had rightly pointed out .. It was some configuration file
problem ! Sorry for the trouble !
But there's another problem now :
My subject line for the email always remains Re: #id:
Am I supposed to add a 'phrase' of any kind in the
ticket_subject_template ?
the configuration is more or less the same as the previous file ..
except for the email ids .. which should not be much of a relevance
now !
My requirement is that the ticket subject/heading comes in the email
header :
Many thanks !
On Oct 1, 5:54 pm, Emmanuel Blot [EMAIL PROTECTED] wrote:
'SMTP Notification Error')
my configuration file :
[notification]
smtp_from = [email-id]
smtp_replyto = [email id]
smtp_server = [server name]
ticket_subject_template = #.id:
Not sure what you're trying to achieve with ticket_subject_template,
but what you have there isn't going to do anything. It should look
something like this:
$prefix #$ticket.id: $title
Which happens to be the default. This will display something like
[Project Name] #123: Ticket subject
--~--~-~--~~~---~--~~
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: Email Notification Error !
On Thu, Oct 2, 2008 at 1:34 PM, Nishanthi [EMAIL PROTECTED] wrote: i guess it should be : ticket_subject_template = $prefix #$ticket.id: $summary thanks anyway for the tip ! Sorry, you're right about that! It should be $summary, not $title. --~--~-~--~~~---~--~~ 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] postgres and environment upgrade failures
Hello, I'm just setting up trac with postgres 8.3.1, and am running into an issue where many plugins are not actually upgrading the database. Base trac install works. I add a plugin (e.g. mastertickets), and get the message to upgrade the environment. I upgrade with trac-admin (trac-admin /path/to/trac/testing upgrade --no-backup), however new tables are not added to the database. If I use sqlite, I do not have this problem. I've figured out that if I patch those plugins (e.g. mastertickets) to call db.commit() (and some places calling rollback) after and insert/updates (typically in the plugins api.py), then the plugin will upgrade correctly. I've searched the mailing list and bugs, and can not find anyone else running into a similar problem, so I am assuming I have done something wrong, or have not configured postgres correctly for trac. I am new to postgres, though have plenty of mysql/mssql/sqlite experience. The postgres install is 100% default, I've simply created a trac user and trac database, and used the postgres connect url in trac.ini. Correction: I actually just found a bug describing the problem: http://trac-hacks.org/ticket/3408 This however, is not limited to mastertickets. My question is, should I just patch these plugins, or is there some postgres configuration item that I am missing in the documentation? Regards, Shane --~--~-~--~~~---~--~~ 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: Email Notification Error !
On Thu, Oct 2, 2008 at 12:51 PM, Nishanthi [EMAIL PROTECTED] wrote: Like you had rightly pointed out .. It was some configuration file problem ! Sorry for the trouble ! But there's another problem now : My subject line for the email always remains Re: #id: Am I supposed to add a 'phrase' of any kind in the ticket_subject_template ? the configuration is more or less the same as the previous file .. except for the email ids .. which should not be much of a relevance now ! My requirement is that the ticket subject/heading comes in the email header : Many thanks ! On Oct 1, 5:54 pm, Emmanuel Blot [EMAIL PROTECTED] wrote: 'SMTP Notification Error') my configuration file : [notification] smtp_from = [email-id] smtp_replyto = [email id] smtp_server = [server name] ticket_subject_template = #.id: Not sure what you're trying to achieve with ticket_subject_template, but what you have there isn't going to do anything. It should look something like this: $prefix #$ticket.id: $title Which happens to be the default. This will display something like [Project Name] #123: Ticket subject --~--~-~--~~~---~--~~ 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: TracNav-4.0pre7-py2.4 with TracEnvisionTheme-1.0-py2.4
Thomas Moschny wrote: 2008/9/30 Eric Shubert [EMAIL PROTECTED]: You're right about the bullets. They could be simply omitted in the TOC as far as I'm concerned. I don't see their purpose there. Please let me/us know if/when you come up with something for this issue. As the bullets are inserted by the Envision theme, I don't see a rather unobtrusive way of removing them. Nevertheless, I recently changed TracNav to construct a properly nested tree for the TOC, which should improve the overall look for such a theme. Could you please test the latest TracNav version from SVN (http://svn.ipd.uka.de/repos/javaparty/JP/trac/plugins/tracnav-0.11/) ? Regards, Thomas Looks much nicer, thanks. One thing though. When I installed it globally (in site-packages folder) trac couldn't find the plugin. I tried both tracnav.tracnav.tracnav = enabled and tracnav.* = enabled in trac.ini, but either worked. However, when I put it in the project's plugins folder it found it ok. Some rookie error on my part perhaps? I downloaded the plugin, and built it with python setup.py bdist_egg, then copied the dist/TracNav*.egg to its destination, and renamed the 4.0pre7 egg. Any idea where I might have goofed? -- -Eric 'shubes' --~--~-~--~~~---~--~~ 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] MultipleRepositorySupport install error
I followed http://trac.edgewall.org/wiki/MultipleRepositorySupport I recieve the below error and warning when I load the trac page cgi- bin/trac.cgi/browser Warning: Can't synchronize with the repository (Unsupported version control system hg: Can't find an appropriate component, maybe the corresponding plugin was not enabled? ). Look in the Trac log for more information. Trac Error Unsupported version control system hg: Can't find an appropriate component, maybe the corresponding plugin was not enabled? It is a fedora core 5 system. Another sympton is that when I try to run trac-admin /var/trac resync I receive an error that a file in the repository is from an untrusted user and group? How can I fix this? (I checked that I could import mercurial under python and saw that I had the 4 components of TracMercurial 0.12.0.3dev enabled). What should I send next for debugging? Thanks for your time. --~--~-~--~~~---~--~~ 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] Moving to trac
Hi please pardon me for any ignorance, as this is my first encounter with trac and on this mailing list. Now back to business. I have to move data from existing legacy bugtracking system, (which is Microsoft Access based and contains more than 100,000 tickets), to trac 0.11 + sqlite3. Now after looking at all the schemas in MS Access, I have created a small application, which will go through existing tickets and views one by one in access db and insert records into trac 'ticket' and trac 'ticket_custom' tables. Now question is, am I doing it the right way, or missing some thing. Another question arises is that the priority in legacy Ms Access db is 'High,Normal,Low'. So I want to change the trac's priority drop down values to ones in access db. I tried something like this in trac.ini where there are default values for priority (please ignore typo for priority) default_priority = 'low' default_priority.options = High|NormalLow but this didnt work. Although I changed some bits in components table, and can have my own component and mile stone values. Any idea if you see problem with my approach to migration, please ring the bell. Any help will be appreciated. Regards --~--~-~--~~~---~--~~ 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: Moving to trac
On Thu, Oct 2, 2008 at 4:26 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi please pardon me for any ignorance, as this is my first encounter with trac and on this mailing list. Now back to business. I have to move data from existing legacy bugtracking system, (which is Microsoft Access based and contains more than 100,000 tickets), to trac 0.11 + sqlite3. Now after looking at all the schemas in MS Access, I have created a small application, which will go through existing tickets and views one by one in access db and insert records into trac 'ticket' and trac 'ticket_custom' tables. Now question is, am I doing it the right way, or missing some thing. Another question arises is that the priority in legacy Ms Access db is 'High,Normal,Low'. So I want to change the trac's priority drop down values to ones in access db. I tried something like this in trac.ini where there are default values for priority (please ignore typo for priority) default_priority = 'low' default_priority.options = High|NormalLow but this didnt work. Although I changed some bits in components table, and can have my own component and mile stone values. Any idea if you see problem with my approach to migration, please ring the bell. Any help will be appreciated. Regards Your approach for migrating the tickets themselves sounds just fine. I don't know if you're trying to also import ticket histories, but that's what the ticket_change table is for. Otherwise, I suppose your tickets will just be treated like new tickets, and any changes after the move to Trac will be recorded accordingly. As for priorities the way you were trying to do it won't work at all. The default_priority option only sets the default value for the priority field in a ticket. It's not a custom field, and its options aren't set that way. You can edit the priorities through Trac's admin interface. Look under the Ticket section of the admin interface and select Priority. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
