October 2004 - Zope - Zope lists

Newbie question about Zope functions
by Beverly 29 Oct '04

29 Oct '04

We're trying to pick the right open-source platform to build an online community site. Needs are a bulletin board, a blogging capability, and a good permissioning system (users will be members of groups and some pages will be accessible to everyone, but some limited to members of one group or another). Would Zope be a good fit for this? Any examples of Zope sites built with this functionality appreciated. Thanks for any illumination. Beverly (I didn't see a bboard on the zope.org site itself, so maybe Zope's strong points are in content management, rather than these community functions?)

5 5

File uploads: filename with ';'
by Vova 28 Oct '04

28 Oct '04

Hello All! It seems that Zope does not handle names of uploaded files correctly when it include ';'. -- Vladimir

7 17

add folder by ftp/webdav script
by Garito 28 Oct '04

28 Oct '04

Hi! I create a folderish product and I override MKCOL_handler and manage_addFolder to execute a function. This function call a python script and executes it The process work fine (the folder is created) but the FTP client raises an error (but the folder is created correctly!!!!) has anyone any idea about what is happening? Thanks!!!

1 0

sendall attribute error in zope 2.6.1/python2.1.3/windows
by Sean Kelley 27 Oct '04

27 Oct '04

Hi, I am sending email via zope and a python script from cmf workflow. When I as the admin send the email it sends without problems. When a CMF/Plone member with manager rights does it I get this sendall missing attribute error. I have researched this and it appears there may have been an issue with python 2.1.3 not having sendall module included in the windows release. HOWEVER, if I can do it as the site admin this would seem to me not to be the issue. I am hoping to find the actual issue here before attempting to fix python 2.1.3 or upgrade zope/python. Traceback (innermost last): Module ZPublisher.Publish, line 98, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 39, in call_object Module Products.CMFPlone.FormTool, line 235, in __call__ Module Products.CMFPlone.NavigationTool, line 98, in getNextObject Module Products.CMFPlone.NavigationTool, line 289, in _getScript Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 39, in call_object Module Products.CMFCore.FSPythonScript, line 90, in __call__ Module Shared.DC.Scripts.Bindings, line 252, in __call__ Module Shared.DC.Scripts.Bindings, line 270, in _bindAndExec Module Shared.DC.Scripts.Bindings, line 283, in _bindAndExec Module Products.CMFCore.FSPythonScript, line 124, in _exec - __traceback_info__: ({'script': <FSPythonScript at /utilities/content_status_modify used for /utilities/Special_Groups/Subregional_Discussion_Team/SubDiscussionMinutes>, 'context': <Document at /utilities/Special_Groups/Subregional_Discussion_Team/SubDiscussionMinutes>, 'container': <PloneSite instance at 01B1EF48>, 'traverse_subpath': []}, ('announce', '', '', ''), {}, ('', None, None)) Module Script (Python), line 7, in content_status_modify Module Products.CMFPlone.WorkflowTool, line 37, in doActionFor Module Products.CMFCore.WorkflowTool, line 309, in doActionFor Module Products.CMFCore.WorkflowTool, line 624, in _invokeWithNotification Module Products.DCWorkflow.DCWorkflow, line 275, in doActionFor Module Products.DCWorkflow.DCWorkflow, line 440, in _changeStateOf Module Products.DCWorkflow.DCWorkflow, line 489, in _executeTransition Module Shared.DC.Scripts.Bindings, line 252, in __call__ Module Shared.DC.Scripts.Bindings, line 270, in _bindAndExec Module Shared.DC.Scripts.Bindings, line 283, in _bindAndExec Module Products.PythonScripts.PythonScript, line 315, in _exec Module Script (Python), line 94, in email_announce - <PythonScript at /utilities/portal_workflow/plone_workflow/scripts/email_announce> - Line 94 Module Products.MailHost.MailHost, line 125, in send Module Products.MailHost.MailHost, line 145, in _send Module smtplib, line 466, in sendmail Module smtplib, line 316, in ehlo Module smtplib, line 247, in putcmd Module smtplib, line 235, in send Module socket, line 1, in sendall AttributeError: sendall Sean

1 0

python script containing userid and ip address help
by Jason Leach 27 Oct '04

27 Oct '04

After re-reading I see you already have the info. I still think it will need to be an external method since you can't import md5 into Zope (security). (Use your digest funciton call if you like.) ####### External Method ######### import md5, string def _formatHex(str): "Generate a MD5 string's HEX code." d = map(None, str) d = map(ord, d) d = map(lambda x:"%02x" % x, d) return string.join(d, "") # add the external method, and call it in your PythonScript (something like): myHash = container.mhtools_getHexHash('%s%s%s' % (member.getProperty('uid'), REQUEST['REMOTE_ADDR'], passphrase)) then return a string to your ZPT to fill in the link: return a string as your url: return 'http://url?action=sso:portal&userid=%s&session=%s' % (userid, myHash) This is just to give you the idea. It's not the actual code you shoud use, but hopfully it helps get the gears truning. Jason.

1 0

RE: RFC: Proposed backward-compatibility policy
by Gfeller Martin 27 Oct '04

27 Oct '04

>> You probably have to explicitly exclude the environment of >> external methods, > Why do you say that? As I can basically access and modify anything from an external method (thanks to Python power), you must either define very clearly what I'm allowed to do, or decline any assurance that it will work in any future release. Of course I have some (hopefully good) idea about what I can do from an external method without breaking things in the future, but since this is not a compiled (aka, locked & sealed) environment, I think you have to exclude it. This applies to external methods and writing of products, but not to TTW use of Zope's facilities (including scripts). Even if I test and report it, you may rightly say that I shouldn't have "touched" that part in the first place. Martin

1 0

RE: RFC: Proposed backward-compatibility policy
by Gfeller Martin 27 Oct '04

27 Oct '04

Jim, I think this is a very fair and gentle policy for any kind a programmable product, and an extremly fair policy for an open source product (where I can check and/or modify the source if I run into a crucial compatibility problem). You probably have to explicitly exclude the environment of external methods, and restrict compatbility to the published APIs ("published" being easier to define in Zope 3 than in Zope 2, I assume). Best regards, Martin _______________________ COMIT Gruppe Risk Management Systems http://www.comit.ch http://www.quantax.com - Quantax Trading and Risk System http://www.swordrisk.com - Sword Operational Risk System

2 1

Subject: [Zope] python script containing userid and ip address help
by Jason Leach 27 Oct '04

27 Oct '04

I'm surprised you could import md5 into a PythonScript. I had to do it with an external method. What you are asking is not too hard, I would probably write an External method. It's pretty easy to query LDAP for the UID number. If passphrase is in the directory also just ask for this at the same time. Since this ends up being an LDAP question you can mail me out of the list for the LDAP query code. (if an External method is how you want to do it). Jason.

1 0

RFC: Proposed backward-compatibility policy
by Jim Fulton 27 Oct '04

27 Oct '04

Below is a proposed policy on backward compatibility for Zope. Zope Policy on Backward Compatibility ===================================== Backward compatibility needs to be a very high priority. Clean software also needs to be a high priority. Unfortunately, these goals are often at odds. Providing backward compatibility support makes code more complex and, thus, less maintainable. Going forward, we will address these conflicting goals in the following ways; 1. During development, alpha testing, and beta testing of new releases, any backward-incompatible change will be considered a bug. That is, we will make all effort to make sure that each release of Zope is backward compatible with the previous two feature releases. 2. Backward compatibility support will be limited. When we make a change that would require a change in software or data, we'll add code to support the old software or data, but we will also add code to generate deprecation warnings when that support code is used. The deprecation warnings will say specifically when the backward-compatibility support will go away. This time will usually be expressed as a release number at least two feature releases past the next feature release. (For example, if the next feature release is release 3.1, then the backward compatibility support would not be removed any sooner than release 3.3.) In other words, we will limit the time extent of backward compatibility support, but we will give plenty of warning. When data changes are involved, we'll provide data conversion tools that will be available before we begin the deprecation process. An additional issue is that it is often difficult to figure out if subtle features are being used. (For example, a change in an exception base class might affect some client that expected to catch the exception based on it's base exception.) It is very hard for a developer to assess whether any applications are relying on a particular feature and thus whether backward-compatibility support needs to be provided. Often developers will make judgment calls. If they judge wrong, we need to catch this with testing. This leads to a 3rd point: 3. It is very important to catch backward compatibility problems during development of new releases. In particular, it is important to test new Zope releases before they are released in final form. If a backward-compatibility problem is found before the final release, it will be considered a bug and will be fixed (by adding backward compatibility support) if at all possible before the final release. After the final release, we may choose not to bother to fix backward-compatibility problems. Consumers of Zope have a right to backward compatibility, but they also have a responsibility to test Zope against their applications during the beta release cycle (or sooner) to make sure their applications work. Questions? Thoughts? Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

1 0

Re: [Zope] Use of APE in a production environment?
by Brad Clements 27 Oct '04

27 Oct '04

On 27 Oct 2004 at 8:14, Kelly McDonald wrote: > However, zope chokes on that keyword. I'm wondering if you had to patch > zope in some manner to get it to work? > > I'm currently using apelib 1.0, & Zope 2.7.2 and my Ape-fs is being > mounted at the root directory. > > any suggestions? Ah, I think I have submitted a change to Shane about this too. In Ape-1.0 directory, edit component.xml and about line 96, check to see if it looks like this: <key name="hidden_filenames" default="_"> I think it used to be hidden-filenames, which doesn't work. -- Brad Clements, bkc(a)murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax http://www.wecanstopspam.org/ AOL-IM: BKClements

1 0