- Zope-Dev - Zope lists

Establishing root objects in ZODB under Zope
by Ross Boylan 25 Jan '02

25 Jan '02

I have some data that will not naturally live as an item in a folder. If I'm using Zope, how do I establish a root for it? The ZODB docs talk about how to handle a free-standing database, but I don't see info about how to use the one that Zope has already set up. I recall there's some way to get a handle to the open database, but I don't recall exactly what. Can anybody help me out? If I use a class variable, will that be persisted automatically, e.g. class MyManager(Persistence.Persistent): MyClassVariable = SomePersistentClass() ..... ? (Actually, I'm not sure if it matters whether MyManager is a subclass of Persistent). Or, if it is not automatically persistent, is there anything I can do to make it persistent so that it will obey the transaction boundaries coming from web requests? Final question, which is distinct from the root objects issue: if I use Zope's Persistent List, will that avoid the problem of faulting in the whole list if I don't need it? I am looking for a good way to keep a record of transactions. ZODB's raw transaction recording is probably not quite right since it has the wrong granularity, it mixes a lot of unrelated transactions (it's only some I want), and I think it can get zapped if I do various database compactions and cleanups. Thanks.

2 3

Error 11
by Ahsan Imam 24 Jan '02

24 Jan '02

Hey Chris, 1) Installed Python 2.1.2 (with threads and without pymalloc) 2) Got the latest cvs built of zope 2.4. 3) Then compiled zope wo pcgi. 4) Even tried with the Zope 2.5 beta. Zope still keeps restarting every 10 to 15 minutes. Excerpt from the stupid.log: 2002-01-24T16:53:01 ERROR(200) zdaemon zdaemon: Thu Jan 24 09:53:01 2002: Aiieee! 21993 exited with error code: 11 ------ 2002-01-24T16:53:02 INFO(0) zdaemon zdaemon: Thu Jan 24 09:53:02 2002: Houston, we have forked ------ 2002-01-24T16:53:02 INFO(0) zdaemon zdaemon: Thu Jan 24 09:53:02 2002: Houston, we have forked ------ 2002-01-24T16:53:02 INFO(0) zdaemon zdaemon: Thu Jan 24 09:53:02 2002: Hi, I just forked off a kid: 22007 ------ 2002-01-24T16:53:04 PROBLEM(100) OFS.Application Duplicate Product name After loading Product 'Customizations' from '/usr/local/zslave2/Products', I skipped the one in '/usr/local/zope/lib/python/Products'. ------ 2002-01-24T16:53:13 INFO(0) ZODB Opening database for mounting: '148382768_1011864262.427182' ------ 2002-01-24T16:53:13 INFO(0) ZODB Mounted database '148382768_1011864262.427182' at /temp_folder ------ 2002-01-24T16:53:13 INFO(0) Zope Default Object Creation /usr/local/zope/lib/python/../../import/Examples.zexp examples import file could not be found. ------ 2002-01-24T16:53:13 INFO(0) ZServer HTTP server started at Thu Jan 24 09:53:13 2002 Hostname: node1.newtimes.com Port: 8080 ------ 2002-01-24T16:53:13 INFO(0) ZServer FastCGI Server (V1.0) started at Thu Jan 24 09:53:13 2002 IP : zslave2.newtimes.com Port : 8889 Socket path : None

3 2

Re: [Zope-dev] REQUEST.AUTHENTICATED_USER question
by vio 24 Jan '02

24 Jan '02

The point in a customised login method is precisely to do just that: validate user credentials with some custom scheme. If interested, this is trivial to do with a valid UserFolder instance around: 'if my_custon_loginForm_password == Users_folder.getUser(my_custon_loginForm_loginName)._getPassword(): and here SWITCH to the authenticated new user identity'.And Voila! No sweat. But I just don't know nor understand how to do that switch yet, 'programmatically'. * Jens Vagelpohl <jens(a)zope.com> [020121 09:02]: > the user gets modified automatically, provided you use common > login-methodology and a user folder that supports it. You must be referring to the routine HTTPResponse.HTTPResponse.unauthorised(), called with REQUEST.RESPONSE.unauthorised(). It just happens that I really don't like that 'Basic Authentication' dialog, that's why I want to use mine. So I've done half of the job to that end, only remaining problem is to switch 'programmatically' to the new authenticated user id. Doing something like 'REQUEST['AUTHENTICATED_USER'] = my_custon_loginForm_loginName' seems to have no effect, because the user is still 'Anonymous User' (found with 'AUTHENTICATED_USER.getUserName()'). If only I could understand where REQUEST gets its data for its 'AUTHENTICATED_USER' attribute, I could simply change that data source, and I'd be done. But I don't still understand how REQUEST gets all the data to its attributes. > > you don't set the user "manually". Of course you do ('programmatically' not 'manually'), as proven by all the customised 'login' products out there, who are doing just that. Only the one I studied so far (CookieCrumbler) seems to re-write the REQUEST.RESPONSE at each traversal. Which to me seems like a lot of overhead. If someone could point me to where Zope keeps user state (I believe with a cookie on the user's browser, but where in the source does Zope set this cookie up?), I could simply re-write that cookie with the new User ID ... Just a thought of a simple and elegant solution (aka 'magic bullet') for my problem. Vio > > jens > > > On Monday, January 21, 2002, at 12:35 , vio wrote: > > > Hi, > > Does anybody know what is the method call to modify the > > AUTHENTICATED_USER attribute? I am unable to trace where REQUEST feeds > > data for its AUTHENTICATED_USER attribute. > > > > Some context to my question: I am using a custom method to authenticate > > users coming to my site. So when the user logs in, he is 'Anonymous User' > > (from call: AUTHENTICATED_USER.getUserName()). But after his login name > > and password checked ok, how do I switch his identity in Zope from > > 'Anonymous User' to his/her new identity? What I am looking for is that > > next time I call 'REQUEST.AUTHENTICATED_USER.getUserName()' to get the > > new UserName he just logged in as, not 'Anonymous User' again. > > > > Examining CookieCrumbler.py source, this authentication product uses the > > 'before_publishing_traverse hook' mechanism. But isn't there a simpler > > way to do this than modifying REQUEST.RESPONSE at each traversal? Sounds > > like a lot of overhead. > > > > Vio > > > >

6 17

SOME ITEMS THAT YOU MAY BE INTERESTED IN OR BE ABLE TO ADVISE ME ON
by kriss rolo 24 Jan '02

24 Jan '02

These are the items that iam interested in selling.. Could you help me with some details on the goods, history, origin etc. are these worth anything and if so who would i contact with regards to selling them? and the best way to sell them ie auction etc APOLOGISE IF YOU HAVE ALREADY RECEIVED THIS E-MAIL JPEGS ARE AVAILABLE AT YOUR REQUEST MANY THANX kriss rolo tel: 0044 182760393 office (uk) 0044 1216864211 home (uk) 0044 7814294018 mobile (uk) return e-mail address krissrolo(a)aol.com UK ONLY VEHICLE REGISTRATION NUMBER N64 CON NINTENDO 64 CONSOLE item 1 hand carved round table with metal chain link in the middle item 2 magnum laurent perrier vintage 1988 champagne item 3 miniture football on stand from euro96 signed by pele and bobby charlton item 4 is a bit more interesting. its a protana minifon attache, as u will see ive enclosed notes from a web site regarding this and you will see back in the 50's it cost $340.00 so i could imagine this to be worth a bit. it also has an original tape inside i do not know what is on this tape, but judging by who made it and the cost of the machine, the tape could have some important information on it. heres the note..... The Minifon, developed in the early 1950s by Monske GMBH of Hanover(or by Protona GMBH- I'm not certain), was an ultra-miniaturized, battery operated magnetic recording device. It could not (initially at least) record the full range of sounds and was thus limited to voice recording, but it did offer easy portability in a very small package. The idea of offering a pocket dictating machine was novel, since dictation had previously been done in the office. However, it was thought that people like salesmen could take the machine "on the road" with them. Once on the market, the Minifon's promoters discovered that many people took advantage of the recorder's small size to make secret recordings to be used as evidence, as in court.<BR> <BR> The "legitimate" use of the Minifon, as a dictating machine, was somewhat problematical. Recordings made on regular dictating equipment were usually letters, and thus were normally sent almost immediately to a typist. The Minifon offered no obvious advantages over standard dictation equipment for office use, but its developers hoped to cultivate new uses for dictation equipment, such as stock taking in warehouses, or the use of the machine as a substitute for note-taking by reporters, insurance adjusters, salesmen, and others. In its original form, the Minifon was a wire recorder, using a type of wire medium developed by the Armour Research Foundation of Chicago and employed in many similar devices since the late 1940s. The machine at its introduction in 1952 had a recording time of one hour, which was remarkably long, and weighed only about 3 pounds at a time when a typical office dictating machine weighed upwards of 10 pounds. It accomplished this small size and light weight in part through the use of miniature tubes and clever mechanical design. The basic machine cost $289.50-- a price that sounds high today but was very much in line with competing office dictating machines. The parent company attempted to set up distribution, sales and service networks in the United States. It established a business office called the Minifon Export Corp in New York, and an existing company, Harvey Radio in New York City became the main distributor. Although smaller tape recorders appeared at about the same time, the main competition in the voice recording field was from an American company, Mohawk, which made a small, battery-operated cartridge tape recorder called the Migetape. Both products sold less than 10,000 units per year in the U.S.<BR> After a few years, the Minifon was modified to use transistors and magnetic tape, further lowering its weight and cost. By 1962 the basic machine weighed in at only 1.5 pounds. Competition by this time had helped bring the cost down to $249.50. The Minifon after about 1962 was distributed by the international conglomerate ITT through its subsidiary in the U.S., Federal Electric Corp. A little later, distribution was taken over by the ITT Distributor Products Division in Lodi, New Jersey. (I don't know whether these were the same company with different names) By the time ITT became associated with this product, it had taken on the name of Minifon "Attache," and a new line of models and options appeared. These included a hi-fi model, the 978H, which sold for $330.50.Usinga two-track, 1/4 inch tape cartridge operating at 1 7/8 inches per second, the machine claimed a frequency response of up to 12,000 Hz, plus or minus 3db. The coming of magnetic tape did not completely displace wire. The Model 240 series of recorders introduced in the early 1960s were probably the last wire recorders in regular production. The 240L, at a price of $269.50 used a special long-playing wire cartridge that held 4 hours of wire. Otherwise it looked like both the tape model and the 240S, which used a 2-hour wire cartridge and sold for $249.50. Another innovation was the introduction of more conventional recorders. After years of offering only "half" of a complete dictation system, Minifon finally developed a restyled, non-portable "office" machine, mainly for use by a transcriber, with pedal controls. By the mid-1960s, Minifon was trying to market its machines as multi-purpose devices suitable for nearly any recording need. In addition to the hi-fi and long-playing machines, the company offered an astounding variety of optional equipment such as foot controls, microphones, external amplifiers and loudspeakers, headsets, external power supplies, telephone recording attachments, conference recording adapters. One of the most interesting options were the miniature microphones intended to allow users to make "spy" recordings. In addition to a small tie-clip microphone, the Minifon could be equipped with a microphone disguised as a wrist- watch.

1 0

getting a dtmlfile from ZODB instead of the file system.
by Romain Slootmaekers 24 Jan '02

24 Jan '02

Yo, Most of the products that were developed using code instead of ZClasses. The problem i have is that the forms for management are always created on the file system, like this: index_html = DTMLFile('www/index_html', globals()) I really would like the index_html file to come from the ZODB instead of the file system, so how do I do that? I suspect opening a database object with from ZODB import FileStorage, DB storage = FileStorage.FileStorage('var/data.fs') db = DB(storage) connection = db.open() root = connection.root() and looking it up is not the ideal solution, fi I don't know what will happen with ohter threads accessing the same object aso. So How do I do that ? TIA, Sloot.

3 2

problem in adding objects to the ZCatalog
by sanjay singh 24 Jan '02

24 Jan '02

Hi all, I m installing Zope 4.2.1 on Windows 2000.After getting it installed, and starting , when i try to add objects to the Z Catalog which is created one level down the site root folder(/epsite), when i select dtml documents without selecting the id and i click Find and Catalog, its giving the following error : Zope Error Zope has encountered an error while publishing this resource. Error Type: AttributeError Error Value: __call__ -------------------------------------------------------------------------- Troubleshooting Suggestions a.. The URL may be incorrect. b.. The parameters passed to this resource may be incorrect. c.. A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to the HTML source for this page. If the error persists please contact the site maintainer. Thank you for your patience. Traceback (innermost last): File C:\PROGRA~1\EIP\lib\python\ZPublisher\Publish.py, line 223, in publish_module File C:\PROGRA~1\EIP\lib\python\ZPublisher\Publish.py, line 187, in publish File C:\PROGRA~1\EIP\lib\python\Zope\__init__.py, line 226, in zpublisher_exception_hook (Object: LockableItem) File C:\PROGRA~1\EIP\lib\python\ZPublisher\Publish.py, line 171, in publish File C:\PROGRA~1\EIP\lib\python\ZPublisher\mapply.py, line 160, in mapply (Object: manage_catalogFoundItems) File C:\PROGRA~1\EIP\lib\python\ZPublisher\Publish.py, line 112, in call_object (Object: manage_catalogFoundItems) File C:\PROGRA~1\EIP\lib\python\Products\ZCatalog\ZCatalog.py, line 393, in manage_catalogFoundItems (Object: LockableItem) File C:\PROGRA~1\EIP\lib\python\Products\ZCatalog\ZCatalog.py, line 727, in ZopeFindAndApply (Object: LockableItem) File C:\PROGRA~1\EIP\lib\python\Products\ZCatalog\ZCatalog.py, line 727, in ZopeFindAndApply (Object: LockableItem) File C:\PROGRA~1\EIP\lib\python\Products\ZCatalog\ZCatalog.py, line 715, in ZopeFindAndApply (Object: LockableItem) File C:\PROGRA~1\EIP\lib\python\Products\ZCatalog\ZCatalog.py, line 498, in catalog_object (Object: LockableItem) File C:\PROGRA~1\EIP\lib\python\Products\ZCatalog\Catalog.py, line 381, in catalogObject File C:\PROGRA~1\EIP\lib\python\Products\ZCatalog\Catalog.py, line 494, in recordify AttributeError: (see above) Also tell me how to select and add all documents to the Z catalog and get it searchable. Do tell me fast. thanks in advance, Sanjay

2 1

ZODBCDA
by Christian Theune 23 Jan '02

23 Jan '02

Hi. Currently I have following problem: I am connecting to a postgres database via ZODBCDA, which works well most time. When I create an ``large'' query (insert statement with base64 encoded binary) of about 80kbyte zope will halt on an signal 11. I don't know if this relates to the problems discussed earlier on this list. I traced it down to be a problem in the shared library (sql.so) brought with ZODBCDA. Due to my lack of knowledge on C and the python API I get stuck on this. The last thing i know: the crash happens in SQLExecDirect, callen from db.py in line 201 (+/- 3 lines). Thanks for helping Christian -- Christian Theune - ct(a)gocept.com gocept gmbh & co.kg - schalaunische strasse 6 - 06366 koethen/anhalt tel.+49 3496 3099112 - fax.+49 3496 3099118 mob. - 0178 48 33 981 reduce(lambda x,y:x+y,[chr(ord(x)^42) for x in 'zS^BED\nX_FOY\x0b'])

2 1

Re: Python 2.1.2 does not fix the signal 11 crashing problem !!!!!!!!!!!
by Anthony Baxter 23 Jan '02

23 Jan '02

>>> Harald Koschinski wrote > Hallo, > > after switching to python 2.1.2 compiled with GC > (intranet:/usr/local/src/Python-2.1.2 # ./configure --without-pymalloc) > the crashes are back again :-((((((((((((((((((((((( > Which version of Zope? Does it have the RestrictedCompiler fix? As far as I am aware, Zope 2.4 includes it's own version of the Compiler code, and the current release of 2.4 still has the stacksize bug. Anthony -- Anthony Baxter <anthony(a)interlink.com.au> It's never too late to have a happy childhood.

5 5

Re: [Zope-dev] Re: Python 2.1.2 does not fix the signal 11 crashing problem !!!!!!!!!!!
by Anthony Baxter 23 Jan '02

23 Jan '02

>>> Behrens Matt - Grand Rapids wrote > Anthony Baxter wrote: > > > In that case, how about cutting a version which is 2.4.3 + the compiler > > fixes? Crashes are bad, and it would be very nice to Make Them Go Away. :) > > You already have that. Check out the Zope-2_4-branch from CVS (see > http://dev.zope.org/CVS for info). Now leave poor Matt alone :-) I know - I do have this. Plenty of other people, tho, do NOT have the ability to build their own version of Zope. Requiring people to follow a somewhat arcane set of instructions and steps merely to get a stable version of Zope that doesn't crash strikes me as... odd. Anthony

4 3

Re: [Zope] install problem in 2.50b4 on RedHat 7.2
by Ricardo L. A. Bánffy 22 Jan '02

22 Jan '02

Thanks, Chris I solved the problem with a less draconian rm lib/python2.1/test/nocaret.py lib/python2.1/test/test_future3.py lib/python2.1/test/test_future4.py lib/python2.1/test/test_future5.py lib/python2.1/test/test_future6.py lib/python2.1/test/test_future7.py or, with reading enhancements (and mail compatibility) rm lib/python2.1/test/nocaret.py lib/python2.1/test/test_future3.py lib/python2.1/test/test_future4.py lib/python2.1/test/test_future5.py lib/python2.1/test/test_future6.py lib/python2.1/test/test_future7.py which are the files install complained of. I suspect I didn't really need to remove the first one. If someone cares to test, I won't object... ----- Original Message ----- From: "Chris Kratz" <chris.kratz(a)vistashare.com> To: "Clint Brubakken" <cabrubak(a)inetic.com>; <zope(a)zope.org> Sent: Tuesday, January 15, 2002 7:54 PM Subject: Re: [Zope] install problem in 2.50b4 on RedHat 7.2 > Hello Clint, > > I ran into the same problem today. I found that if I cleared all the test > scripts, the install script ran to completion. There are probably less > draconian methods for fixing the problem, but it got my test zope up and > running without problems. In a shell, something like > > rm -f > /usr/cabrubak_software/tgzs/zope/Zope-2.5.0b4-linux2-x86/lib/python2.1/test/ * > > should work. > > ***But, be forwarned, this will clear all scripts from this directory. > > Alternatively, you could track down each one that causes a problem and remove > it. I gave up on that approach after the third one had a problem. > > good luck, > > -Chris > > On Tuesday 15 January 2002 04:00 pm, Clint Brubakken wrote: > > I'm getting the : > > Compiling python modules > > File > > "/usr/cabrubak_software/tgzs/zope/Zope-2.5.0b4-linux2-x86/lib/python2.1/tes > >t/nocaret.py", line 2 > > [x for x in x] = x > > SyntaxError: can't assign to list comprehension > > SyntaxError: from __future__ imports must occur at the beginning of the > > file (test_future3.py, line 3) > > SyntaxError: from __future__ imports must occur at the beginning of the > > file (test_future4.py, line 3) > > SyntaxError: from __future__ imports must occur at the beginning of the > > file (test_future5.py, line 4) > > SyntaxError: from __future__ imports must occur at the beginning of the > > file (test_future6.py, line 3) > > SyntaxError: from __future__ imports must occur at the beginning of the > > file (test_future7.py, line 3) > > > > > > > > which I've seen on the list to ignore, but it stops with a message: > > > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > >!!! There were errors during Python module compilation. > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > >!!! > > > > and doesn't create the start, zope.cgi, or inituser files > > > > > > _______________________________________________ > > Zope maillist - Zope(a)zope.org > > http://lists.zope.org/mailman/listinfo/zope > > ** No cross posts or HTML encoding! ** > > (Related lists - > > http://lists.zope.org/mailman/listinfo/zope-announce > > http://lists.zope.org/mailman/listinfo/zope-dev ) > > -- > Chris Kratz > Systems Analyst/Programmer > VistaShare LLC > www.vistashare.com > > _______________________________________________ > Zope maillist - Zope(a)zope.org > http://lists.zope.org/mailman/listinfo/zope > ** No cross posts or HTML encoding! ** > (Related lists - > http://lists.zope.org/mailman/listinfo/zope-announce > http://lists.zope.org/mailman/listinfo/zope-dev ) > >

1 0