- Zope - Zope lists

Global Variable In PT
by tonylabarbara＠aol.com 24 Aug '07

24 Aug '07

Hi: I have this code (editing out the extraneous) at the beginning of a page: <body bgcolor="#ffffff" tal:define="newRow string:yes"> After calling some other variables (specifically rotating through a changing ¨item¨ (for item in items...)), I try and change newRow: Then I try and call newRow: But it gives me the original value. Now, if I edit the page like this: it gives me a different value (the one I expect and want). Obviously, my ¨global¨ definition isn´t going global. What can I do to make it global; that is, call it outside of the span tag? TIA, Tony ________________________________________________________________________ Email and AIM finally together. You've gotta check out free AOL Mail! - http://mail.aol.com

3 2

New set of z3c.form* releases!
by Stephan Richter 24 Aug '07

24 Aug '07

Hi everyone, in the past month more project-related work, user feedback/requests and Javascript work has driven the development of the z3c.form framework. There are many new exciting features. There were also some small refactoring changes, which might require your CSS and tests to be adjusted. Please read the changes section below carefully! As always, the demos can be run using: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.4.0 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -N $ ./bin/demo fg Thanks to Roger, Windows users should be able to run the demos this way now as well! Visually, not much has happened; there are no new demos. However, just wait until the next round of z3c.formjs* releases! Changes ------- - Feature: An event handler for ``ActionErrorOccurred`` events is registered to merge the action error into the form's error collectors, such as ``form.widgets.errors`` and ``form.widgets['name'].error`` (if applicable). It also sets the status of the form. (Thanks to Herman Himmelbauer, who requested the feature, for providing use cases.) - Feature: Action can now raise ``ActionExecutionError`` exceptions that will be handled by the framework. These errors wrap the original error. If an error is specific to a widget, then the widget name is passed to a special ``WidgetActionExecutionError`` error. (Thanks to Herman Himmelbauer, who requested the feature, for providing use cases.) - Feature: After an action handler has been executed, an action executed event is sent to the system. If the execution was successful, the event is ``ActionSuccessfull`` event is sent. If an action execution error was raised, the ``ActionErrorOccurred`` event is raised. (Thanks to Herman Himmelbauer, who requested the feature, for providing use cases.) - Feature: The ``applyChanges()`` function now returns a dictionary of changes (grouped by interface) instead of a boolean. This allows us to generate a more detailed object-modified event. If no changes are applied, an empty dictionary is returned. The new behavior is compatible with the old one, so no changes to your code are required. (Thanks to Darryl Cousins for the request and implementation.) - Feature: A new ``InvalidErrorViewSnippet`` class provides an error view snippet for ``zope.interface.Invalid`` exceptions, which are frequently used for invariants. - Feature: When a widget is required, HTML-based widgets now declare a "required" class. - Feature: The validation data wrapper now knows about the context of the validation, which provides a hook for invariants to access the environment. - Feature: The BoolTerms term tokens are now cosntants and stay the same, even if the label has changed. The choice for the token is "true" and "false". By default it used to be "yes" and "no", so you probably have to change some unit tests. Functional tests are still okay, because you select by term title. - Feature: BoolTerms now expose the labels for the true and false values to the class. This makes it a matter of doing trivial sub-classing to change the labels for boolean terms. - Feature: Exposed several attributes of the widget manager to the form for convenience. The attributes are: mode, ignoreContext, ignoreRequest, ignoreReadonly. - Feature: Provide more user-friendly error messages for number formatting. - Refactoring: The widget specific class name was in camel-case. A converntion that later developed uses always dash-based naming of HTML/CSS related variables. So for example, the class name "textWidget" is now "text-widget". This change will most likely require some changes to your CSS declarations! - Documentation: The text of ``field.txt`` has been reviewed linguistically. - Documentation: While reviewing the ``form.txt`` with some people, several unclear and incomplete statements were discovered and fixed. - Bug (IE): In Internet Explorer, when a label for a radio input field is only placed around the text describing the choice, then only the text is surrounded by a dashed box. IE users reported this to be confusing, thus we now place the label around the text and the input element so that both are surrounded by the dashed border. In Firefox and KHTML (Safari) only the radio button is surrounded all the time. - Bug: When extracting and validating data in the widget manager, invariant errors were not converted to error view snippets. - Bug: When error view snippets were not widget-specific -- in other words, the ``widget`` attribute was ``None`` -- rendering the template would fail. Enjoy!

1 0

How do I eval a variable within the acquisition path?
by Tim Nash 22 Aug '07

22 Aug '07

I apologize for the question (the zope area of my brain must need coffee) but I can't find the answer in the zope book or in any of the scripts posted to the zope cookbook. I want to use a variable in a acquisition path. So for example, from the zope book on scripts, imagine that vaccinateplan() printed out a specific animals vaccination plan. Now instead of saying 'LargeAnimals' and 'hippo' like so: print context.Vet.LargeAnimals.hippo.vaccinateplan() I want to do like this: category = REQUEST.form['category'] animal = REQUEST.form['animal'] print context.Vet.category.animal.vaccinateplan() but I get an Attribute Error. How do I eval a variable within the acquisition path? Thanks, Tim

4 6

asynchronous MailHost
by Sean Fulmer 21 Aug '07

21 Aug '07

I just read about the latest changes to MailHost: http://blog.zopyx.com/blog_ajung/archive/2007/08/19/zopes-mailhost-overhaul… I'm currently using MaildropHost to do async delivery and would like to streamline that setup if possible. Can the latest MailHost be dropped into Zope 2.9.8? -- Sean Fulmer wsfulmer(a)gmail.com

4 3

cannot access POST content in Zope
by Manuel Spuhler 20 Aug '07

20 Aug '07

Hello, I am trying to record the result of a POST request sent to Plone. I can get the content of the POST when I send the file post.xml (valid xml) curl http://elevator.sytes.net/RSR/setSMS -d @post.xml In this case, CONTENT_TYPE headers is set to 'application/x-www-form-urlencoded' by curl. but the content of the POST is empty when I do curl http://elevator.sytes.net/RSR/setSMS -H "Content-Type: text/xml" -d @post.xml I'm working on integrating SMS on Plone, and the external system sends me a text/xml header, text/xml is the right type, I think, according rfc 3023 I have been tracking the frames through tcpdump and the request looks good before zope. I have then parsed the code of Zope to find where I could change this, but I can't figure it out for the moment, and maybe it's something which need to be changed. Could you help me to fix this please? Best regards Manuel Spuhler www.rsr.ch Zope 2.9.7-final, python 2.4.4, Plone 2.5.3

4 7

Why doesn't os.system(command) work?
by rieh25 17 Aug '07

17 Aug '07

I have an external method like this: import os def ext_programm(): os.system('notepad.exe') But it doesn't work. -- View this message in context: http://www.nabble.com/Why-doesn%27t-os.system%28command%29-work--tf4283613.… Sent from the Zope - General mailing list archive at Nabble.com.

5 10

URL_Rewrite
by tonylabarbara＠aol.com 16 Aug '07

16 Aug '07

I have this line of code: <a tal:define="std modules/Products.PythonScripts.standard; url_quote nocall: std/url_quote; x python:url_quote(here/CheckOutAfterEditStuff)" tal:attributes="href string:${here/renumberTheCart/absolute_url}?doc=${x}">test</a> but I get this error: Error Type: NameError Error Value: name 'CheckOutAfterEditStuff' is not defined So I tried this: <a tal:define="std modules/Products.PythonScripts.standard; url_quote nocall: std/url_quote; x python:url_quote(here/Our_Store/CheckOutAfterEditStuff)" tal:attributes="href string:${here/renumberLarimanCart/absolute_url}?doc=${x}">test</a> and I got the same error, although now it can't find "Our_Store". Now, "Our_Store" is the container for this PT and "CheckOutAfterEditStuff" is in the same container. What am I doing wrong? TIA, Tony ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com.

3 2

Zope 3 Foliage Sprint
by Stephan Richter 16 Aug '07

16 Aug '07

Hi everyone, it has been over a year, since we had a conference-independent fully Zope 3 focused sprint. And I think it is time to have one! :-) Thanks to JSA Tech, there will be a sprint between September 24-28, 2007 right in the center of historical Concord, Massachusetts. We have reserved a big room where we can easily fit 35 people. For details, go to the link below: http://wiki.zope.org/zope3/FoliageSprint Now that some fairly large Zope 3 projects are in production, this will be a great opportunity to share our experiences, to learn from each other and discuss new directions that we would like to go. Upon request, I will also give some of my Zope 3 training sessions during the sprint. So I envision the sprint to be interesting for any level of Zope 3 developer, from the beginner to the expert. So sign up now! Just add yourself to the list of participants in the Wiki or send me an E-mail, if you can't. Regards, Stephan

1 0

Re: [Zope] URL_Rewrite
by Garito 16 Aug '07

16 Aug '07

This is another problem. You need to import url_quote in order to use it But my help was about the error you send See u 2007/8/16, tonylabarbara(a)aol.com <tonylabarbara(a)aol.com>: > > Your solution didn't work. It throws an error, stating "url_quote" is not > defined. Actually, the solution I posted below *did* work, but I needed to > clean up the code being tossed around (I found a mistake). > Thanks, > Tony > > > -----Original Message----- > From: Garito <garito(a)sistes.net> > To: tonylabarbara(a)aol.com <tonylabarbara(a)aol.com> > Sent: Thu, 16 Aug 2007 12:49 am > Subject: Re: [Zope] URL_Rewrite > > python: url_quote(path('here/CheckOutAfterEditStuff')) > > Cheers > > 2007/8/15, tonylabarbara(a)aol.com < tonylabarbara(a)aol.com>: > > > > I have this line of code: > > > > <a tal:define="std modules/Products.PythonScripts.standard; url_quote > > nocall: std/url_quote; x python:url_quote(here/CheckOutAfterEditStuff)" > > tal:attributes="href > > string:${here/renumberTheCart/absolute_url}?doc=${x}">test</a> > > > > but I get this error: > > > > *Error Type: NameError > > Error Value: name 'CheckOutAfterEditStuff' is not defined* > > > > So I tried this: > > > > <a tal:define="std modules/Products.PythonScripts.standard; url_quote > > nocall: std/url_quote; x > > python:url_quote(here/Our_Store/CheckOutAfterEditStuff)" > > tal:attributes="href > > string:${here/renumberLarimanCart/absolute_url}?doc=${x}">test</a> > > > > and I got the same error, although now it can't find "Our_Store". Now, > > "Our_Store" is the container for this PT and "CheckOutAfterEditStuff" is in > > the same container. What am I doing wrong? > > TIA, > > Tony > > ------------------------------ > > AOL now offers free email to everyone. Find out more about what's free > > from AOL at *AOL.com * <http://www.aol.com/?ncid=AOLAOF00020000000437>. > > > > _______________________________________________ > > 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 ) > > > > > > > -- > Mis Cosas > http://blogs.sistes.net/Garito > ------------------------------ > AOL now offers free email to everyone. Find out more about what's free > from AOL at *AOL.com* <http://www.aol.com?ncid=AOLAOF00020000000437>. > -- Mis Cosas http://blogs.sistes.net/Garito

1 0

Another "Structure" Problem
by tonylabarbara＠aol.com 16 Aug '07

16 Aug '07

Hi; I can work around this one, but it's not as elegant and will waste an hour or so. Here's the problem I'd like to resolve. I have this line of code: <a tal:attributes="href string:${here/renumberTheCart/absolute_url}?doc=${here/CheckOutAfterEditStuff}">test</a> The problem is that "doc" comes back with all the special characters in ASCII: <a href="http://203.223.152.46:8080/lariman.com/s/renumberTheCart?doc=<div>&lt… type="hidden" name="redirect_cmd" value="_cart"> etc. Is there a way to work around this? TIA, Tony ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com.

4 6