- Zope-Dev - Zope lists

ANN: Proposal for ZCatalog "drop-in" indexes
by Chris McDonough 29 Mar '01

29 Mar '01

Hi all, I'd like comments on this proposal if you've got the time: http://dev.zope.org/Wikis/DevSite/Proposals/DropInIndexes It deals with the implementation of "drop-in" ZCatalog indexes. Thanks! - C

1 0

Re: [Zope-dev] Problem with Hotfix 2000-10-11 on 2.1.6
by Gregor Hoffleit 29 Mar '01

29 Mar '01

On Thu, Mar 29, 2001 at 10:10:50PM +1000, Zac Stevens wrote: > Howdy, > > On Thu, Mar 29, 2001 at 01:28:13PM +0200, Gregor Hoffleit wrote: > | 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." > > I think you're just making a minor braino here - 2.1.6 isn't higher than > 2.2.0 > > The Readme is somewhat ambiguous though - it starts off stating that "all > versions up to and including 2.2.2" are affected, but then recommends "Zope > 2.2.x" sites upgrade. Perhaps it isn't even a genuine issue for 2.1.6? > (I don't know) Ooops, sorry, sorry, sorry. I had read the start of the README (like you wrote: 'Zope versions up to and including Zope 2.2.2.'), but I had quoted and paragraph that indeed implied an answer to my question ('will work for all versions of Zope 2.2.0 and higher.'). So 2.1.6 ought to be vulnerable as well, but that Hotfix won't work for it. Gregor

2 2

Re: Zope on OpenBSD 2.8 makes me cry
by Alexander Limi 29 Mar '01

29 Mar '01

andrew fabbro afabbro(a)indoctrination.com wrote: > I'm pulling out my hair trying to get Zope working on OpenBSD 2.8. I I'll repeat my original post, and the 2.7 libc can be found at http://mp3.no/openbsd/libc_r.so.3.0 (not indefinitely, though) I hope the file is OK, I have a shitty connection at the moment, and I haven't got the time to verify it right now. (from http://lists.zope.org/pipermail/zope-dev/2001-January/009137.html) For those of you wishing to run Zope on OpenBSD 2.8, here is a solution. The reason Zope doesn't work in the first place is a thread bug in the OpenBSD 2.8 release version. The solution is to use the libc_r from OpenBSD 2.7 for the Zope instance. Thanks to Jason Ish for the howto, I thought I would rewrite it to be more generic and post it to the lists. So, here we go: Python on OpenBSD 2.8 uses /usr/lib/libc_r.so.3.1. libc_r.so.3.1 is from 2.8, libc_r.so.3.0 is from 2.7 and will work. So what we do is to copy the old libc file (if you don't have it, mail me and I'll send it to you) into a directory in the Zope install dir, and add that to the path. Then we rename the old file so the system thinks it is the curent version. In this example, I assume your Zope install is in /usr/local/zope. First, we copy the old library into our Zope dir, and rename it: cp /usr/lib/libc_r.so.3.0 /usr/local/zope/libc_r.so.3.1 Then you should add something like this to the top of your "start" script: export LD_LIBRARY_PATH=/usr/local/zope Start Zope, and you will find that it works fine now. Zope also works fine in the CURRENT tree of OpenBSD, so presumably it will work out-of-the-box on OpenBSD 2.9. This is the safest way of getting it to work at the moment. Happy OpenBSD'ing :) -- Alexander Limi alexander(a)limi.net

1 0

Re: recent CVS update: dc/pyexpat, also: cPersistence stuff
by Jens Quade 28 Mar '01

28 Mar '01

Steve Spicklemire <steve(a)spvi.com> writes: > Hmm.. anybody seen this? Yes, but it's already gone... See http://lists.zope.org/pipermail/zope-checkins/2001-March/date.html for details. Anyway, I had to remove lib/python/Shared/DC/xml/pyexpat/Setup manually to build dcpyexpat.o, which was renamed last night. jens -- Shipping software is an unnatural act

1 0

Re: [Zope-dev] Memory problems with ParsedXML ?
by Dieter Maurer 28 Mar '01

28 Mar '01

Godefroid Chapelle writes: > I have imported about 2500 xml files in ParsedXML objects through the > use of : > ... > But when trying to browse the folder containing the ParsedXML instances, > a whole lot of memory is used by Zope and it took my machine down. Are you sure, you want to browse 2,500 objects? Zope must load all objects, build a really big HTML page transfer it to the user's browser which will have a hard time to render this monster. I am sure, you want to organize your objects in a sensible way.... Dieter

1 0

ZopeSecurityPolicy & this()
by Petr Knapek 28 Mar '01

28 Mar '01

Hi Zopists, I have now problem with executable content where this() is called. My problem: I have this structure in ZODB / |_ acl_users (Zope default) |_ dalmatin (ISNG Folder) * ownes user who is in role Manager from /dalmatin/acl_users |_ acl_users (Modified LDAPAdapter) |_ index (ISNG Document) ** ownes user who is in role Manager from /dalmatin/acl_users * ISNG Folder is my python product which is created from Folder ( ISNGFolder(Folder) ) ** ISNG Document is my python product, it is created from DTML Document ( ISNGDocument(DTMLDocument) ) In index I call this: <dtml-if "AUTHENTICATED_USER.hasRole('nextra.cz', this())"> ... and when I try to execute index also when I am in role Manager from /dalmatin/acl_users, an Zope error is raised that I am not autorized to access object this. Zope Error Zope has encountered an error while publishing this resource. Unauthorized You are not authorized to access this. Traceback (innermost last): File /usr/local/Zope-2.3.0-src/lib/python/ZPublisher/Publish.py, line 222, in publish_module File /usr/local/Zope-2.3.0-src/lib/python/ZPublisher/Publish.py, line 187, in publish File /usr/local/Zope-2.3.0-src/lib/python/ZPublisher/Publish.py, line 171, in publish File /usr/local/Zope-2.3.0-src/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: index) File /usr/local/Zope-2.3.0-src/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: index) File /usr/local/Zope-2.3.0-src/lib/python/OFS/DTMLDocument.py, line 189, in __call__ (Object: index) File /usr/local/Zope-2.3.0-src/lib/python/DocumentTemplate/DT_String.py, line 538, in __call__ (Object: index) File /usr/local/Zope-2.3.0-src/lib/python/DocumentTemplate/DT_Util.py, line 328, in eval (Object: AUTHENTICATED_USER.hasRole('nextra.cz', this())) (Info: this) File /usr/local/Zope-2.3.0-src/lib/python/OFS/DTMLMethod.py, line 261, in validate (Object: index) File /usr/local/Zope-2.3.0-src/lib/python/AccessControl/SecurityManager.py, line 144, in validate File /usr/local/Zope-2.3.0-src/lib/python/AccessControl/ZopeSecurityPolicy.py, line 199, in validate Unauthorized: (see above) Can somebody help me to solve my problem with ZopeSecurityPolicy? Zope 2.3.0 (compiled from sources) on Debian -- Petr Knápek NEXTRA Czech Republic, s.r.o., Hlinky 114, 603 00 Brno, Czech Republic e-mail: mailto:petr.knapek@nextra.cz tel:+420-5-43 554 150 FAX:+420-5-43 554 214 "Perl is worse than Python because people wanted it worse." Larry Wall, 14 Oct 1998

1 0

Memory problems with ParsedXML ?
by Godefroid Chapelle 28 Mar '01

28 Mar '01

Hi, I have imported about 2500 xml files in ParsedXML objects through the use of : manage_addProduct['ParsedXML'].manage_addParsedXML(id, '', xmlString) This works perfectly. But when trying to browse the folder containing the ParsedXML instances, a whole lot of memory is used by Zope and it took my machine down. Have I done something wrong or does this info help you debug the product ? Hope this help. -- Godefroid Chapelle BubbleNet sprl rue Victor Horta, 30 1348 Louvain-la-Neuve Belgium Tel 010 457490 Mob 0477 363942 TVA 467 093 008 RC Niv 49849

1 0

Btree problems on recent CVS update..
by Steve Spicklemire 28 Mar '01

28 Mar '01

Hmm.. anybody seen this? -steve cc -fpic -I../Components/ExtensionClass/src -I../Components/BTree -I./ZODB -O -pipe -D_THREAD_SAFE -I/usr/local/include/python1.5 -I/usr/local/include/python1.5 -DHAVE_CONFIG_H -c ./../Components/BTree/BTree.c ./../Components/BTree/BTree.c: In function `BTreeItems_item_BTree': ./../Components/BTree/BTree.c:249: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c:249: (Each undeclared identifier is reported only once ./../Components/BTree/BTree.c:249: for each function it appears in.) ./../Components/BTree/BTree.c: In function `BTreeItems_item': ./../Components/BTree/BTree.c:299: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `bucket_index': ./../Components/BTree/BTree.c:471: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `_bucket_get': ./../Components/BTree/BTree.c:509: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `BTree_index': ./../Components/BTree/BTree.c:596: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `_BTree_get': ./../Components/BTree/BTree.c:647: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `_bucket_set': ./../Components/BTree/BTree.c:749: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `BTree_grow': ./../Components/BTree/BTree.c:961: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `_BTree_set': ./../Components/BTree/BTree.c:1028: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `bucket_keys': ./../Components/BTree/BTree.c:1099: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `bucket_values': ./../Components/BTree/BTree.c:1129: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `bucket_items': ./../Components/BTree/BTree.c:1159: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `bucket_clear': ./../Components/BTree/BTree.c:1209: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `BTree_clear': ./../Components/BTree/BTree.c:1265: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `bucket_getstate': ./../Components/BTree/BTree.c:1294: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `BTree_getstate': ./../Components/BTree/BTree.c:1759: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `BTree_elements': ./../Components/BTree/BTree.c:1851: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `Bucket_length': ./../Components/BTree/BTree.c:1986: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `BTree_length': ./../Components/BTree/BTree.c:2002: `cPersistenceCAPI' undeclared (first use in this function) ./../Components/BTree/BTree.c: In function `initBTree': ./../Components/BTree/BTree.c:2122: `cPersistenceCAPI' undeclared (first use in this function)

1 0

LoginManager question
by Bertrand Croq 28 Mar '01

28 Mar '01

Hi, I am currently using LoginManager to authenticate users from a MySQL database. I followed the tutorials and it works quite well; but there are other data associated with users in the database that I would like to use in Zope. I have found a solution but I think it is quite complicated: - first, I added SQL_id_user (ZSQL-method) in the acl_users: select id_user from user where <dtml-sqltest username column=user_name type=string> - then, I added id_user (DTML-method) in the acl_users: <dtml-in expr="SQL_id_user(username=username)"> <dtml-return id_user> </dtml-in> - now, when I want to get the id_user value associated with the current user, I need to do: <dtml-with REQUEST> <dtml-var expr = "AUTHENTICATED_USER.id_user( AUTHENTICATED_USER, username=AUTHENTICATED_USER )" > </dtml-with> Isn't there an easier way to get the id_user value? -- Bertrand Croq - VIRTUAL NET (http://www.virtual-net.fr) 80, avenue des Buttes de Coesmes - 35700 RENNES tel: +33 2 23 21 06 30 - fax: +33 2 99 38 16 85

2 2

Re: [Zope-dev] FTP interface being worked on?
by Karl Anderson 27 Mar '01

27 Mar '01

"Chris McDonough" <chrism(a)digicool.com> writes: > I don't think it's reasonable or wise to impose any "master > structure" for filesystem serialization of bodies of > objects. Each instance (or perhaps each class) should > define how best to serialize itself to disk. > Representations between classes are likely to be radically > different. A place for standardization is in the > "properties" file(s) which accompany each object rep... this > is likely to be XML or another structured variant. Is there a motivation for using serialization to provide an editable "god's eye view" of all or part of a Zope site? That is, provide a two-way XML serialization at any stage of the managed hierarchy of a site? That way, XML tools could be used as stream editors at any level, to the extent that the serialization is understandable. So, for example, we'd have ways to not just alter a template or content that gets templatized, but the containers that organize them, and related metadata or content that isn't as near. This links well with the standardization that you mention - objects can have arbitrary serialization formats, but if certain attributes that we're interested in are recognizable, those attributes could be edited on a containerwide level. So, if we had arbitrary objects that we wanted to have an effect on content or display, the same XML tools could be used to manage them all, limited only by the ability of those tools to slog through a level of the hierarchy. This is kind of stream-of-consciousness talk, and might be more silly than realistic; certainly, if the objects didn't guard how they could be updated, a misconfigured tool could waste them without warning. There's a similar project called psilib that was discussed in xml.com: <http://www.xml.com/pub/a/2000/03/22/psi/index.html> -- Karl Anderson karl(a)digicool.com

6 10