[Issuetracker-development] IssueTrackerMassContainer 0.0.2a

[Peter B. <ma...@pe...>]

To all administrators or the IssueTrackerProduct.

Remember the IssueTrackers general masscontainer?
http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers_masscontainer_first_release
http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers.zexp/view

Now I've put this together as a proper python product instead.
It's called IssueTrackerMassContainer and has only been released on 
SourceForge yet.

Download it from
http://sourceforge.net/project/showfiles.php?group_id=60145
Or from these CVS commands
$ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login
[when asked for password, press ENTER]
$ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker co 
IssueTrackerMassContainer

If you don't already use the folder 'issuetrackers', just install it and 
create an instance of it. Then create all your issue tracker instance 
inside this object.

If you already have a folder with lots of issuetracker instances, install 
the product, create an instance and copy all the instances from the old 
folder to this new object.
HOWEVER, because you're copying ZCatalogs the references within them are 
incorrect. You'll need to do a UpdateCatalog.
For this to be efficient, you must download the latest CVS version of 
IssueTrackerProduct like this

$ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login
[when asked for password, press ENTER]
$ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker co 
IssueTrackerProduct

This latest version (not yet released) has a much improved UpdateCatalog() 
method.

Then use the 'automate' python script that was created in the new mass 
container object to go through the UpdateCatalog() method for each instance.


I would very much like to have some functional feedback on this before I 
release it to Zope.org
Does it work?
Feedback?

Peter