November 1999 - Zope-Dev

Re: Dealing with form data in External Methods
by Martijn Pieters 08 Nov '99

08 Nov '99

I am moving this to Zope-Dev. At 02:50 08/11/99 , David S. Harrison wrote: >After a little experimentation, I found that the values submitted >via a form are placed into the receiving DTML document's name space. >That is very nice. Now I am wondering whether these values are >also available to external methods I call as part of the evaluation >of the receiving DTML page. Let me be more specific: suppose >I have an external method: > >def ComputeColumns(self): > # Find the value of 'testcase' in the enclosing name space? > return computeList(testcase) > >The DTML page that calls this external method has a form >variable named 'testcase'. Is there some way I can use >the self object to evaluate names in the enclosing name space? >Or should I try to call the method explicitly with arguments? >Right now, the code in the DTML page is kind of nice: > ><dtml-in ComputeColumns> > <LI><dtml-var sequence-item> ></dtml-in> > >I suppose I could change it to be a call. But I am not >clear on what should be used for the name of "ComputeColumns" >or how it should be called. My first guess would be: > ><dtml-in "self.ComputeColumns(testcase)"> > >But I haven't tried it yet. I am hoping there is some >method I can call using 'self' to evaluate name space >variables in an external method. Brian Lloyd's External Method HowTo provides all the answers: http://www.zope.org/Documentation/How-To/ExternalMethods -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------

1 0

Patch to provide "local" and "set" tags in DTML
by Phillip J. Eby 08 Nov '99

08 Nov '99

Below is a patch for the current version of DocumentTemplates which adds "local" and "set" tags to DTML. Both use syntax identical to that of the "let" tag, with two key differences. First, where "let" defines variables that remain constant within the block, the "local" tag defines local variables which may be changed within the block's scope by using the "set" tag. The second difference is that the "set" tag is an empty tag like "var", not a block tag. Thus, it can be used repetitively (e.g. within "in" loops) or to set different values of a variable on opposing conditions of an "if" tag. There are some limitations, for security reasons. Only variables named in a "local" block may be set by "set", and only those in the innermost such block. This helps to prevent an untrusted, called DTML method from polluting its parent's namespace (since its caller can wrap the call with a "local" block that defines no variables). Naturally, "set" cannot be used outside a "local" block, although this is a runtime error rather than a compile-time error. The code should be considered alpha quality - I have used it for a few things over the past few months, but it has not been put to anything heavy yet. It is available for use under the same terms as the rest of DT_Let, which is to say, under the ZPL. Enjoy. Index: DT_Let.py =================================================================== RCS file: /cvs-repository/Zope2/lib/python/DocumentTemplate/DT_Let.py,v retrieving revision 1.5 diff -r1.5 DT_Let.py 122c122,127 < tname, args, section = blocks[0] --- > if hasattr(self,'blockContinuations'): > tname, args, section = (blocks[0]+(None,))[:3] > self.section = section.blocks > else: > tname, args = self.name, blocks > 124,125c129 < self.section = section.blocks < self.args = args = parse_let_params(args) --- > self.args = args = parse_let_params(args,tag=tname) 177a182,232 > > > > > localdictname = '__$local.dict__' > > class Local(Let): > > name = 'local' > > def render(self, md): > > d={}; md._push(d); > > try: > d[localdictname]=d > for name,expr in self.args: > if type(expr) is type(''): d[name]=md[expr] > else: d[name]=expr(md) > return render_blocks(self.section, md) > > finally: > if d.has_key(localdictname): del d[localdictname] > md._pop(1) > > __call__ = render > > > class Set: > name = 'set' > > __init__ = Let.__init__.im_func > > def render(self, md): > > try: > d = md[localdictname] > > except KeyError: > raise 'SetWithoutLocal',"'set' used outside of 'local' block" > > for name,expr in self.args: > > if not d.has_key(name): > raise 'SetUndefined',"variable '%s' is not defined within current 'local' block" > > if type(expr) is type(''): > d[name]=md[expr] > else: d[name]=expr(md) > > __call__ = render Index: DT_String.py =================================================================== RCS file: /cvs-repository/Zope2/lib/python/DocumentTemplate/DT_String.py,v retrieving revision 1.31 diff -r1.31 DT_String.py 141a142,143 > 'local': ('local', 'DT_Let', 'Local'), > 'set': ('set', 'DT_Let', 'Set'), _____ _/__) ___/

1 0

Need help with Products
by Ross Boylan 07 Nov '99

07 Nov '99

I am trying to create a User subclass which will hold additional information about a user. Could someone help me get oriented? I've been using 3 primary sources of information: the existing poll product (as an example), Amos Latteier's recently released "Extending Zope in Python" slides, and Zen's "How-To: The (old) Product AP Tutorial." The latter notes it is out of date. I notice, for example, that the recent info has no reference to methods = ... to get the product creation methods out to the folders. Users have the additional complexity, I think, that there are two items to be managed: the folder which holds the users (the thing which appears as acl_list in the GUI?) and the users themselves. My only interest in a new folder is to assure that the right kind of user object gets created. My intention is that users will create their own user objects off a simple screen asking for the basic info. One specific problem has been that I kept getting a broken product because UserFolder was an unrecognized symbol. The tracebacks displayed on the product information seemed to show the error being thrown at class OrgUserFolder(UserFolder): in OrgUser.py, which in turn was being called from __init__.py's import statement. Yet my various attempts to trap the error failed (in fact, at least some times the code seemed to run OK when it was in the debugger). Mysteriously, when I took the context.RegisterClass out of the __init__ file, the product reported as OK. Note those statements occur after the apparent point the error was thrown. While tracing I also noticed that class definitions seemed to invoke an __init__ method in the App hierarchy (I don't recall the specifics) at the point they were scanned. Can anyone tell me how such a hook gets set up in general, and what it is doing in this case? Another specific question is whether spaces are legal for meta type names. I'm running on NT, and had Python 1.5.2 on my system before I installed Zope. Here's the current code. I've fiddled with lots of variants. ------------------------__init__.py----------------------------------------- ------------- __doc__='''Sample PSA Organizational User Adopted from Poll The job of this module is to provide any run-time initialization needed and to define meta data. ''' __version__='$Revision: 0.1 $'[11:-2] from ImageFile import ImageFile import OrgUser # meta-data: # Names of objects added by this product: meta_types=( {'name': 'PSA User' , # The name of the object type 'action': 'manage_addUser', # The method to add one. }, ) # Attributes (usually "methods") to be added to folders to support # creating objects: methods= { 'manage_addUserForm' : OrgUser.addUserForm, 'manage_addUser': OrgUser.addUser #I need to define this method } # the following gave me an error on UserFolder being unrecognized #def initialize(context): # context.registerClass(OrgUser) ----------------------OrgUser.py-------------------------------------------- --- from AccessControl.User import * addUserForm = HTMLFile('addUser', globals()) class OrgUser(User): """Add additional information on the user""" meta_type ='PSA User' id = 'Organizational_User' title = 'Organizational User' def __init__(self,name,password,roles,domains): User.__init__(self, name, password, roles, domains) self.email = "Your email here" class OrgUserFolder(UserFolder): ### this seems to be where I get the error that UserFolder is unrecognized """Base class for UserFolder-like objects""" meta_type='PSA User Folder' id ='PSA_users' title ='Organizational User Folder' def _doAddUser(self, name, password, roles, domains): """Create a new user""" self.data[name]=OrgUser(name,password,roles,domains) Globals.default__class_init__(OrgUserFolder) def manage_addUserFolder(self,dtself=None,REQUEST=None,**ignored): """ """ f=OrgUserFolder() self=self.this() try: self._setObject('acl_users', f) except: return MessageDialog( title ='Item Exists', message='This object already contains a User Folder', action ='%s/manage_main' % REQUEST['URL1']) self.__allow_groups__=f if REQUEST: return self.manage_main(self,REQUEST,update_menu=1)

2 1

Re: [Zope-dev] RE: [Zope] xmlrpc calls require string results?
by Jeff Rush 07 Nov '99

07 Nov '99

On Fri, 5 Nov 1999 15:18:27 -0500, Dan Pierson wrote: >Here are the method definitions, all in SquishSite in Squishdot.py: > > def has_subjects(self): > ''' returns true if site has subject topics defined''' > return len(self.subjects) > > def subject_count(self): > ''' gives count of subject topics defined''' > return self.has_subjects() > > def subjects_list(self): > ''' lists all subjects ''' > subjects = self.subjects.keys() > subjects.sort() > return subjects > > def item_count(self): > return len(self.data) > >Maybe this is just a Squishdot problem, but I can't see any significant >different between subject_count and item_count above, can you? Uh, yes I can, a very big one. The item_count() method is missing a function-comment string, which means the ZPublisher module won't allow it to be externally called. That sure looks like your problem. -Jeff Rush

2 1

Looking up objects, calling objects
by Itamar Shtull-Trauring 07 Nov '99

07 Nov '99

In my effort to create a simple python cache Product, I need to: A. Pass the name of a DTML method/document or PythonMethod to the ZCache, and then turn this into an object I can call from python (e.g. turn the string "QuickStart.index_html" into a object I can call, while still preserving security.) B. Call the above object from python, passing it the appropiate environment so it can run (_, REQUEST, etc.), that is execute a DTML method in the ZODB, for example, from inside a python Product. I'm also wondering about _v_ attributes - when are they flushed? Is it possible for them to persist in memory for a while at least, so I can use one to store the cached method? -- Itamar - itamars(a)ibm.net ---------------------------o----------------------------------------------o Perl/Gimp Greeting Cards | Trust? Ha! The US dollar is backed by ICBMs! | http://www.sealingwax.com | --Anonymous Coward, Slashdot |

1 0

question:how can i modify a method of a product
by sdf 07 Nov '99

07 Nov '99

I just want to make a product with a main document such as HTML file and related files such as image,I made a product basing object manager,and so i can upload related files,but i don't know how I can edit the index_html method of the product when using the product. it seems problem with the permission thanks

1 0

Re: [Zope-dev] ANNOUNCE: ZWiki 0.1 released
by Simon Michael 06 Nov '99

06 Nov '99

Simon Michael <simon(a)joyful.com> writes: > Perhaps after an edit I can > > try: > render new page > except: > revert to old content Ok, now after an edit I just call apply(DTMLDocument.DTMLDocument.__call__, (self, None, REQUEST, None)) and if there's a DTML problem zope rolls back the transaction & gives an appropriate error. Right on! I'll update the product on zope.org soon.

1 0

RE: [Zope] xmlrpc calls require string results?
by Dan Pierson 06 Nov '99

06 Nov '99

OK, now I'm really confused. You're both right of course, the general case works, but see the following: [dan@silver alist]$ python Python 1.5.2 (#4, Sep 17 1999, 15:44:43) [GCC egcs-2.91.66 19990314/Linux (egcs- on linux2 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam >>> import xmlrpclib >>> x = xmlrpclib.Server('http://silver.control.com/zope/') >>> x <Server proxy for silver.control.com/zope/> >>> x.control_com.subject_count() 14 >>> x.control_com.subjects_list() ['Applications', 'Business', 'Communications', 'Engineering', 'HMI', 'Information', 'Languages', 'Motion Control', 'News', 'PCs in Automation', 'PLCs', 'Process Control', 'Sensors', 'Software in Automation'] >>> x.control_com.item_count() Traceback (innermost last): File "<stdin>", line 1, in ? File "./xmlrpclib.py", line 547, in __call__ return self.__send(self.__name, args) File "./xmlrpclib.py", line 630, in __request request File "./xmlrpclib.py", line 582, in request headers xmlrpclib.ProtocolError: <ProtocolError for silver.control.com/zope/: 404 Not Found> >>> Here are the method definitions, all in SquishSite in Squishdot.py: def has_subjects(self): ''' returns true if site has subject topics defined''' return len(self.subjects) def subject_count(self): ''' gives count of subject topics defined''' return self.has_subjects() def subjects_list(self): ''' lists all subjects ''' subjects = self.subjects.keys() subjects.sort() return subjects def item_count(self): return len(self.data) Maybe this is just a Squishdot problem, but I can't see any significant different between subject_count and item_count above, can you? Dan Pierson, Control Technology Corporation

2 1

Re: [Zope-dev] ANNOUNCE: ZWiki 0.1 released
by Simon Michael 06 Nov '99

06 Nov '99

David Kankiewicz <kankie(a)thegrid.net> writes: > just an idea but wouldn't a text property field work? (no DTML > evaluation for text..) Oh.. are you saying, eg, make the edit box the whole page ? Hmm.. low-tech.. but effective! :) I'd like to offer this as a UI option.

1 0

Re: [Zope-dev] ANNOUNCE: ZWiki 0.1 released
by Simon Michael 06 Nov '99

06 Nov '99

Hi David, I saw the problem - thanks for bringing it to light. Namely: it's easy to enter some bad dtml which then prevents the page from rendering. It has to be fixed through the management interface. Hmm what can we do about this. I had hoped to allow the use of DTML. Perhaps after an edit I can try: render new page except: revert to old content You also revealed a pagenames-with-spaces problem, fixed. The above issue aside, does anonymous DTML entry open up big security holes, I wonder ? I don't *think* so.. I think DTML's whole rationale is that it won't harm the server no matter what you do with it. Regards, -Simon

1 0