December 2001 - Zope-Dev

ZCatalog becoming empty when using "Update" in conjunction with ZPatterns
by Jean Jordaan 03 Dec '01

03 Dec '01

Hi all I had a ZCatalog with about 3500 DataSkin instances indexed. Then I started to index instances of a regular ZClass as well. Then I added another index, to catalog an additional property of this ZClass, and hit "Update Catalog". When Zope returned from updating, there were no records in the Catalog, though the Vocabulary was intact. I see that I cannot search for the DataSkin metatypes using the "Find Objects" ZCatalog tab: they don't show up in the "Find objects of type" field. So perhaps this is why updating failed. However, now the Catalog is not accepting any entries. I originally did the cataloging using this kind of loop on all the classes I wanted indexed:: ids = container.Roundup.Issues.defaultRack.getPersistentItemIDs() for id in ids: object = container.Roundup.Issues.defaultRack.getItem(id) Catalog.catalog_object( object , string.join( object.getPhysicalPath() , '/')) When I try to run that again, I still get "There are no objects in the Catalog." upon return. When I run it using a newly created catalog ('testCatalog') instead, it works fine. Could anyone perhaps explain what's happening here? Regards, Jean

1 0

Re: [Zope-dev] WebService package
by sean.bowman＠acm.org 02 Dec '01

02 Dec '01

hello, there's a collector issue at http://collector.zope.org/Zope/62. thanks, Sean

1 0

WebService package
by sean.bowman＠acm.org 02 Dec '01

02 Dec '01

hello, I found a couple of problems while I was playing around with the WebServices package; I think this patch fixes them. The package looks very nice, especially the documentation. Unfortunately, I don't understand SOAP well enough yet to make any intelligible comments... Sean Index: SOAPMessage.py =================================================================== RCS file: /cvs-repository/Packages/WebService/SOAPMessage.py,v retrieving revision 1.1 diff -u -r1.1 SOAPMessage.py --- SOAPMessage.py 26 Nov 2001 16:18:22 -0000 1.1 +++ SOAPMessage.py 2 Dec 2001 22:35:23 -0000 @@ -118,7 +118,7 @@ def getParameter(self, name): """Return the named message parameter of the SOAP response.""" - for item in self.params: + for item in self.parameters: if item.name == name: return item return None Index: Transports.py =================================================================== RCS file: /cvs-repository/Packages/WebService/Transports.py,v retrieving revision 1.4 diff -u -r1.4 Transports.py --- Transports.py 29 Nov 2001 22:18:02 -0000 1.4 +++ Transports.py 2 Dec 2001 22:35:23 -0000 @@ -51,12 +51,11 @@ raise ValueError( 'This Python installation does not have SSL support.' ) - conn = TimeoutHTTPS(host, None, self.timeout) + conn = TimeoutHTTPS(host, None, self.timeout, + key_file=self.key_file, + cert_file=self.cert_file) else: - conn = TimeoutHTTP(host, None, self.timeout, - key_file = self.key_file, - cert_file = self.cert_file - ) + conn = TimeoutHTTP(host, None, self.timeout) conn.putrequest(verb, path)

2 1

Fully Zope-based Mailman Version
by Stephan Richter 02 Dec '01

02 Dec '01

Hello everyone, I just had a look into Mailman again. The API seems to be very clear, even though I could not find any UML diagrams anywhere. However I found out that porting Mailman to Zope (as a Python Product) might be a very simple task. Due to the nature of the project, the implementation phase could be setup in a couple of independent steps: 1. Convert the HTML screens to Zope DTML and connect the functionality to Mailman. 2. Move storage of list and user info to the ZODB 3. Move archives to the ZODB. 4. Create a nice installer that can bind the latest Mailman release with Zope. I think a first alpha release could be produced in about 40-60 hours and the full-fledged Mailman Distribution beta in about 1.5 man-month (270 hours). In fact most of the API would not even need to change, since we just need to insert our modified API at specific places, such as database connectivity and saving processes. Later we could even provide a Mailman UserFolder and search functionality for the archive. For people that do not think that the ZODB is up to handling large archives, DBObjects could be used for transparent R2O mapping from PostGreSQL (or any other RDB). The reason I write is, because I wanted to know whether someone would be interested in helping with this project, that would start after mid-December... Help can be offered in terms of programming or financial support of course. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management

2 4

Scrollbar off the page in manage_workspace
by Walter Miller 01 Dec '01

01 Dec '01

Both in 2.4.3 and 2.5.0 b1, the scrollbar seems to be off the end of the page and the "Wider" and "Narrower" buttons don't work. For example, in 2.5.0 b1, editing http://localhost/index_html in the browser seems to work fine but the http://localhost/standard_template.pt doesn't. I'm using IE 6.0 but I believe I had this same problem with IE 5.5. Netscape 4.08 seems to work. Mozilla 0.9.5 kind of works meaning that at least the scrollbar is not off the page but the "Wider" and "Narrower" buttons don't work. Opera 6.0 works as well as Netscape 4.08 except I did notice it doesn't like it when you change the default preferences, i.e. no CSS, no top bar. Walter

1 0

Catalog improvements
by Wolfram Kerber 01 Dec '01

01 Dec '01

Hi, i'm currently working on a product that allows to attach relational information to zope-objects. It works quite well so far, but to further enhance it i need to make some changes to the Catalog. I could perhaps implement it as a separate product, but i strongly feel that those changes are best applied to the Catalog itself, as they are of general use (i think) and involve a lot of changes to the inner workings of the Catalog. In particular i need the following: - named/stored queries these are precompiled queries, so they can be executed without parsing and are easily cacheable i.e. similar to what is implemented in CMFTopic, but stored in the Catalog and a bit smarter - caching support - unions and intersections sub-queries (i.e. queries that are directed at a certain index) should be more flexibly combineable I searched this mailing-list as well as zope.org to get an idea about what has already been discussed and requested, and there seems to be some interest in improving the Catalog. Some people even seem to have worked on this, perhaps they could give an update on this? Possibly i don't have to write everything from scratch... I would have put this into a proposal, but there already are two proposals that deal with the features i want, one is dedicated to unions/intersections, the other (TopicIndexes) to performance issues (i dont't know what's the status of these though, especially the first one is rather old), and i don't want to hijack them without asking. As so often i will need to complete my current project first, but would then like to help in improving the Catalog for a more general use. So, if there is interest, i would propose to collect some ideas and comments about how a better Catalog should look like, how it could be best implemented and how to organize this effort (with respect to the already existing proposals). -- Wolfram Kerber Gallileus GmbH http://www.gallileus.info/

11 26