Changes between Version 21 and Version 22 of TracMultipleProjects/ComprehensiveSolution

Timestamp:

Jun 28, 2007, 6:24:52 PM (17 years ago)

Author:

Dave Abrahams <dave@…>

Comment:

—

TracMultipleProjects/ComprehensiveSolution

@@ -65 +65 @@
 
  Naturally, the same kinds of issues apply to other resources such as Milestones.  Upon creation by a customer, they need to be private to that customer and (some subset of) my people.  When ''I'' create these resources there needs to be an ''easy'' way to make them private to a particular customer's company.  And I'm sure that other people will have vastly different "permission workflow" requirements than I do, so the system probably needs to be more flexible than what I've described.
-
-== Troubleshooting ==
-
-I have applied a few small patches to my local trac installation to work around various bugs in Trac or in plugins.  I'm not sure that these bugs will show up for you when implementing this solution (and it's very likely they've already been fixed by the trac team), but in the interest of full disclosure, here they are:
-
- * ticket:4547 describes a problem where python generates errors because {{{datetime}}} objects and numeric types such as {{{float}}} don't interoperate.  The latest patch at the time of this writing is attached to the ticket: [#4547/datefmt-r5696.diff].
- * If Trac tells you to run "{{{trac-admin /path/to/your/environment upgrade}}}, and it fails with "{{{iteration over a non-sequence}}}", apply the tiny patch shown in #5593.