- Zope-Dev - Zope lists

trying to update an archetype field
by Sadullah Mr S 28 Sep '04

28 Sep '04

Hello, I have been trying to update an archetype field after upgrading to Plone 2.0.4 using Archetypes 1.2.5rc4. Every time i try to click on edit i get -- This message has been scanned for viruses and dangerous content by the Cranfield MailScanner, and is believed to be clean.

2 1

script to test update error
by Sadullah Mr S 28 Sep '04

28 Sep '04

Hello, I have upgraded the product plone on zope to version 2.0.4 and have been trying to edit content with the archetype product 1.2.5rc4. I get attribute error: unicode policy. Is there a simple script i could use to loop through all the content on a site and check (when in edit and then save ) the attribute error that comes up and get the path of the object where that error exists? Regards, Shayan. -- This message has been scanned for viruses and dangerous content by the Cranfield MailScanner, and is believed to be clean.

1 0

AW: AW: [Zope3-dev] Release for Views As Adapters
by dev＠projekt01.ch 28 Sep '04

28 Sep '04

Jim Fulton wrote: > Betreff: Re: AW: [Zope3-dev] Release for Views As Adapters > > > dev(a)projekt01.ch wrote: > > ... > > >>These particular changes are no cause for a new release. > > > > > > We use some removed concepts like: > > > > _context.action( > > discriminator = ('view', for_, name, > IBrowserRequest, layer), > > callable = handler, > > args = (zapi.servicenames.Presentation, 'provideAdapter', > > IBrowserRequest, new_class, name, for_, > Interface, layer, > > _context.info), > > ) > > You have your own view directive? > > Why? We can take alook at this at the IsarSprint. Or if you interessted you can see the metaconfigure at: http://svn.tiks.org/viewcvs/Tiks/trunk/src/tiks/skinbase/slots/metaconfigure .py?rev=1244&view=markup and the mixin class for the multipage directive: http://svn.tiks.org/viewcvs/Tiks/trunk/src/tiks/skinbase/slots/app/portletvi ewclass.py?rev=1236&view=markup > > Is there a way for to register this views for both version of z3? > > You might be able to call the default view directive. I > can't really tell because I don't know what you're doing. I will take a look at the new api. Thanks Roger > Jim > > -- > Jim Fulton mailto:jim@zope.com Python Powered! > CTO (540) 361-1714 http://www.python.org > Zope Corporation http://www.zope.com http://www.zope.org > > _______________________________________________ > Zope3-dev mailing list > Zope3-dev(a)zope.org > Unsub: > http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch > >

2 1

ZPT Optimization Opportunity
by Tres Seaver 27 Sep '04

27 Sep '04

After seeing Chris McDonough's excellent paper at the Plone conference on optimizing content delivery using the new IStreamIterator iterface, I began experimenting with implementing such an optimization in ZopePageTemplates. I played around with having 'ZopePageTemplate._exec' request that it receive an iterator, instead of the usual big string. I hoped that such a change might enable greater concurrency and memory footprint, by avoiding creation of the big string at all; instead, medusa to push out the "chunk stream" represented by the StringIO buflist, while the appserver would be free to handle a new request without needing to malloc / copy the data. Here are the timings I have seen so far, using 'zopectl debug', with the following template: --------------- Template source -------------------------------- <html> <body> <div tal:repeat="item python:[x for x in range(1000)]" tal:content="item">ITEM</div> </body> </html> ---------------------------------------------------------------- --------------- Before the patch ------------------------------- >>> Zope.debug('/test_iter', t=1) 250.2 milliseconds >>> Zope.debug('/test_iter', t=1) 106.7 milliseconds >>> Zope.debug('/test_iter', t=1) 106.5 milliseconds >>> Zope.debug('/test_iter', t=1) 124.6 milliseconds ---------------------------------------------------------------- --------------- After the patch -------------------------------- >>> Zope.debug('/test_iter', t=1) 249.2 milliseconds >>> Zope.debug('/test_iter', t=1) 107.2 milliseconds >>> Zope.debug('/test_iter', t=1) 125.0 milliseconds >>> Zope.debug('/test_iter', t=1) 162.1 milliseconds ---------------------------------------------------------------- Given that the performance looks similar in this context, which doesn't benefit from the medusa / concurrency intent of the patch, it seems as though it might be a win (of *course* there aren't any tests for it!) I am attaching the patch I have so far for review and comment. Tres. -- =============================================================== Tres Seaver tseaver(a)zope.com Zope Corporation "Zope Dealers" http://www.zope.com

5 10

Survey on Open Source
by Mike Chan 26 Sep '04

26 Sep '04

Dear all, I am conducting a survey on open source software. This is for my academic coursework and dissertation. It will be great to have your support and participation in this survey. This survey has two separate questionnaires, focusing on the following areas: 1) OSS development (Developers or those who contribute in coding or documentation), and 2) IT/IS costs (CIOs or IT Managers). You are free to go for the questionnaire that is appropriate for you. Below are the links: 1) Brief introduction page: http://web.singnet.com.sg/~mikecck/opensource/Introduction1.htm 2) Questionnaire 1(Open Source Development): http://web.singnet.com.sg/~mikecck/opensource/WebFormA1.htm 3) Questionnaire 2(Open Source and IT/IS Cost): http://web.singnet.com.sg/~mikecck/opensource/WebFormB1.htm Thank you for your time. Mike Chan Student Curtin University of Technology

1 0

September Bug Day Roundup
by Chris Withers 25 Sep '04

25 Sep '04

Hi All, Well, it looks like another bumper crop, not quite eclipsing the 60 issues in July's bug day, but still, 32 issues got dealt with including 9 resolved issues. 2 of those had seen lots of work throughout the month and it was great to finally put them to bed. Session stuff and what-happens-to-transactions-when-errors-get-handled-by-ZPublisher both seem to have been resolved, and make 2.7.3 quite a compelling prospect once Andreas gets a chance to release it. Anyway, thanks to everyone who helped out, look forward to seeing you all (and more) next month... cheers, Chris The lowdown as before: Resolved: #789 - Zope's transaction behaviour flawed #819 - No id returned after import #820 - ZCTextIndex: broken link in manageZCTextIndex.dtml #982 - CMF FSDV skins differ across unix/windows #1401 - SystemError in SessionDataManager #1457 - ZCTextIndex: QueryError and ParseError not available for import #1473 - zpasswd.py: username from command line and password from tty #1479 - browser time out viewing index tab of ZCatalog #1483 - error in documentation for fast-cgi configuration Rejected: #821 - ZCTextIindex: Vocabulary query page problem #973 - BaseStorage.tpc_finish does not release ZODB.DB lock #992 - ZCatalog weirdness when a cookie has the same ID as an index #985 - import Testing changes attributes available to Zope.app() #994 - Precondition property cannot be set #1009 - Zope 2.7b1 problems with refreshing products #1022 - zpt barfs on <script>document.write("<script>") workaround #1455 - Transient Obj Container: values always resetted after a restart #1482 - weird problem with ZMySQLDA #1499 - misunderstanding of MailHost's send method Wontfix: #1502 - KDE's Konquerer won't FTP .jpg properly Deferred: (meaning act on these or they get rejected next month) #551 - ExtentionClass.h might conflict with other system versions #576 - Importing ZClass fails #679 - ZPT: bogus close tag </link> should be removed #721 - ZPT escapes attributes when it shouldn't #745 - zope2.6.1b1 and zclass #764 - ZCTextIndex does work in enumerateIndexes() #808 - Site Access Rule not working with dtml method in 2.6.1 #881 - Error: The ZGadflyDA product must be installed #912 - import of PythonScript causes unseemly failure #941 - Emergency user can own objects in Zope 2.7 #971 - Version only saves the last change #995 - zope/python seg fault with infinite __str__ recursion And here's the "player stats" ;-) Resolved Rejected Wontfixed Deferred Assists chrisw 5 2 10 ajung 2 3 1 mcdonc 1 1 tim_one 1 regebro 5 2 tseaver 2 yuppie 1 dunny 1 -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

NOT operator in Unindex.
by Johan Carlsson 24 Sep '04

24 Sep '04

Hi, I've been hacking FieldIndex and KeywordIndex to allow it to take the operator not to exclude object that matches from the result. As it seems to me it would be possible to patch the Unindex with the changes I've made. Is this something that could be added to the core? Examples of special not-enabled indexes: http://zope.org/Members/Colliberty/Easy%20Pieces/EasyIndexes/EasyIndexes-0-…

3 2

Re: [Zope-dev] NOT operator in Unindex.
by Johan Carlsson 24 Sep '04

24 Sep '04

Andreas Jung wrote: > Why don't you use AdvancedQuery+ManageableIndes by DM? Sure. Why would that be preferred? And is there any chance of AdvancedQuery+ManageableIndes will make it to the Zope Core? My exampel extends Field- and KeywordIndex and any other index based on Unindex without changing backward compatability. I don't see a reason why this couldn't be included to the Zope Core in a short term. Regards, Johan Carlsson -- Johan Carlsson Tel: + 46 8 31 24 94 Colliberty Mob: + 46 70 558 25 24 Torsgatan 72 Email: johanc(a)easypublisher.com SE-113 37 STOCKHOLM

2 1

2.7 branch: attribute permission problems
by Richard Jones 22 Sep '04

22 Sep '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [might dupe - sent the first copy of this from the wrong address, sorry!] I've just upgraded to use the bleeding-edge 2-7 branch (from 2.7.2, running in py 2.3.3) and I've started getting permission problems with attributes. The cause appears to be acquired attributes. With VerboseSecurity installed (note: behaviour not dependent on VS - I checked), I get told: Error Type: Unauthorized Error Value: The container has no security assertions. Access to 'secure_url' of (CG Conference Proposals proposals at 0x41387b40) denied. The "secure_url" attribute is defined at a much higher object, where we have a declaration including: security.setDefaultAccess({'secure_url': 1}) On the "proposals" object though, we don't have any delaration for the "secure_url" attribute. If I add one, or a general security.setDefaultAccess("allow"), then the error goes away. This doesn't seem correct to me. The relevant change in CVS appears to be: *** ../../../../Zope-2.7.2/lib/python/AccessControl/ImplPython.py 2004-02-10 17:46:02.000000000 +1100 - --- AccessControl/ImplPython.py 2004-09-15 09:59:41.617423171 +1000 *************** *** 551,560 **** return v validate = SecurityManagement.getSecurityManager().validate - - # Filter out the objects we can't access. - - if hasattr(inst, 'aq_acquire'): - - return inst.aq_acquire(name, aq_validate, validate) - - # Or just try to get the attribute directly. if validate(inst, inst, name, v): return v raise Unauthorized, name - --- 551,556 ---- The change note being "- Removed DWIM'y attempt to filter acquired-but-not-aceessible results from 'guarded_getattr'." and I'm not sure what that means :) Richard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBR5hnrGisBEHG6TARAuucAJ42D8pU6kuPQ+mBwadqJq8uQbG12gCggN2u AzBBhs5eCekTdl6bYtyBrCk= =aUXn -----END PGP SIGNATURE-----

4 13

Multi-part export files
by Johan Carlsson 22 Sep '04

22 Sep '04

Hi Y'all, I have currently implemented a object repository which uses dynamic Acquisition wrapping to create an illusion of a object hierarchy. This means that sub object isn't contained in there parents rather in the repository and this effectively breaks export/import behavior and other behavior that rely in it such as CopySupport. After doing some testing I've noticed that I can "stack" export files in the same file by just keeping the file open between the calls to exportFile (and the same for importFile). In this way I could stack a number of export files in one file (this could be used to export a set of object in a Folder in one file so it might be useful for Zope Core as well). Now the problem is that the import has no way to know where to create the object, in my case I can let the repository handle this using meta data in the objects. The repository has a fixed structure, but in regular OFS the structure might vary from system to system. It could be used to import all object to the current folder, if name collision are taken care of. Any thought on this? Anybody done something remotely similar? Could this be a useful feature in Zope core someway? Best Regards, Johan Carlsson -- Johan Carlsson Tel: + 46 8 31 24 94 Colliberty Mob: + 46 70 558 25 24 Torsgatan 72 Email: johanc(a)easypublisher.com SE-113 37 STOCKHOLM

1 0