[Trac] Re: modifying trac.db directly
[EMAIL PROTECTED] wrote: I want to change an assignee in a bunch of tickets, and it would be a lot easier to do using a straight connection to the sqliite db (via python script or excellent GUI tools like Sqlite Administrator or Sqlite Expert). It's just a one time thing. Just wondering if there are any gotchas. Did some tests in a sandbox and seemed fine. Thanks in advance. No, you should be fine changing the assignee in the database. -- Matt Good --~--~-~--~~~---~--~~ 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: Customizing notification Subject
I searched for "format_subj" in notification.py, and it doesn't exist anywhere. Did you mean "format_header"? If so, I'm not clear (not even close) on where to insert the above. notification code is split in two files: trac/notification.py for generic code, trac/ticket/notification.py for ticket-related data Look around line 188 in the latter file (trac-0.10.3) Cheers, 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: Customizing notification Subject
Marc-Antoine Zizka wrote: > Is there an easy way to modify the notification Subject line to include > a ticket field? We have a custom field, "State". We'd like the > notification Subject to include the State field and follow this syntax > as much as possible: > > [Type] [Ticket] [State]: [Summary] > > Example: > > CR #4 Assigned: Change background color from black to chartreuse. > > > Can this easily be done? I'm looking at notification.py and it isn't > clear to me (as a non-programmer) how to do this. I would appreciate > any guidance and details. There is no "easy" way. You'll have to change the 'format_subj' method in notification.py. You would want something like this: return '%s #%s %s: %s' % (self.ticket['type'], self.ticket.id, self.ticket['status'], self.ticket['summary']) If you have the smtp_subject_prefix set to something or simply not part of your configuration (so the project name is added to each email), then you'll want to change the other return value in a similar way, only adding the prefix first. Thank you for your reply. I searched for "format_subj" in notification.py, and it doesn't exist anywhere. Did you mean "format_header"? If so, I'm not clear (not even close) on where to insert the above. Jen --~--~-~--~~~---~--~~ 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: Possible to use plain text instead of wikiformatting?
Christian Boos wrote: A middle term would be to simply respect newlines, as we already do for changeset messages. That would avoid most of the issues. I wanted to do that for 0.11 anyway, but wondered about what the default should be. Like we have now, or escape newlines enabled by default? I'd like escape-newlines to be on. What about a compromise: respect newlines after <50 chars? I.e. short lines stay short; long lines wrap. Creole respects source line breaks too. -- 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: Customizing notification Subject
Is there an easy way to modify the notification Subject line to include a ticket field? We have a custom field, "State". We'd like the notification Subject to include the State field and follow this syntax as much as possible: [Type] [Ticket] [State]: [Summary] Example: CR #4 Assigned: Change background color from black to chartreuse. Can this easily be done? I'm looking at notification.py and it isn't clear to me (as a non-programmer) how to do this. I would appreciate any guidance and details. There is no "easy" way. You'll have to change the 'format_subj' method in notification.py. You would want something like this: return '%s #%s %s: %s' % (self.ticket['type'], self.ticket.id, self.ticket['status'], self.ticket['summary']) If you have the smtp_subject_prefix set to something or simply not part of your configuration (so the project name is added to each email), then you'll want to change the other return value in a similar way, only adding the prefix first. --~--~-~--~~~---~--~~ 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: Possible to use plain text instead of wikiformatting?
You can put all text in
{{{
}}}
And it will be treated as plain text, but this is not pretty either.
More than anything, I want to be able to take all \n's and turn them
into line breaks, even turn them in to wiki br's by just replacing them
with [br]
-Original Message-
From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED]
On Behalf Of Garrett McGrath
Sent: Monday, January 08, 2007 3:08 PM
To: trac-users@googlegroups.com
Subject: [Trac] Re: Possible to use plain text instead of
wikiformatting?
Ah, well I guess technically this is a wiki formatting thing but if you
just put a second line in like:
Line 1.
Line 2.
Line 3.
It'll work a bit better.
-Original Message-
From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED]
On Behalf Of Leon Torres
Sent: Monday, January 08, 2007 2:33 PM
To: trac-users@googlegroups.com
Subject: [Trac] Re: Possible to use plain text instead of
wikiformatting?
Hi again. :-)
It doesn't quite match what the user types in. The specific issue my
boss had was when he was typing in several lines like follows:
Line 1.
Line 2.
Line 3.
This isn't an itemized list, just several lines intended to be separated
by a CR. The wiki formatting put them all into one paragraph:
Line1. Line2. Line3.
Whereas in a standard text, it would come out exactly as the user
typed.
For instance, see the sourceforge issue description boxes. Those use
plain text formatting and what you type is what you get.
I personally don't mind the wiki formatting as plain text input, but one
day my boss typed in a ticket for me to do and when I read it, the lines
were jumbled together and created a communication issue.
- Leon
Garrett McGrath wrote:
Really the wiki formatting is only there to make things look pretty if
they just type it'll come out as plain text (or at least it 'should').
Just reinforce the use of the 'preview and confirm' practice.
-Original Message-
From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED]
On Behalf Of [EMAIL PROTECTED]
Sent: Monday, January 08, 2007 1:52 PM
To: Trac Users
Subject: [Trac] Possible to use plain text instead of wikiformatting?
Hi all,
I was wondering if it's possible to use plain text input in the trac
ticket description field instead of wiki formatting? The motivation
for this is to present a simpler input format for users that might not
be inclined to learn wiki formatting.
- Leon
>
--
This message has been scanned for viruses and dangerous content by the
eDiets MailScanner, and is believed to be clean.
--~--~-~--~~~---~--~~
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: Possible to use plain text instead of wikiformatting?
Leon Torres wrote: It doesn't quite match what the user types in. The specific issue my boss had was when he was typing in several lines like follows: Line 1. Line 2. Line 3. This isn't an itemized list, just several lines intended to be separated by a CR. The wiki formatting put them all into one paragraph: Line1. Line2. Line3. Whereas in a standard text, it would come out exactly as the user typed. A middle term would be to simply respect newlines, as we already do for changeset messages. That would avoid most of the issues. I wanted to do that for 0.11 anyway, but wondered about what the default should be. Like we have now, or escape newlines enabled by default? Now that we're talking about the wiki, I'd like to get some feedback about two other possible changes: - what about allowing bulleted list to start at the beginning of line? The constraint of the space in front is a bit artificial, as I don't see many possibility of having "false positive". (1) - the WikiCreole "standardization" initiative is an interesting one, and we can get close without sacrificing much (if anything). (2) I'd be interested to get some feedback on the above points. -- Christian (1) - http://trac.edgewall.org/ticket/124#comment:13 (2) - http://trac.edgewall.org/ticket/4356 --~--~-~--~~~---~--~~ 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] Customizing notification Subject
Is there an easy way to modify the notification Subject line to include a ticket field? We have a custom field, "State". We'd like the notification Subject to include the State field and follow this syntax as much as possible: [Type] [Ticket] [State]: [Summary] Example: CR #4 Assigned: Change background color from black to chartreuse. Can this easily be done? I'm looking at notification.py and it isn't clear to me (as a non-programmer) how to do this. I would appreciate any guidance and details. Thanks, Jen --~--~-~--~~~---~--~~ 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: Possible to use plain text instead of wikiformatting?
Ah, well I guess technically this is a wiki formatting thing but if you just put a second line in like: Line 1. Line 2. Line 3. It'll work a bit better. -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Leon Torres Sent: Monday, January 08, 2007 2:33 PM To: trac-users@googlegroups.com Subject: [Trac] Re: Possible to use plain text instead of wikiformatting? Hi again. :-) It doesn't quite match what the user types in. The specific issue my boss had was when he was typing in several lines like follows: Line 1. Line 2. Line 3. This isn't an itemized list, just several lines intended to be separated by a CR. The wiki formatting put them all into one paragraph: Line1. Line2. Line3. Whereas in a standard text, it would come out exactly as the user typed. For instance, see the sourceforge issue description boxes. Those use plain text formatting and what you type is what you get. I personally don't mind the wiki formatting as plain text input, but one day my boss typed in a ticket for me to do and when I read it, the lines were jumbled together and created a communication issue. - Leon Garrett McGrath wrote: Really the wiki formatting is only there to make things look pretty if they just type it'll come out as plain text (or at least it 'should'). Just reinforce the use of the 'preview and confirm' practice. -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, January 08, 2007 1:52 PM To: Trac Users Subject: [Trac] Possible to use plain text instead of wikiformatting? Hi all, I was wondering if it's possible to use plain text input in the trac ticket description field instead of wiki formatting? The motivation for this is to present a simpler input format for users that might not be inclined to learn wiki formatting. - Leon > --~--~-~--~~~---~--~~ 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: Possible to use plain text instead of wikiformatting?
Hi again. :-) It doesn't quite match what the user types in. The specific issue my boss had was when he was typing in several lines like follows: Line 1. Line 2. Line 3. This isn't an itemized list, just several lines intended to be separated by a CR. The wiki formatting put them all into one paragraph: Line1. Line2. Line3. Whereas in a standard text, it would come out exactly as the user typed. For instance, see the sourceforge issue description boxes. Those use plain text formatting and what you type is what you get. I personally don't mind the wiki formatting as plain text input, but one day my boss typed in a ticket for me to do and when I read it, the lines were jumbled together and created a communication issue. - Leon Garrett McGrath wrote: Really the wiki formatting is only there to make things look pretty if they just type it'll come out as plain text (or at least it 'should'). Just reinforce the use of the 'preview and confirm' practice. -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, January 08, 2007 1:52 PM To: Trac Users Subject: [Trac] Possible to use plain text instead of wikiformatting? Hi all, I was wondering if it's possible to use plain text input in the trac ticket description field instead of wiki formatting? The motivation for this is to present a simpler input format for users that might not be inclined to learn wiki formatting. - Leon > --~--~-~--~~~---~--~~ 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: Possible to use plain text instead of wikiformatting?
Really the wiki formatting is only there to make things look pretty if they just type it'll come out as plain text (or at least it 'should'). Just reinforce the use of the 'preview and confirm' practice. -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, January 08, 2007 1:52 PM To: Trac Users Subject: [Trac] Possible to use plain text instead of wikiformatting? Hi all, I was wondering if it's possible to use plain text input in the trac ticket description field instead of wiki formatting? The motivation for this is to present a simpler input format for users that might not be inclined to learn wiki formatting. - Leon --~--~-~--~~~---~--~~ 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] Possible to use plain text instead of wikiformatting?
Hi all, I was wondering if it's possible to use plain text input in the trac ticket description field instead of wiki formatting? The motivation for this is to present a simpler input format for users that might not be inclined to learn wiki formatting. - Leon --~--~-~--~~~---~--~~ 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: Yet Another "Authentication information not available."
Sebastien ... I've got a similar setup to what you want (but with TRAC installed under /usr/share/trac), and here's my Apache config: # Virtual host Projects ServerName projects.examples.com ServerAdmin [EMAIL PROTECTED] # Set the DocumentRoot for TRAC DocumentRoot /usr/share/trac/htdocs # Configure TRAC as root application, automatically identify valid projects SetHandler mod_python PythonHandler trac.web.modpython_frontend PythonOption TracUriRoot "/" PythonOption TracEnvParentDir "/usr/share/trac/projects" SetEnv PYTHON_EGG_CACHE /usr/share/trac/plugins # Configure authentication for TRAC AuthType Basic AuthName "trac" AuthUserFile /usr/share/trac/users Require valid-user # Configure basic resources for TRAC Alias /trac /usr/share/trac/htdocs Alias /css /usr/share/trac/htdocs/css SetHandler None # Configure Subversion access DAV svn SVNParentPath /data/svn # Limit write permission to list of valid users. AuthType Basic AuthName "Subversion" AuthUserFile /usr/share/trac/users Require valid-user Comparing your setup and mine, I'd say the problem lies in the way you've configured the authorization for /svn and /login, and as Marc-Antoine suggested, you need to use a LocationMatch for /login to support multiple projects. You don't need to put everything under /trac to get everything to work; Apache will match the best pattern from each Location section. You could copy my setup as long as you translated "/usr/share/trac" to "/var/trac" and "/usr/share/trac/users" to "/etc/apache2/dav_svn.passwd". You'll need to keep your PythonPath line if you don't install the Trac modules into the Python libs, and you'll want to have the "SetEnv PYTHON_EGG_CACHE" line if you install any Trac extensions. Note that if you do this, you'll need to have a SetHandler set for any other locations you choose to add, otherwise you'll inherit the mod_python handler from the root. This is the cost of using Trac as the root application for the virtual server. - Craig - sarbogast wrote: I've just set up Trac 0.9.3 on an Ubuntu 6.0.6 server in order to run multiple projects. Everything works fine until I try to login, and I get the following Python traceback: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/trac/web/modpython_frontend.py", line 206, in handler dispatch_request(mpr.path_info, mpr, env) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 139, in dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 107, in dispatch resp = chosen_handler.process_request(req) File "/usr/lib/python2.4/site-packages/trac/web/auth.py", line 82, in process_request self._do_login(req) File "/usr/lib/python2.4/site-packages/trac/web/auth.py", line 103, in _do_login assert req.remote_user, 'Authentication information not available.' AssertionError: Authentication information not available. I know that this kind of error has been reported several times in Trac's issue tracker but the solution seemed to be different everytime and none seemed to fit my configuration. Here is my virtual host configuration: ServerAdmin [EMAIL PROTECTED] ServerName trac.epseelon.org DocumentRoot /var/trac/ SetHandler mod_python PythonHandler trac.web.modpython_frontend PythonOption TracEnvParentDir /var/trac/ PythonOption TracUriRoot / PythonPath "sys.path + ['/var/trac/']" ErrorLog /var/log/apache2/error.trac.epseelon.org.log CustomLog /var/log/apache2/access.trac.epseelon.org.log combined Order allow,deny Allow from all DAV svn SVNParentPath /var/svn Satisfy Any Require valid-user AuthType Basic AuthName "The Epseelon Project Subversion Repository" AuthUserFile /etc/apache2/dav_svn.passwd AuthType Basic AuthName "Trac login" AuthUserFile /etc/apache2/dav_svn.passwd Require valid-user I'm almost certain there's something wrong in that virtual host because I tinkered with it based on a one-project configuration. Does anyone know what's wrong? Thanks in advance. --~--~-~--~~~---~--~~ 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: Setting Trac date format on Windows
OK, wiki page updated :-) Feel free to update the wiki page. --~--~-~--~~~---~--~~ 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: Setting Trac date format on Windows
It doesn't make clear that using 'PythonOption' is the only way to make
it work when using mod_python and it also implies that this is only for
Unix-like systems.
Feel free to update the wiki page.
PythonOption TracLocale is for mod_python, while the syntax of the
locale string ("de_DE.UTF-8") is for Unix.
Cheers,
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: Setting Trac date format on Windows
Thanks for that. The following line did the trick: PythonOption TracLocale "English_United Kingdom" I guess I was put off by the fact that in the FAQ it says: Alternatively, to simply change the date and time when using mod_python with a Un*x-like >system, simply do this... SetHandler mod_python PythonOption TracLocale "de_DE.UTF-8" ... It doesn't make clear that using 'PythonOption' is the only way to make it work when using mod_python and it also implies that this is only for Unix-like systems. Anyway, thanks again. Michael -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For mod_python you need to do "PythonOption TracLocale" instead of "SetEnv LC_TIME". - --Noah --~--~-~--~~~---~--~~ 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: Yet Another "Authentication information not available."
From: sarbogast [mailto:[EMAIL PROTECTED] I've just set up Trac 0.9.3 on an Ubuntu 6.0.6 server in order to run multiple projects. Everything works fine until I try to login, and I get the following Python traceback: [...] SetHandler mod_python [...] I'd be surprised if your SVN works in this way. If you're hosting the SVN repositories and Trac projects on the same host, then it's easiest to just put them in separate hierarchies: /trac, /svn. And set mod_python as handler under /trac, and TracUriRoot to /trac. [...] The login URL is per project, so that should be: #... Or if you'll be following the separate paths as mentioned above: --~--~-~--~~~---~--~~ 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: Setting Trac date format on Windows
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For mod_python you need to do "PythonOption TracLocale" instead of "SetEnv LC_TIME". - --Noah On Jan 8, 2007, at 4:40 AM, Michael Sanders wrote: I have unsuccessfully attempted to change the Trac date format from US format (mm/dd/) to European format (dd/mm/). I have the following set-up: Trac 0.10.3 Apache 2.0.58 Python 2.4.4 mod_python 3.2.10 Windows XP SP2 ...and have inserted the following line in to the Apache config: SetEnv LC_TIME "English_United Kingdom" This is in line with the instructions found in the TracFAQ: http://trac.edgewall.org/wiki/TracFaq#how-do-i-change-the-format- used-for-displaying-date-and-time I have restarted Apache, but the date format in all places in Trac remains in US format. I'd be grateful for any pointers to what I'm doing wrong. Does anyone have this working on Windows? & if so, with what configuration? I have also tried setting LC_ALL and LANGUAGE, but this also had no effect. Many thanks, Michael > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFokzoA9fEp2eRsU8RAt+dAKCDYinGA44A9faD6ppf2lQ2O/WqEwCfWYjQ oLOAEaNhzyWaZ14kR4ByEeA= =EAVK -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 -~--~~~~--~~--~--~---
[Trac] Setting Trac date format on Windows
I have unsuccessfully attempted to change the Trac date format from US format (mm/dd/) to European format (dd/mm/). I have the following set-up: Trac 0.10.3 Apache 2.0.58 Python 2.4.4 mod_python 3.2.10 Windows XP SP2 ...and have inserted the following line in to the Apache config: SetEnv LC_TIME "English_United Kingdom" This is in line with the instructions found in the TracFAQ: http://trac.edgewall.org/wiki/TracFaq#how-do-i-change-the-format-used-for-displaying-date-and-time I have restarted Apache, but the date format in all places in Trac remains in US format. I'd be grateful for any pointers to what I'm doing wrong. Does anyone have this working on Windows? & if so, with what configuration? I have also tried setting LC_ALL and LANGUAGE, but this also had no effect. Many thanks, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
