March 1999 - Zope-Dev

Re: Zope-Dev digest, Vol 1 #2 - 8 msgs
by Tres Seaver 05 Mar '99

05 Mar '99

> Message: 2 > To: zope-dev(a)zope.org, amos(a)aracnet.com > Subject: [Zope-dev] bug: ZOPE FAQ product failing on starship.python.net > Reply-To: vanandel(a)ucar.edu > Date: Thu, 04 Mar 1999 08:59:40 -0700 > From: Joe Van Andel <vanandel(a)atd.ucar.edu> > > I'm trying to use the FAQ module to build a FAQ area for Numeric > Python. starship.python.net is running Zope-1.10.2 . > > I've simply created a few categories and sample FAQs, for testing. The > last thing I did was to create a 'faqmaster' user, so I could let NumPy > email list subscribers add/edit FAQ entries. But now, the FAQ module > seems broken (see below for details) > > Any ideas on how to fix this? > > Right now, the URL > http://starship.python.net:9673/crew/vanandel/NumPy/ > > yields "System Unavailable", with a backtrace of: > > Error type: > Error value: isCategory > > traceback (innermost last): > File /home/zope/Zope-1.10.2-src/lib/python/ZPublisher/Publish.py, line 877, in publish_module > File /home/zope/Zope-1.10.2-src/lib/python/ZPublisher/Publish.py, line 590, in publish > (Info: crew/vanandel/NumPy/) > File /home/zope/Zope-1.10.2-src/lib/python/OFS/DTMLMethod.py, line 155, in __call__ > (Object: index_html) > File /home/zope/Zope-1.10.2-src/lib/python/OFS/DTMLMethod.py, line 151, in __call__ > (Object: index_html) > File /home/zope/Zope-1.10.2-src/lib/python/DocumentTemplate/DT_String.py, line 513, in __call__ > (Object: index_html) > File /home/zope/Zope-1.10.2-src/lib/python/TreeDisplay/TreeTag.py, line 154, in render > (Object: a tree tag) > File /home/zope/Zope-1.10.2-src/lib/python/TreeDisplay/TreeTag.py, line 244, in tpRender > (Object: Navigation) > File /home/zope/Zope-1.10.2-src/lib/python/TreeDisplay/TreeTag.py, line 331, in tpRenderTABLE > (Object: Navigation) > AttributeError: (see above) > You are not alone -- I had to back out the UserFolder / security on my FAQ object on starship, too. -- ========================================================= Tres Seaver tseaver(a)palladion.com 713-523-6582 Palladion Software http://www.palladion.com

1 0

Re: [Zope] special characters
by John Eikenberry 04 Mar '99

04 Mar '99

On Thu, 4 Mar 1999, John Eikenberry wrote: > This leads to a followup question/request for the group. > > 'manage_addProperty' calls various converters from ZPublisher.Converters > to format the properties values. Shouldn't html_quote be used when > formatting strings and text? This would be trivial to change. Would this > cause some problem I don't realize? If not, I'd like to add this to the > Collector for the next version. (Switched over to zope-dev to reply to myself.) After a bit more digging, I found some weirdness in Zope/lib/python/OFS/properties.dtml  <input type="text" name=":" size="35" value="">  <input type="text" name=":string" size="35" value=""> 'string' is in the first list, this is probably a bug considering it has its own #elif and this case does the correct formatting. The 'text' type don't have the html_quote format thought, and they probably should to. So, is it's probably better to format this stuff here (on the way to the display) rather than on the way to storage. I'll probably enter this one in the Collector. I'll test it a bit first. --- John Eikenberry [jae(a)kavi.com - http://taos.kavi.com/~jae/] ______________________________________________________________ "A society that will trade a little liberty for a little order will deserve neither and lose both." --B. Franklin

1 0

Programmatically accessing Z SQL Methods
by Mike Pelletier 04 Mar '99

04 Mar '99

I've got a pretty solid understanding of how to get around Zope from the Product API point of view, and there is good documentation on using Z SQL Methods from the DTML point of view. I'm finding myself in the grey overlapping area, and there isn't a lot of documentation yet. I'm finding myself having trouble getting started. Here's a deal: If I get a boost up the learning curve with a few answers, I'll put it in a How-To once I understand it all. I would like the user to select the Database Connection when my Product is being added. When the Product installs itself, I want it to check the database it's been passed for the existance of a particular table. If it does not exist, I want to create said table and do some initial populating. So far my scheme for doing this involves adding a Z SQL Method to the current folder, putting some SQL in it, running it, putting some SQL in it, running it, etc, etc, and then removing it when I'm done. This seems like a stupid way to go about things. I'd much rather just be able to take my connection and submit some SQL programmatically. So, I guess question is simply, "How do I submit an SQL query, starting from a connection_id?" Thanks, Mike. -- --- | Mike Pelletier Work: 519-746-1607 /opeware! | Software Developer Home: 519-725-7710 --- | mike(a)zopeware.com Fax: 519-746-7566 http://www.zopeware.com | Zopeware is not endorsed by Digital Creations

2 1

Re: [Zope-dev] FAQ Submission
by Philip Aylesworth 04 Mar '99

04 Mar '99

>Michel's use of a debug flag is cool. Only, are you aware of Z_DEBUG_MODE I have seen mention of this. How do I use it? Do I just setenv Z_DEBUG_MODE 1? > try: n=string.atoi(n) > except: pass > if n: Globals.DevelopmentMode=1 > I am not up to speed on Python yet. Does this mean that it is expecting Z_DEBUG_MODE to be set to an integer? Does the value mean anything? Phil A ------------------------------------------ Philip Aylesworth zopelist(a)regalint.com Regal International

1 0

RE: [Zope-dev] FAQ Submission
by Michel Pelletier 04 Mar '99

04 Mar '99

> -----Original Message----- > From: Amos Latteier [mailto:amos@aracnet.com] > Sent: Thursday, March 04, 1999 1:28 PM > To: Pavlos Christoforou > Cc: zope-dev(a)zope.org > Subject: Re: [Zope-dev] FAQ Submission > > > At 12:32 PM 3/4/99 -0500, you wrote: > > > > > > >I think Skip provided a better way to deal with this, but I > am not sure if > >it has made it in the official DocumentTemplate release. > > Michel's use of a debug flag is cool. Only, are you aware of > Z_DEBUG_MODE > (aka BOBO_DEBUG_MODE, aka __bobo_debug_mode__)? It's purpose > is exactly > things like this. It gives more informative errors, and > should make all > objects that care operate in debug mode. > > For example, I believe that HTMLFiles should check for this > and reload it's > content if it is set. > > Check out this snippet of code from Main.py > > for n in 'Z', 'BOBO': > if os.environ.has_key('%s_DEBUG_MODE' % n): > n=string.lower(os.environ['%s_DEBUG_MODE' % n]) > if n=='no' or n=='off': continue > try: n=string.atoi(n) > except: pass > if n: Globals.DevelopmentMode=1 > > Now you know how to check for debug mode in your own objects, > check for > 'DevelopmentMode' > > -Amos > I think we're talking about two different methods. In my code... def defaultDocFile(self, id, title, file): f=open('%s/Products/Notmail/%s.dtml') % (SOFTWARE_HOME, file)) file=f.read() f.close() self.manage_addDocument(id, title, file) (which BTW Amos, YOU contributed to NotMail months and months ago before the Great Open Sourcing ;) ...how does the Document object know, after the fact (remember this method is called from __init__) where it's content came from? The path and file pointer are discared after this function returns. Unless the Document instance added by manage_addDocument is telepathic, I can see how it would know where it came from. I can see where in the case where DTML is called like so: amethod = HTMLFile('filename', globals()) The Z_DEBUG_MODE comes in handy, but the manager is never given the option to edit the contents of the Document after the object is created without changing the file on disk, which would change the return values of *all* the returned methods (like 'amethod' above) and effectively change the look of ever instance of the Product in Zope. Different instances of the NotMail Product (the one where my code snips came from) can all edit their own interfaces, because defaultDocFile loads the documents off of disk and puts them into the NotMail Folder. At this point they are unrelated to the files on disk. I think? If this is the case (I think it is) then my original post was a correct method (altough my original post was probably nowhere near clear enough about it). If the Product author wants to return a document loaded at __init__ time into a folder with defaultDocFile she can just: def amethod(blah, bler, REQUEST=None) ... return self.id_of_document(self, REQUEST) With this method, if a Product is a folder it can contain it's own UI, independent of any other instance of the object's UI, and independent of the contents of the DTML in the Products directory on disk. Because this Document object is independent of the contents of the file on disk, the reload_docs method in my original post is used to delete each Document, and reload it from disk, without having to delete/recreate the NotMail object, which gets REALLY old quick when I'm changing my DTML alot. All of this aside, I should not have my own 'debug' attribute but should sniff for Z_DEBUG_MODE instead. I'll try and wrassle up a clearer post for the list. (BTW, both of these methods, the common way and the Product-containing-it's-own-UI way, are detailed extensively in The Zen of Zope). For a hands on example of this method, check out NotMail sources. Confera also does a similar thing (but doesn't offer the ability to reload it's interface) -Michel > > > > _______________________________________________ > Zope-Dev maillist - Zope-Dev(a)zope.org > http://www.zope.org/mailman/listinfo/zope-dev >

1 0

Re: [Zope-dev] FAQ Submission
by Amos Latteier 04 Mar '99

04 Mar '99

At 12:32 PM 3/4/99 -0500, you wrote: >On Thu, 4 Mar 1999, Michel Pelletier wrote: > >> When your debugging your DTML, it's a pain to keep deleting and creating >> new instances of your object in order to load the new dtml files off of >> the disk. This function comes in handy: >> >> def refresh_docs(self, REQUEST): >> """ refresh documents from disk (for debug purposes) """ >> >> for id,title in self.defaultDocs: >> try: >> self._delObject(id) >> except: >> pass >> try: >> self.defaultDocFile(id, title, id) >> except: >> pass >> return self.manage_main(self, REQUEST) > >I think Skip provided a better way to deal with this, but I am not sure if >it has made it in the official DocumentTemplate release. Michel's use of a debug flag is cool. Only, are you aware of Z_DEBUG_MODE (aka BOBO_DEBUG_MODE, aka __bobo_debug_mode__)? It's purpose is exactly things like this. It gives more informative errors, and should make all objects that care operate in debug mode. For example, I believe that HTMLFiles should check for this and reload it's content if it is set. Check out this snippet of code from Main.py for n in 'Z', 'BOBO': if os.environ.has_key('%s_DEBUG_MODE' % n): n=string.lower(os.environ['%s_DEBUG_MODE' % n]) if n=='no' or n=='off': continue try: n=string.atoi(n) except: pass if n: Globals.DevelopmentMode=1 Now you know how to check for debug mode in your own objects, check for 'DevelopmentMode' -Amos

1 0

FAQ Submission
by Michel Pelletier 04 Mar '99

04 Mar '99

How does my Folder Product load default documents? Create a list of tuples containing filenames (without '.dtml') and title pairs: self.defaultDocs = [ ('index', 'NotMail'), ('address', 'Address Book'), ('attach', 'Attach a File'), ('composer', 'Compose a Message'), ('contact', 'Contact Developers'), ('search', 'Search Your Mailboxes'), ('results', 'Your Search Results'), ('folder', 'Mailbox'), ('message', 'Message'), ('help', 'Help'), ('lookup', 'Lookup Users'), ('standard_footer', 'Standard HTML Footer'), ('standard_header', 'Standard HTML Header'), ('noto', 'Message must have at least one recipient.'), ('reminders', 'Your Reminders'), ('save', 'Save Message'), ('logout', 'You have been logged out'), ('GPL', 'The GNU General Public License'), ('sentmail', 'Mail was sent')] # Then iterate over them and create each one for id,title in self.defaultDocs: try: self.defaultDocFile(id, title, id) except: pass # defaultDocFile is a handy little function: def defaultDocFile(self, id, title, file): f=open('%s/Products/NotMail/%s.dtml' % (SOFTWARE_HOME, file)) file=f.read() f.close() self.manage_addDocument(id, title, file) When your debugging your DTML, it's a pain to keep deleting and creating new instances of your object in order to load the new dtml files off of the disk. This function comes in handy: def refresh_docs(self, REQUEST): """ refresh documents from disk (for debug purposes) """ for id,title in self.defaultDocs: try: self._delObject(id) except: pass try: self.defaultDocFile(id, title, id) except: pass return self.manage_main(self, REQUEST) Then, assuming your object has an attribute 'debug' you can define some DTML like so in your manage_main screen:  <p><a href="refresh_docs">Refresh Documents from disk</a></p>

2 1

bug: ZOPE FAQ product failing on starship.python.net
by Joe Van Andel 04 Mar '99

04 Mar '99

I'm trying to use the FAQ module to build a FAQ area for Numeric Python. starship.python.net is running Zope-1.10.2 . I've simply created a few categories and sample FAQs, for testing. The last thing I did was to create a 'faqmaster' user, so I could let NumPy email list subscribers add/edit FAQ entries. But now, the FAQ module seems broken (see below for details) Any ideas on how to fix this? Right now, the URL http://starship.python.net:9673/crew/vanandel/NumPy/ yields "System Unavailable", with a backtrace of: Error type: Error value: isCategory traceback (innermost last): File /home/zope/Zope-1.10.2-src/lib/python/ZPublisher/Publish.py, line 877, in publish_module File /home/zope/Zope-1.10.2-src/lib/python/ZPublisher/Publish.py, line 590, in publish (Info: crew/vanandel/NumPy/) File /home/zope/Zope-1.10.2-src/lib/python/OFS/DTMLMethod.py, line 155, in __call__ (Object: index_html) File /home/zope/Zope-1.10.2-src/lib/python/OFS/DTMLMethod.py, line 151, in __call__ (Object: index_html) File /home/zope/Zope-1.10.2-src/lib/python/DocumentTemplate/DT_String.py, line 513, in __call__ (Object: index_html) File /home/zope/Zope-1.10.2-src/lib/python/TreeDisplay/TreeTag.py, line 154, in render (Object: a tree tag) File /home/zope/Zope-1.10.2-src/lib/python/TreeDisplay/TreeTag.py, line 244, in tpRender (Object: Navigation) File /home/zope/Zope-1.10.2-src/lib/python/TreeDisplay/TreeTag.py, line 331, in tpRenderTABLE (Object: Navigation) AttributeError: (see above) Joe VanAndel Internet: vanandel(a)ucar.edu National Center for http://www.atd.ucar.edu/~vanandel/home.html Atmospheric Research

1 0

etcUserFolder Product
by Michel Pelletier 03 Mar '99

03 Mar '99

Greetings, (This is crossposted because it is a product anouncement, and contains interesting developer pointers) I've have massaged the source code for UserDb and created a new user folder products called etcUserFolder. This products authenticates off of a flat file of usernames:cryptedpasswords. If there is anything trailing the crypted password it is ignored, so any /etc/passwd file will work. It is generaly not recommended, however, to use your /etc/passwd file for security reasons. This is an unsuported product and has been written because it was asked for a few times, and I felt the community could use another good example of writing user folders. It also shows off cookie authentication which Brian perfected with UserDb. Here is the documentation: etcUserFolder requires a directory called 'etcUsers' in which to place your file containing the uid:pwd pairs. This directory may be an INSTANCE_HOME (typicaly your top level Zope dir), SOFTWARE_HOME (typicaly 'lib/python') or in the etcUserFolder directory. Jim wrote a nifty function called getPath that sniffs all of these places for a directory and file of your choosing. This function is included in etcUserFolder and will be included as a standard function of the next release. Other Product authors may find it interesting. Since the flat file is meant to be b/w compatable with /etc/passwd and htpasswd style files, there is no Role associated with the users it authenticates. You can specify a default role which is, by default, 'etcUser'. I have not done extensive testing of this, therefore it is a pre-release. Please send bug-reports and hopefully a patch to me (michel(a)digicool.com) http://www.zope.org/Download/Prereleases/etcUserFolder/etcUserFolder.tar .gz -Michel

1 0

RE: [Zope-dev] zope-dev created - correction
by Ken Manheimer 03 Mar '99

03 Mar '99

Doh. I was hoping to keep it down to one glaring mistake, but instead there are at least four - the URL's i specified were wrong, i should have put www.zope.org instead of www.digicool.com! The correct URLs (tested, this time:-) are: zope http://www.zope.org/mailman/listinfo/zope http://www.zope.org/mailman/roster/zope zope-dev http://www.zope.org/mailman/listinfo/zope-dev http://www.zope.org/mailman/roster/zope-dev Ken again. klm(a)digicool.com

1 0