February 2000 - Zope

urgent UserDB question
by Sam Gendler 24 Feb '00

24 Feb '00

Has anyone seen the following behaviour? If I set the UserDb to be in cookie mode and I access a page that I am unauthorized to view, I get the docLogin page. The docLogin page has a built in html header, and when it gets delivered the standard_html_header also gets included, so there are 2 headers. However, if a user is trying to access a document inside a folder that needs authorization, the user is unable to retrieve the standard_html_header, so they get an ugly page, lacking all of the header content I thought I would resolve this by adding the contents of the standard_html_header and footer to the docLogin, and then putting a special hack in standard_error_message that checks for a LoginRequired Exception, and skips the inclusion of the standard_html_header if serving the docLogin. However, as soon as I replace the top of the docLogin property of the UserDb, instead of sending the docLogin form, it raises the Unauthorized exception, which results in a username/password dialog box from netscape. With the header, by docLogin ends up being about 4200 bytes. Is there maybe a 4096bytes limit on the docLogin property? Has anyone else solved this problem? If so how. Please cc my own email account with your response. --sam -- -------------------------- Sam Gendler CTO, Impossible, Inc. 1222 State St. Suite 250 Santa Barbara, CA. 93101 p: 805-560-0508 f: 805-560-0608 c: 805-689-1191 e: sgendler(a)impossible.com

1 0

(no subject)
by Curtis Maloney 24 Feb '00

24 Feb '00

Greetings, Well... looks like i've found out the problem... SiteAccess doesn't seem to like working with GUF all that much. After removing the SiteAccess product, i had 0 (cont them, ZERO) problems getting back into my directory... so.... all those with their brains in D (for Damage) will now be expecting me to ask something like "How do I stop this, because I need SiteAccess!??!!?!" And so I don't need to ask... just wait for the reply. Have a better one, Curtis.

1 0

XMLDocument "WrongDocument" error and object comparision...
by Anthony Baxter 24 Feb '00

24 Feb '00

I'm playing with XML Document, and I'm finding that I'm getting a bogus WrongDocument error from the sample file. If I open up the 'slides' document and hit 'Change' I'm getting a WrongDocument exception at line 433 of Node.py. if document and ownerDocument and document != ownerDocument: raise ZDOM.WrongDocumentException() (I also see this when I try to create a new document) Putting a print "DOC", document, ownerDocument print "DOC2", id(document), id(ownerDocument) on the line before it gives back DOC <Document instance at 863bf90> <Document instance at 863bf90> DOC2 139736152 139811552 so they _look_ like the same object, but comparision is failing. On a hunch, I tried changing the code to compare document.aq_base and ownerDocument.aq_base, and this works. I have _no_ idea if this is correct, though. I'm running the latest CVS, including Jim's changes to Acquisition.c (r1.36) for numeric object comparision - could this be the problem? anyone? Anthony (patch to make it work for me: ) --- Node.py 2000/02/05 00:33:16 1.18 +++ Node.py 2000/02/24 04:17:55 @@ -430,7 +430,7 @@ raise ZDOM.HierarchyRequestException('Node type does not support children.') document=newChild.getOwnerDocument() ownerDocument=self.getOwnerDocument() - if document and ownerDocument and document != ownerDocument: + if document and ownerDocument and document.aq_base != ownerDocument.aq_base: raise ZDOM.WrongDocumentException() if newChild.getNodeType() == DOCUMENT_FRAGMENT_NODE: newChildren=newChild

1 0

FW: getPreviousSibling (PLEASE HELP)
by RC Compaan 24 Feb '00

24 Feb '00

-----Original Message----- From: RC Compaan [mailto:sparroy@adept.co.za] Sent: 20 February 2000 10:51 To: Zope Subject: FW: getPreviousSibling I still haven't found a solution for the following problem. Help would be greatly appreciated: -----Original Message----- From: RC Compaan [mailto:roche@up-front.co.za] Sent: 17 February 2000 01:57 To: Zope Subject: getPreviousSibling I have a list of folders containing thumbnail images. In each folder I make a link to the previous and next folder with "getPreviousSibling" and "getNextSibling". This works perfectly in all folders except for the first one. This is my code: <dtml-if getPreviousSibling> <dtml-with getPreviousSibling> <a href="<dtml-var absolute_url>"><< <dtml-var title_or_id></a> </dtml-with> </dtml-if> And Zope says: Error Type: SystemError Error Value: infinite recursion in document template My logic says <dtml-if getPreviousSibling> should return "none" for the first folder like <dtml-if getNextSibling> returns none for the last folder in the list. What could it be? roché

1 0

Portal objects holding other objects
by Dale Lance 24 Feb '00

24 Feb '00

Hi, I'm not quite sure where my problem is. I created my own portal object. It works fine. It adds, deletes and changes just fine. Then I added an attribute that is a Folder (plain Zope Folder object). This attribute holds a list of Images. It works fine. Next I added another attribute that is a Folder to hold a list of my new object - Rate I have tried several approaches to this but can't seem to get the Rate object to work Any Ideas? p.s. Sorry about the dual post but wasn't quite sure if this is a general Zope question or something peculiar to PTK Dale Zope Error Zope has encountered an error while publishing this resource. Debugging Notice Zope has encountered a problem publishing your object. Cannot locate object at: http://myserver:8080/mysite/Members/user1/1/rates/manage_addRate ---------------------------------------------------------------------------- ---- Troubleshooting Suggestions The URL may be incorrect. The parameters passed to this resource may be incorrect. 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 /usr/local/Zope/lib/python/ZPublisher/Publish.py, line 214, in publish_module File /usr/local/Zope/lib/python/ZPublisher/Publish.py, line 179, in publish File /usr/local/Zope/lib/python/Zope/__init__.py, line 202, in zpublisher_exception_hook (Object: 1) File /usr/local/Zope/lib/python/ZPublisher/Publish.py, line 151, in publish File /usr/local/Zope/lib/python/ZPublisher/BaseRequest.py, line 338, in traverse File /usr/local/Zope/lib/python/ZPublisher/HTTPResponse.py, line 521, in debugError NotFound: (see above)

1 0

meta type conversion method, Document to Method... help!
by Alex Schonfeld 24 Feb '00

24 Feb '00

Basically the idea is to have it go through and convert all dtml docs to dtml methods. BUT the problem is "index_html" of Document type also have a attribute ".index_html" which is causing problems with the conversion. Thus my special case code. Any ideas or tips would be appreciated. This code is being used to convert all the old style docs to methods for use with Zope2. Thanks! --------------convermetatypes, DTML Method---------------- <html> <body> <dtml-let from_type="'DTML Document'" to_type="'DTML Method'" tmpindex="_.getitem('index_html',0)" tmpraw="tmpindex.raw"> <dtml-comment> and update the called methods............... </dtml-comment> <dtml-in "objectValues(from_type)"> <dtml-let method="_.getitem('sequence-item', 0)" method_id="method.id()" method_title="method.title" method_data="method.raw"> <dtml-if "method_id != 'convertmetatypes'"> Deleting <dtml-var from_type>-<dtml-var method_id>. <dtml-call "manage_delObjects([method_id])"> <dtml-call "manage_addDTMLMethod(id=method_id, title=method_title)"> Creating new <dtml-var to_type>-<dtml-var method_id>. <dtml-let newdoc="_.getitem(method_id,0)"> <dtml-if "newdoc"> Adding data to new <dtml-var to_type>-<dtml-var method_id>. <dtml-call "newdoc.manage_edit(data=method_data, title=method_title)"> <dtml-else> Adding data to new <dtml-var to_type>-<dtml-var "tmpindex.id()">. <dtml-call "tmpindex.manage_edit(data=tmpraw, title=tmpindex.title)"> </dtml-if> </dtml-let> </dtml-if> </dtml-let> </dtml-in> </dtml-let> </body> </html> ---------------------- 1010011010 0 Digital Garage 1 Alex Schonfeld 0 alex(a)garage.co.jp - pear 1 090-4429-2323 +-Personal Junk | alex(a)coolest.com | http://www.coolest.com

1 0

Re: [Zope-dev] Zope Debugging Tips Solicited
by Hung Jung Lu 24 Feb '00

24 Feb '00

"james w. howe" <jw-(a)allencreek.com> wrote: >I can do with it. Any debugging tips that anyone might have would be >appreciated. The Python/Zope combination does not seem to have any nice GUI for debugging... nothing like Visual C++ or Visual Cafe. But then, I have also worked with a few languages where I had only access to simple print statements... At first this might seem to be primitive, but one thing saves the day: in these languages you can modify most program files while the main application is running, like the case of Zope. (Long-running processes.) What I do nowadays for Zope is this: (1) In the standard_footer_html method (or equivalent), I print out whatever variable I want to print out. This includes a string that I store in the REQUEST variable, which you may call debug_output. Typically I print out three things: (a) REQUEST.debug_output, (b) the SESSION variables, (c) the REQUEST variable. (2) I have a flag in the root folder, and setting or unsetting this flag enables or disables the print out. So, when I move the development copy to the production copy, I simply have to unset the flag to suppress the debug printing. (3) I implement an external method called dprint(), and put it in the root folder. This method prints into the REQUEST.debug_output string. I can print from any dtml method/document, something like: <dtml-call "dprint('Hallo I am here')"> <dtml-call "dprint(REQUEST.myvar)"> You of course can also call the dprint() method from within external methods... or maybe you can implement it as a real Python module and put it inside your /lib/python/shared/... folder so you can import it from an external method file. --------------------------- The above method is good only if the program does not have crashes (Zope exceptions.) For nastier crashes, I physically go into the Python code and put print statements, so it prints to the console. Primitive, yes, but so far I have always been able to catch the bugs I wanted to catch, including a few from Zope itself and Sybase database adapter. --------------------------- Of course, if there were some product that implements a real debug para-server (serving on a TCP/IP port, so it's platform independent) with nice HTML GUI interface to poll (or even change) variable values via a web, and even stepping through the code, now, that'll be a wonderful product. :) Hung Jung ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

1 0

Re: [Zope] Private Product Objects (was: object icons)
by Tres Seaver 24 Feb '00

24 Feb '00

Loren Stafford <lstaffor(a)dynalogic.com> writes: > > Now that I've had breakfast and thought about this a little more, I see > there is broader issue: how to handle the special needs of objects that are > private to a product. My product is an event scheduler. (Terry, who started > the "object icons" thread, may have a different situation. Jump in and tell > us about your product, Terry.) The Scheduler product registers an > catalog-aware Event class so user's can define scheduled events. The product > keeps track of all Events in a ZCatalog "Schedule". Now, Schedule is a > persistent object and has a class definition, but the one and only instance > is created by the product and load time, if an instance doesn't already > exist. The Schedule has some special usage requirements: > > 1. There should be only one instance. That's why its class is not > registered. Hmm, I guess I don't see the necessity of making it a Singleton here. Suppose you need to segregate events into separate priority classes, or guarantee that, when executed, the run with the permissions of different users? Splitting up the schedule _might_ not be a terrible thing to do. Your default case could then just require dropping a single instance of the Schedule class at the root of your Zope hierarchy, and leaving it there. > > 2. It probably shouldn't show up on users' navigation bars and folder lists. > This probably is not a problem, because Schedule has a unique meta-type. But > that's not a watertight solution. A standard method for marking it invisible > would be better. If Schedule derives from ZCatalog, as it seems, and the Event class uses the well-known schedule ID as its default_catalog_id, then it isn't even necessary to "contain" the events within the schedule object -- they will find it anywhere above them in the tree by acquisition (think "uncle Schedule" instead of "papa Schedule"). > > 3. If and when it does show up (as on the manage_main menu) it should be > identified with the product (to avoid the "Whaz dis?" confusion). That's why > I want it to have an icon that shows it is part Scheduler product. Solved if Schedule is an "ordinary" ZClass. > > 4. No one, not even a manager, should be able to delete it accidently. You > can make an object undeletable by putting its ID in the list of reserved > names, but I have found, during development of Scheduler, that this hack > causes more problems than it's worth. I might settle for letting be deleted > by a manager. Again, solved for "ordinary" ZClass instances -- just set the permissions so. > > 5. When the product is deleted (I mean really deleted, because you don't > want to use it anymore), the Schedule should be deleted too. Failing this, > it should at least be deletable (an iffy situation, if you use the > reserved_names hack). On the other hand, if you are just updating the > product code, you probably don't want to delete the Schedule object. It may > contain scheduled events. This is complicated by the fact that when you load > a product, Zope first deletes the old product. So a manage_beforeDelete > method can't distinguish between a "real" delete and a code update. I've > also discovered that any error in a product's manage_beforeDelete method > makes the product not only undeletable, but (because of the implicit delete) > unupdatable (un-update-able)! > > (Hmmm. There's an idea. You could make any object, including the Schedule, > undeletable by giving it a manage_beforeDelete method that raises an error.) > > 6. The Schedule need to have a "well known" ID (I think). This is for use in > the default_catalog property of the events. I wouldn't want someone to > change the ID of the Schedule arbitrarily. This may be the same problem as > accidental deletion. You can override the setId() method to prefent changing the id; BasicUserFolder does this:: def _setId(self, id): if id != self.id: raise Globals.MessageDialog( title='Invalid Id', message='Cannot change the id of a UserFolder', action ='./manage_main',) > > Anyway, I thought I'd mention this use case, so that changes to the Zope > product API at least don't make implementation of such products any harder > than they already are, and perhaps make them easier. > > Got any suggestions for the short or long term? Sounds like an interesting project! Tres. -- ========================================================= Tres Seaver tseaver(a)palladion.com 713-523-6582 Palladion Software http://www.palladion.com

2 1

manage_exportObject
by Daniel G. Rusch 23 Feb '00

23 Feb '00

All Does anyone know how to export an object (Folder or such) from outside of the Folder that contains the item to be exported without hard coding the path. In otherwords I would like to be able to have a user interface which would allow a person, with an export role, to be able to enter a list of fully qualified Items to be exported. Consider: FolderA FolderB ItemToExport I can export ItemToExport from FolderA by calling: <dtml-with "FolderA.FolderB"> <dtml-call "manage_exportObject(id='ItemToExport')"> </dtml-with> but I don't want the FolderA.FolderB to be hard coded. I would like it to be a var that I pass into the method. Something like: <dtml-with FullPath> what should the syntax be. Thanks, Dan P.S. since the id in the manage_exportObject argument list is a string, I can handle making that a var instead of hardcoding the value: ItemToBeExport.

1 0

external method problems
by auto44082＠hushmail.com 23 Feb '00

23 Feb '00

This is probably really simple to those of you who have been doing this for a while, but I'm just starting and need some help. I'm creating a zope product consisting of a ZClass which inherrits the DTML Document and the Object Manager. (The Idea is it will be allowed to contain other objects) I've got an external method defined and that part seems to work OK. (I've done the standard hello world test, etc.) Where I'm getting hung up, is I'm trying to upload an external file to this new object, by calling the objects manage_addFile method followed by the manage_upload method. The idea is to create an empty file within my new object, then replace it's contents with the uploaded file, which was specified in a browse field when the object was created. I'm calling the external method that does this from the add constructor of my object. Everything seems to work fine, no errors etc. However, when I try and access the contents of the supposedly uploaded file from within my new object, say in a <dtml-var> tag. I get object not found errors. Unfortunately I'm not experianced enough at this yet for my problem to be immediately obvious to me. If one of you out there feels inclined to explain to me how this shoudl work I would greatly appreciate it. For your reference, here's the python code of my external method such as it is. Thanks a million! def getFile(self, REQUEST): """A simple external method.""" f1=REQUEST.new_file self.manage_addFile('temp',f1) self.temp.manage_upload([REQUEST.new_file,REQUEST]) IMPORTANT NOTICE: If you are not using HushMail, this message could have been read easily by the many people who have access to your open personal email messages. Get your FREE, totally secure email address at http://www.hushmail.com.

1 0