March 2001 - Zope-Dev

Running out of single letters for z2.py command options
by Ng Pheng Siong 22 Mar '01

22 Mar '01

Hi, When I released ZServerSSL for Zope 2.1.x, I used "-W" for HTTPS and "-M" for the encrypting monitor on z2(s).py's command line. For Zope 2.3.0, "-W" has been taken by WebDav; "-x" happens to be free, so I use that for HTTPS. I haven't checked if "-M" is taken. (I intend to build an SRP-based[1] encrypting monitor.) Can I, um, kinda reserve some letters for my crypto options to z2.py? ;-) More seriously, I think soon z2.py must go to long options, i.e., "z2.py --this --that=42". Or, use snippets written in Python for config. How soon is that? Cheers. [1] SRP - Secure Remote Protocol, one of a class of so-called "strong password protocols". http://srp.stanford.edu, I think. -- Ng Pheng Siong <ngps(a)post1.com> * http://www.post1.com/home/ngps

1 0

Deleting objects by the users
by Menno Brandsen 22 Mar '01

22 Mar '01

Hello all, I have a question conserning deleting objects(images) by the user The situation is this : I have a page that lists the contents of the folder below, containing images of a site. In that list a want to let the user/client delete the image that he wants. I've tried using this syntax : <a href="#" onClick="<dtml-call "image_folder.manage_delObjects(ids=_['id'])">"> DELETE </a> What happens now is that as soon as the page loads it inmediatly deletes the images. Can anybody tell me a sollution for this problem ? I would be very gratefull ! =) Greetings, Menno Brandsen 0---------------------------------o | M. Brandsen | | Parkstraat 20 | | 2517 JK | | Den Haag | | +31(0)70-3108950 0---------------------------------o | Menno(a)infinitum.nl | | | | Your mouse has moved. | 0--------------------------| Windows has to reboot for | | changes to take effect. | | | | [ OK ] | | | 0---------------------------------0

4 4

sql_quote problem?
by Chris Withers 22 Mar '01

22 Mar '01

Hi, When I do the following in a ZSQL Method: SELECT * from x WHERE y=<dtml-sqlvar sec type=string> it works fine, however, when I do: SELECT * from x WHERE y=<dtml-var sec sql_quote> I get: exceptions.AttributeError Traceback (innermost last): File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 223, in publish_module File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 179, in publish File /usr/zope/zope-2_3_1b3/lib/python/Zope/__init__.py, line 240, in abort File /usr/zope/zope-2_3_1b3/lib/python/ZODB/Transaction.py, line 179, in abort File /usr/zope/zope-2_3_1b3/lib/python/Shared/DC/ZRDB/TM.py, line 126, in abort File /usr/zope/zope-2_3_1b3/lib/python/Shared/DC/ZRDB/TM.py, line 119, in _abort AttributeError: rollback What gives? ;-) Chris

2 3

More ZSQL weirdness (this time with Python Scripts ;-)
by Chris Withers 22 Mar '01

22 Mar '01

Hi, I had the following line in a dtml method, x_report, generated by 'Add Z Search Interface': <dtml-in x> ...where x is a ZSQL Method that takes one parameter: sec Now, when I try to call x_report from a python script, my_ps, as follows: return container.x_report(context,context.REQUEST,sec='XXX') ...I get the following: Error Type: Bad Request Error Value: ['sec'] ...and the only way I can stop it doing that is to change the line in x_report to read: <dtml-in "x(sec=_.getitem('sec'))"> ...which isn't very nice :-( Has anyone seen anything similar or should I stick this in the collector? cheers, Chris PS: Traceback (innermost last): File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 223, in publish_module File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 187, in publish File /usr/zope/zope-2_3_1b3/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: Traversable) File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 171, in publish File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: my_ps) File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: my_ps) File /usr/zope/zope-2_3_1b3/lib/python/Shared/DC/Scripts/Bindings.py, line 324, in __call__ (Object: my_ps) File /usr/zope/zope-2_3_1b3/lib/python/Shared/DC/Scripts/Bindings.py, line 353, in _bindAndExec (Object: my_ps) File /usr/zope/zope-2_3_1b3/lib/python/Products/PythonScripts/PythonScript.py, line 336, in _exec (Object: my_ps) (Info: ({'script': <PythonScript instance at 9067f20>, 'context': <Folder instance at 90325e8>, 'container': <Folder instance at 90325e8>, 'traverse_subpath': []}, (), {}, None)) File Script (Python), line 2, in my_ps (Object: <lambda>) File /usr/zope/zope-2_3_1b3/lib/python/OFS/DTMLMethod.py, line 189, in __call__ (Object: x_report) File /usr/zope/zope-2_3_1b3/lib/python/DocumentTemplate/DT_String.py, line 538, in __call__ (Object: x_report) File /usr/zope/zope-2_3_1b3/lib/python/DocumentTemplate/DT_In.py, line 646, in renderwob (Object: x) File /usr/zope/zope-2_3_1b3/lib/python/Shared/DC/ZRDB/DA.py, line 476, in __call__ (Object: x) File /usr/zope/zope-2_3_1b3/lib/python/Shared/DC/ZRDB/Aqueduct.py, line 150, in _argdata (Object: x) Bad Request: (see above)

1 0

zserver medusa timeout? anyone?
by J�lio Dinis Silva 22 Mar '01

22 Mar '01

Hi, I would like to know if ANYONE has ever put timeout parameter of ZServer/Medusa to work, i.e, if changing this timeout value to a low value and actually seen it to work, i.e, closing zombie channels. Anyone done this? I've tryed almost everything on my limited knowledge of zope/python, creating zombie requests running in a zserver with a timeout=realylowvalue but the request was never closed. Maybe I'm realy missing something here. Regards, Júlio Dinis Silva _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

1 0

Comment on CVS change of default textindex search operator
by R. David Murray 22 Mar '01

22 Mar '01

>To: zope-checkins(a)zope.org >Date: Mon, 19 Mar 2001 19:47:31 -0500 (EST) >From: chrism(a)digicool.com (Chris McDonough) >Subject: [Zope-Checkins] CVS: Zope2 - UnTextIndex.py:1.33.2.9 > >Update of /cvs-repository/Zope2/lib/python/SearchIndex >In directory korak:/home/chrism/sandboxes/2_3Branch/lib/python/SearchIndex > >Modified Files: > Tag: zope-2_3-branch > UnTextIndex.py >Log Message: >Changed default query operator to 'AND' instead of 'OR' (way improved search results). This strikes me as a Very Bad Thing. Not the idea of having AND be the default query operator, but the fact of *changing* the default. If I remember correctly the default is documented (insofar as it is documented) as being AND, but the default has been OR for so long that I'm sure there are many sites that will break if this change is committed to a release. Worse, the behavior of a site as seen by end users will change. Finally, it is my experience that most search engines use OR as the default operator. I prefer AND myself, but OR appears to be something of a defacto standard. I'm willing to be convinced, though <grin>. A way to set the default would be cool, but might open up a can of worms. --RDM

4 6

ANNOUNCE: Zope 2.3.1 beta 3 released
by Brian Lloyd 22 Mar '01

22 Mar '01

Hello all, Zope 2.3.1 beta 3 has been released - you can download it from Zope.org: http://www.zope.org/Products/Zope/2.3.1b3/ Zope 2.3.1b3 contains a number of bug fixes, including fixes for issues found during b2 regarding ZCatalog and updating ZCatalogs to make use of new underlying data structures. For more information on upgrading ZCatalog objects, see: http://www.zope.org/Members/mcdonc/HowTos/UpgradeToNewCatalog **Users of the Zope source releases should note** that this release contains changes to existing 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. 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.1b3/CHANGES.txt http://www.zope.org/Products/Zope/2.3.1b3/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 - 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

Subject: Re: [Zope-dev] Comment on CVS change
by Tres Seaver 22 Mar '01

22 Mar '01

Casey Duncan <cduncan(a)kaivo.com> wrote: > "R. David Murray" wrote: > > > > >To: zope-checkins(a)zope.org > > >Date: Mon, 19 Mar 2001 19:47:31 -0500 (EST) > > >From: chrism(a)digicool.com (Chris McDonough) > > >Subject: [Zope-Checkins] CVS: Zope2 - UnTextIndex.py:1.33.2.9 > > > > > >Update of /cvs-repository/Zope2/lib/python/SearchIndex > > >In directory korak:/home/chrism/sandboxes/2_3Branch/lib/python/SearchIndex > > > > > >Modified Files: > > > Tag: zope-2_3-branch > > > UnTextIndex.py > > >Log Message: > > >Changed default query operator to 'AND' instead of 'OR' (way improved > > > search results). > > > > This strikes me as a Very Bad Thing. Not the idea of having AND be the > > default query operator, but the fact of *changing* the default. If I > > remember correctly the default is documented (insofar as it is documented) > > as being AND, but the default has been OR for so long that I'm sure there > > are many sites that will break if this change is committed to a release. > > Worse, the behavior of a site as seen by end users will change. Finally, > > it is my experience that most search engines use OR as the default operator. > > I prefer AND myself, but OR appears to be something of a defacto standard. > > > > I'm willing to be convinced, though <grin>. > > > > A way to set the default would be cool, but might open up a can of worms. > > I'm a little torn between being alarmed at this and agreeing with it. I > think if this is done there should be an TTW interface in ZCatalog to > switch between AND and OR as the default. That would be the best > solution IMHO. Also a _documented_ way to switch it in Catalog as well. I've gotta weigh in here, too; the breakage induced by this change will be large. Give that what *real* users expect is *neither* a Boolean "AND" *nor* a Boolean "OR", but instead a DWIM/Googlesque "affinity" search, I don't think the win is clear enough to warrant the breakage: * "AND" searches return *small* result sets; non-programmers will be surprised by the often-empty lists they get back, and won't have any clue how to broaden their search. False negatives suck. * "OR" searches return *long* results sets; non-programmers will be unhappy that the items they want are buried in the muck. False positives suck. Given that any site manager can override the policy trivially, using only two lines of DTML, should we really be switching the (admittedly arbitrary) existing polciy embedded in the core? Tres. P.S. <dtml-let search_terms="_.string.split( search_text )" search_with_and="_.string.join( search_terms, ' and ' )"> <dtml-var searchCatalog> </dtml-let> OK, so it is two and a half lines. -- =============================================================== Tres Seaver tseaver(a)digicool.com Digital Creations "Zope Dealers" http://www.zope.org

5 5

[ ANN ] LDAPLoginAdapter 1.1 released
by Jens Vagelpohl 21 Mar '01

21 Mar '01

LDAPLoginAdapter 1.1, a user folder replacement that authenticates against an LDAP server, has been released. You can view some of the documentation and download the software at http://www.dataflake.org/software/ldaploginadapter/ A Tracker at that same address allows you to easily file bug reports or feature requests for this product. Improvements and bugfixes since the last announcement include: **LDAPLoginAdapter 1.1** Features Added: * Instead of hardcoding fixed publicly available attributes onto the LDAPUser object you can now take full control of the mapping from LDAP attribute to public user object attribute. A public user object attribute is an attribute that is directly accessible on the user object. DTML code like "AUTHENTICATED_USER.email" is an example of accessing a directly accessible attribute on the user object. A lot of legacy DTML code relies on such attributes. Bugs fixed: * finduser() now lowercases all DN records from valid groups and compares it to a lowercased DN from any search results among user records. This fixes records not showing up if the capitalization in the group and on the user record is different. * When a user object was created the code expected a "mail" attribute on the LDAP record to set the email attribute used for compatibility with the Tracker. This has been repaired and will just default to an empty string. * Users who use tools like PADL's migration script end up with records that do not have the expected "sn" attribute. This is not set to a default value in finduser() to avoid errors in case it is not there. This will make the LDAPLoginAdapter compatible with user records of type posixAccount. **LDAPLoginAdapter 1.0** Bugs fixed: * Due to a bug in checking the return values from an LDAP search the cache can be polluted by invalid records for failed logins. This did not constitue a security breach, just more processing than necessary. **LDAPLoginAdapter 1.0beta3** Bugs Fixed: * Moved the LDAP search scope translation list from a volatile attribute on the LDAPLoginAdapter to a module-level attribute. This avoids any re-initialization calls. * Eliminated the extra attribute _v_loglines that counted the length of the log. A simple call to len(self._v_log) replaces it where log length info is needed. * Created one centralized method that handles connecting to and searching the LDAP server. This allows centralized error handling and makes for less and cleaner code. So far finduser, getUserDetails, getGroups, getUserNames and _lookupuser have been converted to use it instead of having their own connection code. * Rooted out error that would put a known user into the cache even though the password was not matched. This was not a security error since the broken user had the wrong password and failed any tests in validate() * Rigorous pruning of overly long lines of code to pare everything down to 80 chars width max * Avoiding unnecessary calls to the logging routine by checking for the correct log level *before* the call and not in the logging method. * Added a file, SAMPLE_RECORDS.txt, that shows a sample group- and user record. This will hopefully make it easier to understand the types of LDAP records needed. Features added: * Nicer Search screen adopted from the LDAPUserManager

1 0

DCOracle2 Alpha 5
by Matthew T. Kromer 21 Mar '01

21 Mar '01

I just packaged up DCOracle2 Alpha 5 on Zope.org. Given that there are no glitches or geez-I-shouldnta-changed-that-at-the-last-minute fixes present, I'm ready to have a wider set of people eyballing it. A few have, largely just from seeing it show up on the News column of Zope.org. If you use DCOracle, either with Zope/ZOracleDA or directly, and are interested in evaluating it, I am currently welcoming all feedback, from packaging, documentation, functionality, etc. While I am nominally subscribed to zope-dev, I route all its mail into a separate folder that -- surprise, surprise -- I don't read very frequently. I strongly encourage people to contact me directly with their comments or questions. I have NT builds and Unix/NT source available at http://www.zope.org/Members/matt/dco2 The NT build is against Oracle 8.1.7; I am not a real NT person so I don't know how portable that binary is. I am *NOT* interested in answering general Oracle questions; I'm trusting those who mail me will take this into consideration (i.e. if it isn't about DCOracle or DCOracle2...) This should build on Solaris with gcc and on Linux systems; I have no access to other platforms to try them. The 'make' command at the top directory should be sufficient to build from source on Solaris or Linux. Obviously, you need Oracle installed -- I get flaky behavior with Oracle 8.0 on Linux, but much better behavior with Oracle 8.1. Stupid database inserts (e.g. repeat 'INSERT INTO...' 100 times) seem to be about 25% faster than DCOracle. LOBS seem to work. Stored procedures (at least my simple ones) work. Complex stuff may not. I still have not done any REF CURSOR stored procedure testing, so that's probably quite buggy. Ditto automatic conversion for ROWIDs (see the documentation at how to get at the raw unconverted data). I get bad Oracle behavior (NULL data) trying to insert more than 8-10 rows with executemany() but it's very random and not visible where the problem is (it just *CANT* be an Oracle bug!) Anyone who wants to do platform migration to other 'nixes is encouraged to submit patches. If you rate the docs, please don't complain about formatting in the HTML version, as it's just a "save as..." HTML doc, and looks like it. The dco2documentation.aw file is the source document, but I've also provided postscript, rtf, and html versions. And, while there is a setup.py in the top level (for distutils) it isn't platform aware; Andreas Jung kindly provided it to me and I haven't spiffed it up, since I (like Majikthies and Vroomfondle) demand rigidly defined areas of doubt and uncertainty (read: I know how to do it better with shell scripts & makefiles). Thanks, Matt Kromer matt(a)digicool.com

1 0