- Zope-Dev - Zope lists

Membership and ZPatterns
by Bill Anderson 30 Jul '00

30 Jul '00

OK, so I have been playing with ZPatterns quite a bit lately. And some old (current) issues with PTK comes back to mind. Among them are: o Not all portals will want a user to have a folder o username is not changeable With ZPatterns, I believe we can solve the first one. First things first, the first one. :) Proposal: On the Membership Add form, there be an option for user folders. If set, this option would install a trigger. This trigger would then, upon creation of a new user, fire off a MakeMemberFolder (that name is just a placeholder) method that would handle the creation of their folder. Of course, this is secondary in priority to getting some user management tools available, IMO. Now, something to remember, is that the lack of a user folder does not neccesarily elminate the capability of a user to contribute to the community site information base; though that is desireable for some sites. Through use of ZTopics, ZPatterns-based Content, and ZCatalog, one can build a site that stores types of content in it's own place, and provide a variable interface, for both browsing, and user management. I am actually working on a site built like this, so I know it is do-able. :) Thoughts, Opinions? Bill -- Do not meddle in the affairs of sysadmins, for they are easy to annoy, and have the root password.

1 0

Re: [Zope-dev] ZPatterns: bug in DataSkins.py
by Steve Alexander 30 Jul '00

30 Jul '00

"Phillip J. Eby" wrote: > > At 08:07 PM 7/30/00 +0100, Steve Alexander wrote: > >Steve Alexander wrote: > >> > >> I'm using ZPatterns 0.4.1snap1. > >> > >> DataSkins.py line 377 > >> method _v_currentSheets(self,_v_dm_=_v_dm_) > >> > >> l.extend(list(sp._PropertySheetsFor(client))) > >> > >> However, the variable "client" isn't declared elsewhere. > > > >..and when I replace it with "self", I get this error when I try to > >iterate through a dataskin's propertysheets: > > > > Would you try something for me? Stick a routine in that class, call it > getCurrentSheets(), with exactly the same code as the _v_currentSheets > method, then call it from your code in place of iterating through > propertysheets? I have a feeling it'll provide a clearer error message. > (That's the only problem with ComputedAttributes - errors that break them > manifest as AttributeErrors, hiding the true error.) Thanks. ok. I think I've found the problem... I removed my own custom SheetProvider from the Specialist, and it works as expected. Here's the traceback with the new method, and my broken sheetprovider still in place: AttributeError: _PropertySheetsFor Traceback (innermost last): File /usr/local/zope/SiteBox/lib/python/ZPublisher/Publish.py, line 222, in publish_module File /usr/local/zope/SiteBox/lib/python/ZPublisher/Publish.py, line 187, in publish File /usr/local/zope/SiteBox/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: address-964970042) File /usr/local/zope/SiteBox/lib/python/ZPublisher/Publish.py, line 171, in publish File /usr/local/zope/SiteBox/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: content_html) File /usr/local/zope/SiteBox/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: content_html) File /usr/local/zope/SiteBox/lib/python/OFS/DTMLMethod.py, line 167, in __call__ (Object: content_html) File /usr/local/zope/SiteBox/lib/python/DocumentTemplate/DT_String.py, line 502, in __call__ (Object: content_html) File /usr/local/zope/SiteBox/lib/python/DocumentTemplate/DT_In.py, line 633, in renderwob (Object: getCurrentSheets()) File /usr/local/zope/SiteBox/lib/python/DocumentTemplate/DT_Util.py, line 337, in eval (Object: getCurrentSheets()) (Info: getCurrentSheets) File <string>, line 0, in ? File /usr/local/zope/SiteBox/lib/python/Products/ZPatterns/DataSkins.py, line 376, in getCurrentSheets (Object: address-964970042) File /usr/local/zope/SiteBox/lib/python/Products/ZPatterns/Providers.py, line 268, in _PropertySheetsFor (Object: PlugInBase) AttributeError: (see above) -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net

1 0

ZPatterns: bug in DataSkins.py
by Steve Alexander 30 Jul '00

30 Jul '00

I'm using ZPatterns 0.4.1snap1. DataSkins.py line 377 method _v_currentSheets(self,_v_dm_=_v_dm_) l.extend(list(sp._PropertySheetsFor(client))) However, the variable "client" isn't declared elsewhere. -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net

2 2

Additional Quoting; Exposing Auxiliary Tag Functions via "_" (was: [Zope-dev] dtml-var tag suggestion) (was: [Zope-dev] dtml-var tag suggestion)
by Dieter Maurer 30 Jul '00

30 Jul '00

Casey Duncan writes: > I have been using dtml to create dynamic JavaScripts for some forms I am > creating. In doing this I came upon the standard problem of inserting > strings containing double quotes into a JavaScript such as where title = > '"Quoted String"': > > form.select.options[0].text = "<dtml-var title>"; > > And you wind up with this rendered: > > form.select.options[0].text = ""Quoted String""; > > I know there is the html_quote and sql_quote options to alleviate this > problem elsewhere. From what I can figure there is no other quote fixing > magic option for the above in the current dtml-var implementation. > > Perhaps an options could be added to dtml-var in the future to handle this; > maybe something like "slash_quote". So that you get this rendered: The existing "quote features" name the context for which quoting is needed. The context determines what needs to be quoted and how quoting has to be done. Your proposal does not state the context but only the how. Otherwise, I would think such an extension would be good. Thus, I propose: 1. new quoting directive "string_quote" quoting Python strings i.e. ", ' and \ are quoted. This would work for Javascript (and other languages with C-like quotation and string literals), too. 2. all auxiliary functions for DTML tags, especially quoting, should be available via the namespace. To avaid namespace pollution, they may go into a separate module, say 'aux'. E.g. I would like to use quoting, formatting etc. inside DTML embedded Python expressions in a form like that: <dtml-var "... _.aux.fmt(x,'%m/%d/%Y')..."> and <dtml-var ".... _.aux.sql_quote(x)..."> Dieter

1 0

Renaming ZClass instances in 2.2.0
by Steve Alexander 29 Jul '00

29 Jul '00

In Zope 2.2.0, I can't rename ZClass instances. When you rename something, lib/python/OFS/CopySupport.py's _verifyObjectPaste() method gets called with the object you're renaming as an argument. The method checks that the current user is authorized to create objects of that kind, and that the current user is authorized to create that object in the current context. The problem seems to be that, in the case of renmaing a ZClass instance, when the ZopeSecurityPolicy tries to get a __roles__ attribute for the instance you're renaming, it can't find one. I'm way out of my depth here, but I can get it to work again by adding to the function PersistentClassDict() in lib/python/ZClasses/ZClass.py (line 195 or so): dict['__roles__']=('Manager',) so that it looks like this: def PersistentClassDict(doc=None, meta_type=None): # Build new class dict dict={} dict.update(Template.__dict__) if meta_type is not None: dict['meta_type']=dict['__doc__']=meta_type if doc is not None: dict['__doc__']=doc dict['__roles__']=('Manager',) return dict This only works for ZClasses defined after the change, though. I have absolutely no idea what the side-effects of this change are, and I'm not even entirely sure what it does :-) It seems to fix the problems of renaming DataSkin-derived ZClasses too. I've looked though the recent CVS checkins, and I can't see a fix for this yet. I've also looked through the Collector, and I can't see this problem reported. -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net

1 0

AcquisitionMadness
by Chris Withers 29 Jul '00

29 Jul '00

Evan, I wonder if the changes Shane suggested in MethodGeddon would make Simplified Acquistion suffice for what Steve was asking about? Also can you explain how from the example: Two path acquisition: A contains B1 and C1, B1 contains B2, C1 contains C2 How (Natural Acquisition): A.B1.B2.C1 == (((C1 o A) o (B1 o A)) o ((B2 o B1) o (B1 o A))) equates to: "Roughly speaking, search the objects in the reverse of the order they were mentioned in, along the shortest physical path between each object." and how it differs in effect from: A.B1.B2.C1 == (((C1 o A) o (B1 o A)) o (B2 o (B1 o A))) (which is what I think simplified Acquisition would return...) cheers, Chris PS: This might just be explaining how the (x o y) notation actually tells you where the object's attribute comes from :S (in the above example, how, in each case, the notation explains where C1 comes from...) PPS: What's happening with the Zope-Dev Wiki? Is it being fazed out?

1 0

Problem by counting the number of result of database query
by Bruno Nana 29 Jul '00

29 Jul '00

> Hi, > > I have one problem with a Zmethod. > > Here is the method: > > select *,summe=sum(count(*)) > from neuigkeiten > where > ( > username like '%%' or > autorloginname like '%%' or > headline like '%%' or > textfeld like '%%') > order by headline > > That is i want to select some data from database and save the number of data > who are found in summe.(Number found:<dtml-var summe> is ok) > There is no error at this level, but there is a problem when i list the > result in the dtml document. There are more data as i need. > > Please would you help me to resolv this problem!! > > Thank > > Bruno >

1 0

bug in ZSQL methods caching; new explicit 'nocache' feature for SQL Methods
by Brian Takashi Hooper 29 Jul '00

29 Jul '00

Hi Zopistas, I've been playing a bit with adding a feature to Z SQL Methods to allow an explicit 'nocache' parameter to be sent to an SQL Method, so that a particular query can be run pre-clearing the cache for that particular query, while leaving the rest of the cache intact. So you for example serve content from your SQL database with something like <dtml-var "selectContent(content_id=1)"> in your display templates, and then say if you have an admin screen where you edit that content in the DB, you can do <dtml-call "selectContent(content_id=1, nocache=1)"> after editing, and that will clear the cache entry only for content_id=1. I think there might be a lot of reasons this could be good. Anyways, when I was looking over Shared.DC.ZRDB.DA.DA._cached_result() to find out how the caching worked, I noticed something that seems a little funny; it looks like the cache clearing is done in _cached_result by sorting through all the time values in tcache, which is an _integer-keyed_ IOBTree which stores the times of each of the queries. However, what happens when the same query is made several times in one second? Only one time-query pair is stored in the tcache for each unique integer time, so if in the same second I make 20 queries using the same SQL method, then later when I try to clean the cache, I will only be able to delete one of these values... I added a little debugging output to _cached_result and was able to, by making a lot of queries to the method in the same page, make the size of the cache go above the supposed maximum size max_cache. Admittedly this kind of usage is rare, but it probably should be fixed... it would probably be improved by making tcache a regular Python dict storing floats as the keys. Finally, here's my code to add 'nocache' to SQLMethods; it would definitely be nicer if it was integrated into DA.py instead, since that would save having to generate the query twice, for example... in the meantime, though here it is (ZSQLMethods/SQL.py, SQL.__call__). def __call__(self, *args, **kw): """ Add an option 'nocache' to avoid using the query cache for a particular query. This way, SQL queries can be cached in general but an application can decide if it wants to explicitly retrieve a new value... """ scall = SQL.inheritedAttribute('__call__') sargs = (self,)+args if kw.has_key('nocache') and kw['nocache'] == 1: # we only care about clearing the cache if there _is_ a cache if hasattr(self,'_v_cache'): cache=self._v_cache cache, tcache = cache srckw = kw.copy() srckw['src__'] = 1 query = (apply(scall, sargs, srckw), self.max_rows_) # clear the cache and tcache, if necessary if cache.has_key(query): t = cache[query][0] t = int(t) del cache[query] if tcache.has_key(t) and tcache[t] == query: del tcache[t] return apply(scall, sargs, kw) Do other people like this idea? --Brian Hooper

1 0

Membership 0.6.1 available
by Bill Anderson 29 Jul '00

29 Jul '00

OK, I have an updated Membership product avalable at http://www.zope.org/Members/Bill/Products/Membership Basically, it fixes the keyword parameter problem, and I've started adding the hooks to eventuall plant a user management interface onto. I just need one crucial piece of the puzzle ... I think. ;) Anyway, same warnings on this as with the version Kevin had. Use in production at your own risk (yes, I take the risk ;) Bill -- Do not meddle in the affairs of sysadmins, for they are easy to annoy, and have the root password.

1 0

Client.py prevents ZScheduler with SSL? (was: Zope.org feedback)
by Loren Stafford 29 Jul '00

29 Jul '00

Moving this to zope-dev and changing title... From: "Jim Sanford" <jsanford(a)atinucleus.com> > We have no http access to our site. > > It is a corporate Client Relationship Management, Job Tracking and Order Processing, Production and Tracking system that is accessed > from all over the world. > > I will send this to the list to see if any one else can provide help. > > > From: Loren Stafford <lstaffor(a)dynalogic.com> > > From: "Jim Sanford" <jsanford(a)atinucleus.com> > > URL: http://www.zope.org/Members/lstaffor > > ZScheduler uses Client.py. > > > > Would it be correct to say that if my entire site is only accessible via > SSL (https) that ZScheduler will not work? > > I hadn't thought about this before, so you probably know more about it than > I do. But given that the python lib that Client.py uses for http > (httplib.py) doesn't support https, then you're right. > > Solutions? > > 1. Permit http traffic to your site if it comes fromt the same IP and is for > URLs that end in "/trigger". I suppose that IP spoofing makes this something > of a security hole. How bad? > > 2. Enhance either Client.py or httplib.py to support at least enough https > to get the job done. I know nothing about this. Is it reasonably doable? Is > there a Zopista willing and able to do it? > > 3. ....? > > -- Loren

1 0