[Trac] Re: doxygen plugin
my questions are: how to install doxygenplugin? how to add doxygen to trac application? Most of the Trac plugins are available from http://trac-hacks.org --~--~-~--~~~---~--~~ 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: TicketQuery macro and Intertrac prefixes
Stephen Moretti wrote: Is it possible to use TicketQuery across trac environments using Intertrac prefixes? I guess I can do [othertrac:query:somequerystring link to query], but I'd like to have the query appear in the wiki page as per the TicketQuery macro. I guess that will never be possible for cross-environment queries, but that syntax will work in a multiple projects per environment setup (which is of course at this point not yet implemented). -- 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] TicketQuery macro and Intertrac prefixes
Is it possible to use TicketQuery across trac environments using Intertrac prefixes? I guess I can do [othertrac:query:somequerystring link to query], but I'd like to have the query appear in the wiki page as per the TicketQuery macro. Regards Stephen --~--~-~--~~~---~--~~ 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: Plugin tutorial
Thanks, Jani. I DO understand the concept of a wiki, believe me! ;-) I just thought that, given my lack of experience with trac, I wouldn't be best placed to judge exactly how that page should be edited. I hoped that there would be others on the list with enough experience to update the tutorial based on what I've said here - maybe you're just that very person! - Bobby 2008/11/19 Jani Tiainen [EMAIL PROTECTED] bobbykjack kirjoitti: Yup - the python version clash was to blame. Would be nice if this were more obvious (not sure how possible that is) and were mentioned in the troubleshooting section of the linked article (as well as the main body text). The tutorial should also be updated to mention the .ini file change, and the wording re: restart server should definitely be clarified. Hint of the day for additions: It's a wiki... :) I haven't checked 0.11 version of that plugin tutorial, it's based on that 0.10 version but should contain some upgraded information specially since you shouldn't be using 0.10 in first place... Maybe I should rewrite whole article, maybe add some bacon with eggs... -- Jani Tiainen Tein sein mihin näillä lahjoilla pystyin. Tein sen, en yhtään enempää. - Martti Servo Napander --~--~-~--~~~---~--~~ 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] modify resultion options based on other field.
Hi all, I think this is a possible option between some of the plugins, but I don't see the path out of the forest. Any thoughts. basically, I want to allow a special resolution if the ticket type =something special or for that matter, based on any other field. Built in filed is sufficieint, custom field is a nice option. Between the TicketValidator, the TicketExt, the BlackMagic ticket tweaks, and the AdvancedTicketWorkflow plugin it seems like it could be done with some combination, but I am not seeing the solution. I suspect it is heavily dependent on the AdvancedTicketWorkflow triage option. Any thoughts? --~--~-~--~~~---~--~~ 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: TicketQuery macro and Intertrac prefixes
2008/11/19 Christian Boos [EMAIL PROTECTED] Stephen Moretti wrote: Is it possible to use TicketQuery across trac environments using Intertrac prefixes? I guess I can do [othertrac:query:somequerystring link to query], but I'd like to have the query appear in the wiki page as per the TicketQuery macro. I guess that will never be possible for cross-environment queries, but that syntax will work in a multiple projects per environment setup (which is of course at this point not yet implemented). Hmm I guess I'd need to really be using a common database (multiple schemas) for all the environments and make a macro that basically replicates ticketquery but can interrogate multiple schema, a la http://trac.edgewall.org/wiki/TracMultipleProjects/MultipleEnvironmentsSingleDatabase On a tangent Whats the issue with MySQL support? Is it down to the MySQL/Python Connector? Is that correct? Stephen --~--~-~--~~~---~--~~ 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: Upgrade existent Trac installation
On Nov 19, 2008, at 7:42 AM, Reynier Perez Mira wrote: Doing subversion checkout from http://svn.edgewall.org/repos/trac/tags/trac-0.11.2.1/ to /tmp/easy_install-M_ZbJw/trac-0.11.2.1 svn: /root/.subversion/servers:78: Comment must start in the first column It looks like you made a mistake when editing the servers file. What does line 78 look like? -- Name: Dave Huang | Mammal, mammal / their names are called / INet: [EMAIL PROTECTED] | they raise a paw / the bat, the cat / FurryMUCK: Dahan | dolphin and dog / koala bear and hog -- TMBG Dahan: Hani G Y+C 33 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA + PL++ --~--~-~--~~~---~--~~ 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: TicketQuery macro and Intertrac prefixes
On Nov 19, 10:45 am, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/11/19 Christian Boos [EMAIL PROTECTED] Stephen Moretti wrote: Is it possible to use TicketQuery across trac environments using Intertrac prefixes? I guess I can do [othertrac:query:somequerystring link to query], but I'd like to have the query appear in the wiki page as per the TicketQuery macro. I guess that will never be possible for cross-environment queries, but that syntax will work in a multiple projects per environment setup (which is of course at this point not yet implemented). Hmm I guess I'd need to really be using a common database (multiple schemas) for all the environments and make a macro that basically replicates ticketquery but can interrogate multiple schema, a lahttp://trac.edgewall.org/wiki/TracMultipleProjects/MultipleEnvironmen... On a tangent Whats the issue with MySQL support? Is it down to the MySQL/Python Connector? Is that correct? Stephen I don't see why you would need a 1 db/multiple project schema. The TracHours plugin has a multi-project query which I beleive works in the standard mutli-project setup. It does modify the database for it's purpose, but I think it could done. --~--~-~--~~~---~--~~ 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: TicketQuery macro and Intertrac prefixes
On Wed, Nov 19, 2008 at 09:17:00AM -0800, [EMAIL PROTECTED] wrote: On Nov 19, 10:45 am, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/11/19 Christian Boos [EMAIL PROTECTED] Stephen Moretti wrote: Is it possible to use TicketQuery across trac environments using Intertrac prefixes? I guess I can do [othertrac:query:somequerystring link to query], but I'd like to have the query appear in the wiki page as per the TicketQuery macro. I guess that will never be possible for cross-environment queries, but that syntax will work in a multiple projects per environment setup (which is of course at this point not yet implemented). Hmm I guess I'd need to really be using a common database (multiple schemas) for all the environments and make a macro that basically replicates ticketquery but can interrogate multiple schema, a lahttp://trac.edgewall.org/wiki/TracMultipleProjects/MultipleEnvironmen... On a tangent Whats the issue with MySQL support? Is it down to the MySQL/Python Connector? Is that correct? Stephen I don't see why you would need a 1 db/multiple project schema. The TracHours plugin has a multi-project query which I beleive works in the standard mutli-project setup. It does modify the database for it's purpose, but I think it could done. To be fair, the TracHours multi-project query is fairly ad-hoc; it also does HTTP requests to get the RSS instead of reading from the DB which is less than ideal. I don't apologize for either of these things, mainly because no framework exists (to my knowledge?) to do this sort of thing in trac in a standardized way. I highly desire such a standardization of dialect whereby trac instances can talk to each other and plugins can talk to each other. But I'm realistic in that not only is this difficult to design, I think any solution (or even the idea of a solution) would be very contraversial. So roll your own? Jeff --~--~-~--~~~---~--~~ 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: Problem setting up track with Apache 2.2
On Nov 19, 5:22 am, Graham Dumpleton [EMAIL PROTECTED] wrote: Did you actually look in the Apache error log file to see if there was any useful information? Nope, I am pretty new to Apache as well. Where can I find those? Try setting: PythonDebug On That way any mod_python/Python error will show in browser rather than Apache error log. Ah great. As I had already thought tonight, the problem is a ‘permission denied’, because the trac directory is root-owned. And indeed simply changing its owner to wwwrun solved the issue. Thanks! H. P.S. Is there some way to follow this group in a proper mail/news reader, such as via Gmane? I’d rather not get all the mails but view it in a usenet-like fashion. --~--~-~--~~~---~--~~ 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: Fwd: Serach respond time in Trac
2008/11/18 [EMAIL PROTECTED]: Hi Thank you your help. Its only trac search that are slow. Isnt running any plugins. I customize this trac file /usr/lib/python2.3/site-packages/trac/ticket/api.py ...snip... I couldn't really read your formatting. Posting a diff would be better. And then i used to this customize file. I tried to trac search in Linux server again.It respond 20 seconds Its fast than berore. But its tentative action. What do you this this customize? Do you have patch for Trac serach repond or improve this poblem Trac version? If you know this problem , please teach me. Not sure why it would be so slow. I'd suggest upgrading Trac to 0.11.2 and seeing if that helps. --~--~-~--~~~---~--~~ 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: TicketQuery macro and Intertrac prefixes
On Wed, Nov 19, 2008 at 12:22 PM, Jeff Hammel [EMAIL PROTECTED] wrote: On Wed, Nov 19, 2008 at 09:17:00AM -0800, [EMAIL PROTECTED] wrote: I don't see why you would need a 1 db/multiple project schema. The TracHours plugin has a multi-project query which I beleive works in the standard mutli-project setup. It does modify the database for it's purpose, but I think it could done. To be fair, the TracHours multi-project query is fairly ad-hoc; it also does HTTP requests to get the RSS instead of reading from the DB which is less than ideal. I don't apologize for either of these things, mainly because no framework exists (to my knowledge?) to do this sort of thing in trac in a standardized way. I highly desire such a standardization of dialect whereby trac instances can talk to each other and plugins can talk to each other. But I'm realistic in that not only is this difficult to design, I think any solution (or even the idea of a solution) would be very contraversial. So roll your own? Jeff Assuming that each environment is located under a single parent directory, why not just go through each environment in the parent directory and open_environment() on it? I have lots of scripts and a few plugins that gather data from all environments on the server in this way. Query each environment's DB separately, and then combine the data in an intelligent way--that part depends entirely on what you're querying and what you intend to do with the data. Of course, that assumes all the environments are on the same server. If not, that's what the XML-RPC plugin is good for, though it certainly doesn't give you the same flexibility. --~--~-~--~~~---~--~~ 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: Problem setting up track with Apache 2.2
On Nov 19, 10:19 pm, Hendrik Maryns [EMAIL PROTECTED] wrote: On Nov 19, 5:22 am, Graham Dumpleton [EMAIL PROTECTED] wrote: Did you actually look in the Apache error log file to see if there was any useful information? Nope, I am pretty new to Apache as well. Where can I find those? Depends on where/how you have Apache installed. You can try running 'httpd -V'. For Apache 2.2 this will dump out, amongst other stuff: -D HTTPD_ROOT=/usr/local/apache-2.2.4 -D DEFAULT_ERRORLOG=logs/error_log Join the paths together and hopefully you have your error log file. Try setting: PythonDebug On That way any mod_python/Python error will show in browser rather than Apache error log. Ah great. As I had already thought tonight, the problem is a ‘permission denied’, because the trac directory is root-owned. And indeed simply changing its owner to wwwrun solved the issue. Thanks! H. P.S. Is there some way to follow this group in a proper mail/news reader, such as via Gmane? I’d rather not get all the mails but view it in a usenet-like fashion. Have you tried: http://groups.google.com/group/trac-users Graham --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
