January 2001 - Zope-Dev

ANN: CoreSessionTracking Release 0.4
by Chris McDonough 03 Jan '01

03 Jan '01

Hello, A new development release of the "Core Session Tracking" product (0.4) is available at http://www.zope.org/Members/mcdonc/Products/CoreSessionTracking This release makes substantial interface and feature changes including using an internal mounted storage to provide an "internal" session data container to each session data manager, autoexpiring session data objects, as well as vastly improved documentation. Please check it out! Thanks, Chris

1 0

uncataloging objects
by Robert Prosenc 02 Jan '01

02 Jan '01

hi there. i have certain problems with the catalog class. i have something over 9000 objects (all of the same type) cataloged, and it does not only take REAL long to reindex them (but hey, i could live with that), sometimes it also makes the python-process sort of 'hang up' - it merly crushes the whole zope process...... the even bigger problem is that it makes trouble when uncataloging objects....that seems to fail completely: here's some code from the class-definition, where i try to uncatalog the object: def killMe(self): "deletes the record. in fact the record has to be uncataloged first." try: self.Catalog.uncatalog_object('/'+self.absolute_url(1)) except: return "couldn't uncatalog the record." try: self.records.manage_delObjects(ids=self.getId()) # 'records' is a folder, in which the objects are stored except: return "couldn't delete the record." return Globals.MessageDialog( titel='Record deleted', message='Record deleted successfully.', ) so i let my objects kill themselves;) what really confuses me is the fact that while performing that function, no exeption is raised. the uncataloging-call is inside a try/except, but it seems to be performed regulary. but: it isn't! the object, while already deleted, remains still cataloged, which leads to some unpleasant error-pages (key-error) when contained inside the result-set of a search. i have a zope 2.2.2 under linux installed, with hotfixes 2000-10-02, 2000-10-11, 2000-12-08, 2000-12-15a and 2000-12-18, zcatalog 2.2.0 and some selfwritten stuff.... does anybody have an idea what goes wrong here? regards, rob. ------------------------------------------------------------ Robert Prosenc web: http://www.matrixware.at/ mail: r.prosenc(a)matrixware.at Matrixware phone: +43( 1) 713 43 06 - 2 postal: Geusaugasse 39 (Ecke Kundmanngasse) A-1030 Vienna, AUSTRIA ------------------------------------------------------------ while !asleep() sheep++ ------------------------------------------------------------

1 0

Re: [Zope-dev] What's 'section' in blocks[0] in block dtml tag?
by Brett Carter 02 Jan '01

02 Jan '01

Lee, I've been diddling around with the same stuff. It took me a lot of introspection with printing of errors via MrCreosote/Spew. To answer your question, 'section' is an object which contains an attribute 'blocks'. If you want to render the dtml in there, you can run the 'render_blocks' method in '<zope-instance>/lib/Python/pDocumentTemplate.py' You pass it the section.blocks object and a mapping dictionary which is the current namespace stack that gets passed in as the only argument to the 'render' method in you tag definition. If you just want the raw text, check you the render_blocks method, so you can see how they take apart the 'section.blocks' object. As to the object hiarchy of everything, your guess is as good as mine as to why there's a list of tuples of blocks wrapped in a section object, wrapped in another blocks object, I have know idea. Perhaps the designer of the document templates could answer... -Brett >>>>> "LEE" == LEE Kwan Soo <kslee(a)plaza1.snu.ac.kr> writes: LEE> Hi. I'm playing/struggling to make a custom block dtml tag. LEE> Let me call it, dtml-quote tag. LEE> dtml-quote tag is similar to dtml-comment tag except it will emit LEE> html_quoted, not rendered version of what lies LEE> between <dtml-quote> ... </dtml-quote>. LEE> (I feel it will be usefull when I show & write some dtml examples on my LEE> korean zope site). LEE> After seeing around some python sources, LEE> I finally got that tname is the name of the tag, args is args, and section LEE> is something, in the following code. LEE> def __init__(self, blocks): LEE> tname, args, section = blocks[0] LEE> and section seems to have 6 attributes/methods: LEE> '__name__', '_v_blocks', '_v_cooked', '_vars', 'blocks', 'globals', 'raw' LEE> But that mistic raw is null string, '' and blocks is no help for me. LEE> How can I retrieve the raw source string enclosed in a block tag pair? LEE> LEE Kwan Soo. LEE> ps. My English is evem more cryptic this morning. Sorry I've sat up alnight play LEE> Kingdom Under Fire. LEE> _______________________________________________ LEE> Zope-Dev maillist - Zope-Dev(a)zope.org LEE> http://lists.zope.org/mailman/listinfo/zope-dev LEE> ** No cross posts or HTML encoding! ** LEE> (Related lists - LEE> http://lists.zope.org/mailman/listinfo/zope-announce LEE> http://lists.zope.org/mailman/listinfo/zope )

1 0

"dynamic permissions" in zope
by Heinz-Josef Claes 02 Jan '01

02 Jan '01

Hi, I'm very new to zope and have to eximine, if it's usable for our requirements. The question I have, is very simple or perhaps very difficult, I don't know. Our requrements are a permissioning system which depends on a matrix: There are two independend qualities which describe, if a user is allowed to see a document. This can be displayed in a matrix. Only if *both* qualities match, the user is allowed to see it. As far as I understand zope, it is not possible to map this directly (as by all other systems I know). So my question: Is it possible to connect a permission (or role) in zope with a method (instead of a static flag which was set)? If it is possible, it should be possible to call a special algorithm with this request, which can implement whatever is needed. So, it would be (easy) possible to *integrate* this functionality. (I called this permissions "dynamic", because the are evaluated when requestet.) Or does anybody has another (better) idea? Any help is very apreciated, Heinz-Josef Claes hjclaes(a)web.de

2 2

Re: [Zope-dev] ZPatterns example update....
by Itai Tavor 02 Jan '01

02 Jan '01

Steve Spicklemire wrote: >Hi Folks, > > The Dumb ZPatterns example is updated. Now there is some more >realistic object referencing going on, borrowing of code snippets >between Specialists and suchlike. There is also more in the way of >reasonable documentation, though everything is in flux, and it still >doesn't resemble a truly completed product. I just feel the need to >get things finished enough that I can stop thinking about them for a >while. ;-) In particular there the ToDos now hold references to Doer >and Deliverable, and no 'lists' are maintained. One thing I need to do >is to have these references automatically 'fixed' when a 'referred to' >entity is removed or modified in such a way that the link should be >broken.... that's for the next version. If I'm not careful.. it won't >be a 'simple' example anymore. There's got to be a line here somewhere >(in the sand?). Nice work, Steve. Removing id lists looks good. I started building objects using getXForY(y_id), but the last one I made used an id list following the Dumb Example. I've just changed it to use getXForY, and it's much cleaner, plus it makes adding X from Y/editInstanceForm easier. I like the idea of naming all UI methods with '_html' - now, if you find yourself referencing a method which doesn't end in '_html' in your html code, you know you need to add an interface method. I just need to decide if I like it enough to change all my existing code... Some thoughts about the broken links handling problem: If an object depends on the existence of another (for example, if you wanted a ToDo to be tightly linked to a Deliverable) then it should be deleted when the Deliverable is deleted, right? You'd have WHEN OBJECT DELETED CALL ToDos.deleteInstances(myToDoIDs) in the Deliverable SkinScript, and you would never have ToDos floating around without a Deliverable. As for the Deliverable changing and invalidating the link, I think it would be solved if you used immutable ids for all objects, and stored the Deliverable title in a separate property. In case of weaker links, such as between ToDo and Doer, I guess it should be ToDo's responsibility to return None if the Doer referenced by doerID doesn't exist - treating it the same way as the case where no doer has been assigned. Maybe with this SkinScript: WITH Doers.getItem(self.doerID) CALCULATE self.doerID=RESULT.id or '' ? But I'm not really sure about this... I think you've managed very well to stay on the right side of the line in the sand... the problem is that complex real world applications have a lot of stuff on the other side of the line, and the challenge is to pull that stuff over the line. My personal problem is figuring out if the stuff I have on the wrong side of the line is necessitated by the complexity of the application, or if I'm just making things unnecessarily complicated... Itai -- Itai Tavor "Je sautille, donc je suis." C3Works itai(a)c3works.com - Kermit the Frog "If you haven't got your health, you haven't got anything"

3 3

Re: [Zope-dev] ZCatalog catalog_object
by Chris Withers 02 Jan '01

02 Jan '01

Itamar Shtull-Trauring wrote: > > Chris Withers wrote: > > > ...in which case, I wonder why CatalogAwareness goes to the trouble of > > unindexing and then re-indexing? > > Because in older ZCatalog (before 2.3 and maybe before 2.2.4), > catalog_object did not uncatalog automatically. When in doubt, assume > ZCatalog is broken :p Hmmm... I wonder if Chris P or anyone else in the know could confirm the recommended steps to recatalog an object? cheers, Chris

1 0

aq_inContextOf attribute error
by Alex V Koval 02 Jan '01

02 Jan '01

Hello All ! After installing latest stable version of Zope (2.2.4) I tried to install ZFormulator version 0.2. And as result got 2 problems with permissions system. First was in ZFormulator itself, and was corrected: __roles__ = ('manager',) was changed to __roles__ = ('Manager',) but this bug correction worked fine for previous versions of Zope, and in current version adding of field produced error: Attribute Error: aq_inContextOf in line 231 of lib/python/AccessControl/User.py I am nor Zope nor Python hacker, but I tried to correct this line a little, and this worked for me. Please advice did I made it correct way or not. User.py line 231: ---------------- Here was the original code (which produced error): if not parent.aq_inContextOf(self.aq_parent.aq_parent,1): Here is replacement (added check is attribute exists): if hasattr(parent, 'aq_inContextOf') and not parent.aq_inContextOf(self.aq_parent.aq_parent,1): After this correction everything works fine, but since I am not Zope/Python guru, but just a user which wanted some program to start working, I keeping changed locally, but of course I am interested was this correction OK. Regards. -- Alex V. Koval

1 0

What's 'section' in blocks[0] in block dtml tag?
by LEE Kwan Soo 02 Jan '01

02 Jan '01

Hi. I'm playing/struggling to make a custom block dtml tag. Let me call it, dtml-quote tag. dtml-quote tag is similar to dtml-comment tag except it will emit html_quoted, not rendered version of what lies between <dtml-quote> ... </dtml-quote>. (I feel it will be usefull when I show & write some dtml examples on my korean zope site). After seeing around some python sources, I finally got that tname is the name of the tag, args is args, and section is something, in the following code. def __init__(self, blocks): tname, args, section = blocks[0] and section seems to have 6 attributes/methods: '__name__', '_v_blocks', '_v_cooked', '_vars', 'blocks', 'globals', 'raw' But that mistic raw is null string, '' and blocks is no help for me. How can I retrieve the raw source string enclosed in a block tag pair? LEE Kwan Soo. ps. My English is evem more cryptic this morning. Sorry I've sat up alnight play Kingdom Under Fire.

1 0

Re: [Zope-dev] PythonScripts
by Dieter Maurer 01 Jan '01

01 Jan '01

Dieter Maurer writes: > I looked at ZopeCVS's PythonScripts. > I mostly like it -- with the following exceptions: > > * Namespace binding > > It does not yet work, apparently: > .... Sorry! This was my fault: I had update my Zope CVS version but not yet recompiled the shared objects. Dieter

1 0