Zope June 2007

zope@zope.dev

56 participants
67 discussions

z3c.form 1.3.0, z3c.formui 1.0.1, and z3c.formdemo 1.1.0 released!
by Stephan Richter 28 Jun '07

28 Jun '07

Hello everyone, Roger and I have received a great deal of feedback about the z3c.form* packages. Several people reported that they immediately started using it for their development. Thanks to those people, we were able to identify many bugs and determined new features. The result is a new round of releases! Again for the curious and impatient ... --------------------------------------- We have added two more demos: * An "Address Book" implements a non-trivial example of an address book, including multiple addresses and E-mails. It demonstrates the use of sub-forms, writing custom widgets and composite content. * An "SQL Message" demo reimplemnets the simple "Hello World!" demo only using queries to the Gadfly database. The example adds to the original demo by also providing a message overview screen, since the ZMI is not helpful for pure SQL data. To run the demos do the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/trunk formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -N $ ./bin/demo fg Now you can access the demo under: http://localhost:8080/ Note: Python's Cheeseshop seems to be extremely slow today, so this might take a while. Alternatively, you can use Zope's distribution server: http://download.zope.org/distribution. On the Javascript Front ----------------------- Paul Carduner, as part of his GSOC project, is developing a super-cool extension to the z3c.form* packages that will make it very easy for the Python developer to write AJAX-driven applications. My hope is that Paul will have the first iteration and a demo done in a few weeks! So stay tuned... Changes ------- z3c.form ~~~~~~~~ - Feature: In an edit form applying the data and generating all necessary messages was all done within the "Apply" button handler. Now the actual task of storing is factored out into a new method called "applyChanges(data)", which returns whether the data has been changed. This is useful for forms not dealing with objects. - Feature: Added support for ``hidden`` fields. You can now use the ``hidden`` mode for widgets which should get rendered as ``<input type="hidden" />``. Note: Make sure you use the new formui templates which will avoid rendering labels for hidden widgets or adjust your custom form macros. - Feature: Added ``missing_value`` support to data/time converters - Feature: Added named vocabulary lookup in ``ChoiceTerms`` and ``CollectionTerms``. - Implemented support for ``FileUpload`` in ``FileWidget``. * Added helper for handling ``FileUpload`` widgets: + ``extractContentType(form, id) Extracts the content type if ``IBytes``/``IFileWidget`` was used. + ``extractFileName(form, id, cleanup=True, allowEmtpyPostFix=False)`` Extracts a filename if ``IBytes``/``IFileWidget`` was used. Uploads from win/IE need some cleanup because the filename includes also the path. The option ``cleanup=True`` will do this for you. The option ``allowEmtpyPostFix`` allows you to pass a filename without extensions. By default this option is set to ``False`` and will raise a ``ValueError`` if a filename doesn't contain an extension. * Created afile upload data converter registered for ``IBytes``/``IFileWidget`` ensuring that the converter will only be used for fiel widgets. The file widget is now the default for the bytes field. If you need to use a text area widget for ``IBytes``, you have to register a custom widget in the form using:: fields['foobar'].widgetFactory = TextWidget - Feature: Originally, when an attribute access failed in Unauthorized or ForbiddenAttribute exceptions, they were ignored as if the attribute would have no value. Now those errors are propagated and the system will fail providing the developer with more feedback. The datamanager also grew a new ``query()`` method that returns always a default and the ``get()`` method propagates any exceptions. - Feature: When writing to a field is forbidden due to insufficient priviledges, the resulting widget mode will be set to "display". This behavior can be overridden by explicitely specifying the mode on a field. - Feature: Added an add form implementation against ``IAdding``. While this is not an encouraged method of adding components, many people still use this API to extend the ZMI. - Feature: The ``IFields`` class' ``select()`` and ``omit()`` method now support two ketword arguments "prefix" and "interface" that allow the selection and omission of prefixed fields and still specify the short name. Thanks to Nikolay Kim for the idea. - Feature: HTML element ids containing dots are not very good, because then the "element#id" CSS selector does not work and at least in Firefox the attribute selector ("element[attr=value]") does not work for the id either. Converted the codebase to use dashes in ids instead. - Bug/Feature: The ``IWidgets`` component is now an adapter of the form content and not the form context. This guarantees that vocabulary factories receive a context that is actually useful. - Bug: The readonly flag within a field was never honored. When a field is readonly, it is displayed in "display" mode now. This can be overridden by the widget manager's "ignoreReadonly" flag, which is necessary for add forms. - Bug: The mode selection made during the field layout creation was not honored and the widget manager always overrode the options providing its value. Now the mode specified in the field is more important than the one from the widget manager. - Bug: It sometimes happens that the sequence widget has the no-value token as one element. This caused ``displayValue()`` to fail, since it tried to find a term for it. For now we simply ignore the no-value token. - Bug: Fixed the converter when the incoming value is an empty string. An empty string really means that we have no value and it is thus missing, returning the missing value. - Bug: Fix a slightly incorrect implementation. It did not cause any harm in real-world forms, but made unit testing much harder, since an API expectation was not met correctly. - Bug: When required selections where not selected in radio and checkbox widgets, then the conversion did not behave correctly. This also revealed some issues with the converter code that have been fixed now. - Bug: When fields only had a vocabulary name, the choice terms adaptation would fail, since the field was not bound. This has now been corrected. - Documentation: Integrated English language and content review improvements by Roy Mathew in ``form.txt``. z3c.formui ~~~~~~~~~~ - Bug: Make sure we use the id for the "for" attribute of the "label" element and not the name. This has worked until recently, because the name and id were the same, but they are different now. z3c.formdemo ~~~~~~~~~~~~ - Feature: New "SQL Message" demo shows how ``z3c.form`` can be used with non-object data. Specificically, this small application demonstrates using a Gadfly database using pure SQL calls without any ORM. - Feature: New "Address Book" demo that demonstrates more complex use cases, such as subforms, composite widgets, and mappings/lists Enjoy! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training

4 5

New class, no access to manage_propertiesForm etc.
by Winterflood, Jonathan 27 Jun '07

27 Jun '07

Hi, I have created a new class in my product, but I can't access the PropertyManager pages for it: import Persistence from OFS.PropertyManager import PropertyManager # Zope security infrastructure from Globals import InitializeClass from AccessControl import ClassSecurityInfo class MyClass(Persistence.Persistent,PropertyManager): """ L'objet d'interfacage """ # Properties are default are persistent typed attributes with builtin form # management in the ZMI _properties = ( {'id':'remote_email', 'type':'string', 'mode': 'w'}, {'id':'local_email', 'type':'string', 'mode': 'w'}, ) # default values remote_email = '' local_email = '' # Tabs that are displayed in the ZMI (inherited from the base classes) manage_options = (PropertyManager.manage_options) # Let me see those pages __ac_permissions__=(('Manage properties', ('manage_addProperty', 'manage_editProperties', 'manage_delProperties', 'manage_changeProperties', 'manage_propertiesForm', 'manage_propertyTypeForm', 'manage_changePropertyTypes', ) )) def __init__(self): pass security = ClassSecurityInfo() security.declarePublic('show') def show(self): return str(self) InitializeClass(MyClass) An instance of this class is held as an attribute of a tool in the product. class DBRTool(UniqueObject, SimpleItem, ActionProviderBase, PropertyManager): """Tool for some logic of the DBR site""" def __init__(self): # interfacage self.myInstance = MyClass() Accessing http://.../portal_dbrtool/myInstance shows str(myInstance), but http://.../portal_dbrtool/myInstance/manage_propertiesForm <http://.../portal_dbrtool/myInstance/manage_propertiesForm> shows "You are not authorized to access this resource." After a login that cannot be satisfied. The manage_options and __ac_permissions__ are set according to the instructions in PropertyManager. Where am I going wrong? How can I access these pages? TIA, Jonathan This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

2 2

securing port 8080 behind apache
by Chris Hoy 27 Jun '07

27 Jun '07

Hi I have an a 2.9.6 instance of zope sitting behind apache all the requrest on port 80 work fine but what i would like to do is disable direct access to the 8080 port. I obviously still need access to the management console of zope but i would like to redirect the request via the apache say commin in on port 8090 and then being proxied to the localhost:8080 (this bit i can do) What i would like to do it get the zope to reject all request that don't come from the localhost Chris

2 1

how to restore a copied instance.
by Tudor Gabriel 27 Jun '07

27 Jun '07

hi, i needed to reinstall my zope site on another computer so i installed (in debian) plone-site using aptitude ... it automatically makes a new instance and starts the server. after that i stopped the server ... and copied my site (instance folder) from the other computer over this one. when i start /etc/init.d/zope2.9 start ... it doesn't complain , but i can't open the site. (same instance names, same port number ) i tryied another aproach ... copied back the default installed instance ... and only overwritten the var folder with the data from the original site. this way i hoped that Data.fs which contained all my objects ... will automatically become visible. it doesn't work this way either, it only sees the default objects, i can access the site ... but all my objects are not visible. grep shows that the names of the objects & folders are still in Data.fs ... so they exist ... i think i missed one configuration somewhere ... to make the folders added by me visible. do you know how can i achieve that?

4 3

A question on pool-size
by Manuel Vázquez Acosta 27 Jun '07

27 Jun '07

Hi all, I'm having a rather weird behavior configuring pool-size. I put a pool-size of 20 on two zeo-clients, but monitoring one of them I saw this on logs: 2007-06-26T16:47:02 WARNING ZODB.DB DB.open() has 19 open connections with a pool_size of 10 ------ 2007-06-26T16:47:02 WARNING ZODB.DB DB.open() has 20 open connections with a pool_size of 10 ------ 2007-06-26T16:47:02 CRITICAL ZODB.DB DB.open() has 90 open connections with a pool_size of 7 Sometimes it reported pool-size of 10, and sometimes it reported 7! What could this be? Another question: My expect a load of 50 concurrent requests, so I set zserver-threads to 25 on both zeo-clients, and a pool-size of 20 (but behaving as explained above). Do this conf make any sense? Where should I read to get more info about this matter? Best regards, Manuel. -- View this message in context: http://www.nabble.com/A-question-on-pool-size-tf3984717.html#a11313581 Sent from the Zope - General mailing list archive at Nabble.com.

2 3

Several questions on Z3 Views backported thru Five
by Manuel Vázquez Acosta 26 Jun '07

26 Jun '07

Hi all, I've been asked to deploy a Plone App which must satisfy a load of at least 1200 users over 8 min. I have tested a fresh Plone 2.5.3 with Zope 2.9.7, plus Squid + CacheFu and everything went just fine. The laptop didn't even notice such a load. But, when I installed the Plone App, even much smaller load didn't pass the test. Thus, I have to dig into the source code of the app to find the source of the problems. I have found that the app uses Z3 concepts, specially Views. This question poped into my mind: 1. Does Zope2+Five creates Views everytime they are used, and discard them afterwards? If this is the case, then maybe I should code a ViewFactory which caches frequently used views. This may help. Best regards, Manuel.

4 6

Re: [Zope] temp_folder not MountTemporaryFolder?
by Chris McDonough 26 Jun '07

26 Jun '07

On Jun 24, 2007, at 9:31 PM, Manuel Vázquez Acosta wrote: > Let me see if I got this right: > > According to ZODB.Mount.MountPoint: mount points are Zope objects > that, when traversed, accesses a different database. You got it. > > Do they report themselves as the container-class defined in zope.conf? > I mean, when I traverse to /temp_folder what do I get? Is it the > MountPoint instance or the container-class instance? Where should I > look for this code? It's the container-class instance (or at least it looks like it when you get there, it does a bunch of trickery under the hood). The default container class is Products.TemporaryFolder.TemporaryContainer. You can influence it within zope.conf though. One of the container class instances (mounted at the /temp_folder mount point) is created within the OFS.Application.install_tempfolder_and_sdc method during Zope startup. > > I have "tried" faster but without any luck. I modified OFS.Application > and replaced TransientObjectContainer with > faster.SessionDataContainer, but still I had too many ConflictErrors > (didn't make any measure to compare with TransientObjectContainer). Have you tried putting the session data container *not* in temp_folder? In other words, create a session data container in the root of your zodb, then cause the session_data_manager object to point at that? You may observe better performance (with the penalty of more storage growth) because FileStorage is typically better at resolving conflicts nowadays than TemporaryStorage is. Note that if you're using ZEO, don't put the data container in the root, you will only get more conflicts. Instead, mount a FileStorage somewhere. See http://plone.org/documentation/how-to/multiple-plone-sites-per- zope-instance-using-separate-data-fs-files-for-each-one for a reasonable explanation of how to create new mount points (ignore the Ploney bits, only pay attention to steps 1 and 2). - C

2 1

List of attributes
by Garito 25 Jun '07

25 Jun '07

Hi all! Is it possible to use tal:attributes with a dictionary or something like this? I would like to change/add attributes to a HTML object in a list or a dict like: <tal:b tal:define='atributos python: {'href': ' http://blogs.sistes.net/Garito', 'target': '_blank', 'myCustomAttribute': 'Value1'} <a href="http://www.sistes.net" tal:attributes='atributos'>I'm a link!</a> Thanks a lot! -- Mis Cosas http://blogs.sistes.net/Garito

2 1

Re: [Zope] temp_folder not MountTemporaryFolder?
by Chris McDonough 25 Jun '07

25 Jun '07

Note also that a patch like this one (against the current Zope 2 trunk, you may need to change it based on whichever version of Zope you're using) might shed more light on where your conflict errors are coming from: Index: lib/python/Zope2/App/startup.py =================================================================== --- lib/python/Zope2/App/startup.py (revision 77024) +++ lib/python/Zope2/App/startup.py (working copy) @@ -166,6 +166,9 @@ conflict_errors, unresolved_conflict_errors, startup_time) + from traceback import format_exception + msg = '\n'.join(format_exception(t, v, traceback)) + conflict_logger.log(level, msg) raise ZPublisher.Retry(t, v, traceback) if t is ZPublisher.Retry: try: On Jun 24, 2007, at 9:31 PM, Manuel Vázquez Acosta wrote: > Let me see if I got this right: > > According to ZODB.Mount.MountPoint: mount points are Zope objects > that, when traversed, accesses a different database. > > Do they report themselves as the container-class defined in zope.conf? > I mean, when I traverse to /temp_folder what do I get? Is it the > MountPoint instance or the container-class instance? Where should I > look for this code? > > I have "tried" faster but without any luck. I modified OFS.Application > and replaced TransientObjectContainer with > faster.SessionDataContainer, but still I had too many ConflictErrors > (didn't make any measure to compare with TransientObjectContainer). > > What I have not grasped yet, is how the whole MountPoint thing works > so that /temp_folder vanishes when Zope dies. This must be a > TemporaryStorage in another DB, accessed thru the MointPoint, but I > have not found where this is done. > > Thanks for your response, and best regards, > Manuel. > > On 6/24/07, Chris McDonough <chrism(a)plope.com> wrote: >> /temp_folder is a "mount point" (see your zope.conf file). >> >> Whether or not you put a session data container inside of a temp >> folder, you may get better conflict-related performance out of >> "faster", a drop-in replacement for the stock Zope sessioning >> machinery... see http://www.agendaless.com/Members/tseaver/software/ >> faster/ (but you might not, it depends on the sessioning access >> pattern). In particular "faster" is much better conflict-wise when >> sessions are accessed but not changed in the course of a request. >> >> - C >> >> On Jun 24, 2007, at 8:19 PM, Manuel Vázquez Acosta wrote: >> >> > Hi all, >> > >> > I have been digging into Session Management in Zope, because is >> > causing a little overhead. We have develop a Plone Application, >> which >> > must respond to 30 concurrent user every 12 seconds, we have setup >> > CacheFu and Squid for this. >> > >> > We have used OpenSTA to stress test the application. >> > >> > When we run the bench for a non login test, everything goes just >> fine. >> > But when run a bench in which a user logs in, we observe too many >> > ConflictErrors, which, I thinks, slows too much the application, >> > because zope retries the request 3 times. >> > >> > I have read /temp_folder is RAM based folder, and also that it >> should >> > be a MountPoint, but looking at the code and with the help of >> > DocFinderTab, I have found /temp_folder is a >> > Products.TemporaryFolder.SimpleTemporaryContainer, which seems >> to be >> > just a folder in the ZODB... This sould be this way? Does >> > /temp_folder/session_data is the RAM based storage? >> > >> > Best regards, >> > Manuel. >> > _______________________________________________ >> > Zope maillist - Zope(a)zope.org >> > http://mail.zope.org/mailman/listinfo/zope >> > ** No cross posts or HTML encoding! ** >> > (Related lists - http://mail.zope.org/mailman/listinfo/zope- >> announce >> > http://mail.zope.org/mailman/listinfo/zope-dev ) >> > >> >> >

1 0

temp_folder not MountTemporaryFolder?
by Manuel Vázquez Acosta 25 Jun '07

25 Jun '07

Hi all, I have been digging into Session Management in Zope, because is causing a little overhead. We have develop a Plone Application, which must respond to 30 concurrent user every 12 seconds, we have setup CacheFu and Squid for this. We have used OpenSTA to stress test the application. When we run the bench for a non login test, everything goes just fine. But when run a bench in which a user logs in, we observe too many ConflictErrors, which, I thinks, slows too much the application, because zope retries the request 3 times. I have read /temp_folder is RAM based folder, and also that it should be a MountPoint, but looking at the code and with the help of DocFinderTab, I have found /temp_folder is a Products.TemporaryFolder.SimpleTemporaryContainer, which seems to be just a folder in the ZODB... This sould be this way? Does /temp_folder/session_data is the RAM based storage? Best regards, Manuel.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Zope June 2007