March 2001 - Zope-Dev

ZCatalog
by Marco Nova 01 Apr '01

01 Apr '01

Hello Guys, I'm a newbie about python and zope (about a week and a half till now), so probably most of what I say now is probably wrong. I was trying to customize the ZDiscussion product with file upload, editing of previous posts and deletes of old posts and I guess I've find a bug in the ZCatalog.uncatalogObject method. In the code there is: for btree in (data, paths): try: del btree[rid] except KeyError: LOG('Catalog', ERROR, ('uncatalogObject unsuccessfully ' 'attempted to delete rid %s ' 'from paths or data btree.' % rid)) else: try: self.__len__.change(-1) except AttributeError: pass # No managed length that means for each successfull unindex item, the __len__ counter will be decreased by 2, that's wrong. The correct code should look like: for btree in (data, paths): try: del btree[rid] except KeyError: LOG('Catalog', ERROR, ('uncatalogObject unsuccessfully ' 'attempted to delete rid %s ' 'from paths or data btree.' % rid)) try: self.__len__.change(-1) except AttributeError: pass # No managed length Or if we want to handle situations where the unindexs are unsuccessfull, we have to rewrite better the method with the use of transactions. That's all. Regards, Marco Nova Tera S.p.A. P.S. Zope Version Zope 2.3.1b2 (binary release, python 1.5.2, win32-x86) Python Version 1.5.2 (#0, Jul 30 1999, 09:52:18) [MSC 32 bit (Intel)] System Platform win32

3 2

Re: [Zope-dev] Medusa and HTTP/1.1
by Dieter Maurer 31 Mar '01

31 Mar '01

Seb Bacon writes: > In the case of the ZServer, I guess the correct behaviour would be to > have every page object return a Last-modified header, which defaults to > the modified date of the newest component of the page. This behaviour > could then be modified using cache managers like the Accelerated HTTP > Cache Manager. This can be quite tricky, as it is not obvious at all what are the components of a page. Dieter

2 1

ANN: mxDateTime 0.1
by palomar＠sg.uji.es 31 Mar '01

31 Mar '01

Hi all, Download mxDateTime 0.1 from http://sourceforge.net/projects/lleu README.txt ---------- Introduction This product makes easier to use the mxDateTime python module from Zope. It allows to use it from Python Products and external methods using for example:: from Products.mxDateTime import DateTime It's also accessible from restricted code (DTML methods, Scripts, etc..) using the '_' variable, for example:: <dtml-var "_.mxDateTime.today()"> How it works (read this if youd don't use a Unix like OS!!) When the product is initialized for the first time a symlink is created to the DateTime directory. If symlinks are not available (for example in Windows) you have to copy the whole DateTime directory instead. To make the module accessible from restricted code it has been needed to wrap it so it plays nice with the Zope security machinery. Best regards, jdavid

1 0

[Mini-HowTo]: Multiple Selects in ZClass Edit Forms
by Michael R. Bernstein 31 Mar '01

31 Mar '01

Problem: ------- You want your ZClass instance edit form to correctly display the currently selected values for a multiple selection property. Assumptions: ----------- You have a ZClass that has a multiple select property named 'format' with a value set to 'format_list'. You have a 'format_list' lines property set where the ZClass *instances* can acquire it. You generated an 'Edit' type 'Property Sheet Interface' that contains the following code: <tr><th align=left valign=top>format</th> <td align=left valign=top></td> </tr> Solution: -------- Replace the above code with the following: <tr><th align=left valign=top>format</th> <td align=left valign=top> <select name="format:list" multiple size="4"> <dtml-in format_list> <option <dtml-if "_['sequence-item'] in _['format']"> SELECTED</dtml-if> > <dtml-var sequence-item></option> </dtml-in> </select> </td> </tr> This will correctly display the currently selected values for your ZClass instance in the edit form, and capture the changed values when the form is submitted, casting even single selections to a list. Note: If the 'format_list' lines property is set where the Zclass instances can acquire it, but not where the ZClass definition can acquire it, then the Property Sheet management screen will *not* display the values. If you want to provide a default set of values that the ZClass definition can acquire as well as the ZClass instances (of course you can also override this locally), set the format_list property on the root folder. HTH, Michael Bernstein.

1 0

Wrong documentation?
by Tim Ansell 31 Mar '01

31 Mar '01

In the help documentation for the 'Authenticated_User' object it says the following.. hasRole(object, roles): Return a value that is true if the user has the given roles on the given object and return false otherwise. Permission - Always available getRoles(object): Returns a list of the roles the user has on the given object (in the current context?) Permission - Always available Neither seem to work (when given an object) with the standard user folder or LoginManager. In Login Manager (and it appears in the normal User Folder, though i haven't tested it) you have to use getRolesInContext(object). As well it appears that hasRole returns 1 when it's not suppose to. The has_role(roles, object) appears to work the way it hasRole is suppose to. Has the documentation become out of date or is their something else going on that i have missed? Mithro

1 0

ZPatterns Image Archive Project
by Michael R. Bernstein 31 Mar '01

31 Mar '01

Hello all, Background ---------- I am building an Image Archive Zope application using ZPatterns. I originally was trying to convert the Photo Product to ZPatterns in such a way as to still have it work as a normal product, but that turned out to be too complex. So, I am building the application fresh. So far, I have a RackImage Python product that subclasses from Image and DataSkin which seems to work fine. I can create, upload, view and delete the RackImages. Now I am working on a ArchiveImage ZClass that holds 'meta' information about an image, such as the description, a date, and keywords. I want to have one Rack for each image size that I want to store. I realize that I need to tie the Racks together in the specialist using SkinScripts, but I had a question that is a bit more fundamental: Where do I put the separate Racks? do I create a specialist for each Rack (seems unneccessary) or do I put several Racks in the same Specialist? If the latter, I'm unsure how to use DTML or PythonScripts to specify which Rack to create a new item in. The DTML I am using to instantiate RackImages in the Rack for example, is as follows: <dtml-let ni="newItem(REQUEST.id)"> <dtml-call "ni.manage_edit(REQUEST.title,'')"> <dtml-call "ni.manage_upload(REQUEST.file)"> </dtml-let> But this code only works for a Rack named defaultRack, which I can obviously only have one of. Any advice on this would be greatly appreciated. Thanks, Michael Bernstein.

2 1

access db linux
by danchik 31 Mar '01

31 Mar '01

does anyone know if there a way to have an access db to be placed onto linux box with zope running on it and have it be able to access that db????... I don't really want to convert the entire database.....

4 3

ANNOUNCE: Zope 2.3.1 final released
by Brian Lloyd 30 Mar '01

30 Mar '01

Hello all, Zope 2.3.1 final has been released - you can download it from Zope.org: http://www.zope.org/Products/Zope/2.3.1/ Zope 2.3.1 contains fixes for a number of issues that have come up since 2.3.0, including the fixes for the issues addressed by the 02/23 and 03/08 hotfixes. It also contains a number of changes to address issues with ZCatalog. New data structures have been introduced to reduce the number of conflict errors caused by object indexing under some types of usage, and to reduce the amount of object database bloat that occurs when indexed objects change frequently. The changes to ZCatalog have been designed so that newly created ZCatalog objects will take advantage of the new data structures. Existing ZCatalog objects will continue to work with the old data structures, but will not gain any of the benefits of the new code. It is possible to upgrade an existing ZCatalog object to use the new data structures by following the How-To at: http://www.zope.org/Members/mcdonc/HowTos/UpgradeToNewCatalog Many thanks go to those who helped exercise the new code and the catalog upgrade process during the beta cycle. Many thanks as well to Jim Fulton, Chris McDonough and Andreas Jung for their hard work and the prodigious amount of unit tests produced for the new (and old) Catalog code! With the 2.3.1 release we have added a Linux Itanium binary distribution. Note that the Itanium binary is bundled with Python 2.0 instead of Python 1.5.2. This release (Zope-2.3.1-linux2-ia64-alpha.tgz) is named with "alpha" because it is the first for the platform. All unit tests pass and moderate testing has found no problems (actually, any problems you find are more likely to be issues with Zope on Python 2.0 rather than issues with the platform). **IMPORTANT NOTE** for users of the source release or users of the "diff" update releases Users of the Zope source releases should note that this release contains changes to C code. If you are using a source release (or the source diff update), be sure to run 'w_pcgi.py' or 'wo_pcgi.py' as appropriate before starting Zope to ensure that your binaries are rebuilt. Also, there has been some recent work on getting Zope to run on the Mac OS X platform. As a result of this work, the names of certain C extension modules were changed to avoid symbol name clashes on systems with a global dynamic module namespace. The result of this is that if you install a diff update over an existing installation, you need to do a few things manually: - If you are using a source release and apply the source update, visit the directories 'lib/python/BTrees' and 'lib/python/Shared/DC/xml/pyexpat'. In each, run 'make clean' and remove any .so files in those directories before rebuilding the extensions. - If you are running a binary release and have applied the diff update for your platform, before restarting Zope visit the 'lib/python/BTrees' directory and remove any .so (or .pyd) files that do *not* have names beginning with an underscore and in the directory 'lib/python/Shared/DC/xml/pyexpat', remove the file 'pyexpat.so' (or .pyd) For more information on what is new in this release, see the CHANGES.txt and HISTORY.txt files for the release: http://www.zope.org/Products/Zope/2.3.1/CHANGES.txt http://www.zope.org/Products/Zope/2.3.1/HISTORY.txt Note that we have also posted "diff" updates as .tgz files that will let you easily upgrade an existing 2.3.x site. These updates are available for those currently using the 2.3.x source release or the 2.3.x binary releases. To apply a differential update to your site: - download the appropriate .tgz file from zope.org - shutdown your Zope process - copy the .tgz to your Zope directory and extract it - SEE THE NOTE ABOVE!! - run w_pcgi or wo_pcgi *if you are not using a binary release* - restart your process Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

1 0

Problem with Hotfix 2000-10-11 on 2.1.6
by Gregor Hoffleit 30 Mar '01

30 Mar '01

I'm having trouble installing Hotfix_2000-10-11 on Zope 2.1.6, although the README says: "The hotfix will work for all versions of Zope 2.2.0 and higher." If installed on 2.1.6, the product shows up as broken, since it tries to run "from OFS.ObjectManager import aq_base", which fails, since aq_base wasn't available in ObjectManager before 2.2.1 (!). Therefore I guess the Hotfix won't work for any versions prior to 2.2.1. According to the README, those versions are still vulnerable. Could somebody give me a hint if and how it's possible to backport the Hotfix to Zope 2.1.6 ? Gregor

3 4

RE: [Zope-dev] ZCatalog
by Marco Nova 30 Mar '01

30 Mar '01

> > I'm a newbie about python and zope (about a week and a half > till now), so > > probably most of what I say now is probably wrong. > > > > I was trying to customize the ZDiscussion product with file upload, > editing > > of previous posts and deletes of old posts and I guess I've > find a bug in > > the ZCatalog.uncatalogObject method. > > Thanks for the report! > > This is already fixed in CVS. you're welcome. > > Or if we want to handle situations where the unindexs are > unsuccessfull, > we > > have to rewrite better the method with the use of transactions. > > We needn't worry about manually managing transactions here > because the ZODB > takes care of it for us. So if a a method raise an exception all the things done (that involve zodb) in the method will be rolled back ? - mn

2 1