March 2000 - Zope-Dev

Can't get DateTime from REQUEST. Bizarre or just dumb?
by Loren Stafford 01 Mar '00

01 Mar '00

All attempts to access executeAt result in NameError, even tho it's obviously there. What am I doing wrong? > C:\Zope214\bin\lib\pdb.py(868)set_trace()->None -> Pdb().set_trace() (Pdb) s > C:/Zope214\lib\python\Products\ZScheduler\ZEvent.py(100)manage_edit() -> self.executeAt=executeAt (Pdb) s NameError: 'executeAt' > C:/Zope214\lib\python\Products\ZScheduler\ZEvent.py(100)manage_edit() -> self.executeAt=executeAt (Pdb) self.executeAt DateTime('1969/12/31 16:00:00 US/Pacific') (Pdb) REQUEST.form {'title': 'Z Event #4', 'executeAt': DateTime('2000/02/04'), 'data': 'Content-Ty pe: text/html\012\012<h1>Bang! Bang?</h1>', 'SUBMIT': 'Change'} (Pdb) title 'Z Event #4' (Pdb) data 'Content-Type: text/html\012\012<h1>Bang! Bang?</h1>' (Pdb) executeAt *** NameError: executeAt (Pdb) DateTime <class DateTime.DateTime.DateTime at 8dc1a0> (Pdb) executeAt.timeTime *** NameError: executeAt (Pdb) DateTime('2000/02/04') DateTime('2000/02/04') (Pdb) This is from a simple manage_edit method. It's not that different from the manage_add method, which handles the DateTime just fine. I'm sure it's just a simple oversight on my part; but I can't see what the problem is. Can you? -- Thanks -- Loren

1 0

Rollback or Commit in a DTML Method ?
by Juan Javier Carrera Obrero 01 Mar '00

01 Mar '00

Hello, Anybody to know to how to do a "Rollback" or a "Commit" in a DTML Method ? Thanks !! ------------------------------------ JUAN JAVIER CARRERA OBRERO e-mail: jcarrera(a)uco.es

2 1

Re: [Zope-dev] Manipulating Meta-Type Global Add list on per-instance basis
by Josh Zeidner 01 Mar '00

01 Mar '00

Hmm... possibly I did not explain my needs : What I need to do is manipulate the attribute of a "folderish" object ( ie. an object that can contain other objects ) that determines what objects are allowed to be contained by my object. I need to do this at instantiation time , *NOT* definition time. I seemed to have accomplished this by manipulating the "meta_types" attribute... but is this a valid way to attain this behavior? thanks again- Josh > >Josh Zeidner <jmz_phylogenic(a)hotmail.com> asks: > > > I am currently trying to define a Z-Class that inherits from Object > > Manager that has the special behavior of being able to change its >"allowable > > sub-objects" on a per-instance basis. > > > > ***************** > > > > ex. > > > > I instantiate the class at a particular location I want this object to > > only be able to contain objects of type "AppleObject" and >"OrangeObject". > > > > I instantiate the class at another location and I want this object to >only > > contain objects of type "LemonObject" and "LimeObject". > > > > note that the difference here is that both of the containers are of >the > > same type. > > > > ************* > > > > is it possible to have this flexibility after the ZClass has been >defined? > >If you are defining the interface (rather than accepting the default >"Contents" >view), then you can do something like:: > > <select name="toAdd"> > <dtml-in "filtered_meta_types( AUTHENTICATED_USER )" mapping> > <dtml-if "name in allowed_types"> > <option value="&dtml-name;"> <dtml-var name> > </dtml-if> > </dtml-in> > </select> > >where 'allowed_types' is a tokens/lines property of the instance. > >Making this happen in the stock management interface is trickier -- you >need to >overried either all_meta_types(), but finding the list of possible types, >so >that the list you return contains the dictionaries required by >filtered_meta_types(). I can't see easily off hand how to do this from >within a >Python Method -- I think I would have to drop down to an External Method, >or >create a new Python base class to implement this. > >Tres. >-- >========================================================= >Tres Seaver tseaver(a)palladion.com 713-523-6582 >Palladion Software http://www.palladion.com ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

2 1