February 2001 - Zope

http://webdav.zope.org DOWN?!
by Tom Freeman 10 Feb '01

10 Feb '01

hey everyone, why is webdav.zope.org not working, i really need to find out about setting up webdav between Dreamweaver UltraDev4 and Zope, but I've looked everywhere and can't find anything? I've run the z2.py script with the -W port option. This works fine, but when I try to transfer files I get the message, 'Unable to authenticate with WebDAV server' what does this mean? any help would be greatly appreciated, thanks, tom. -- ----------------------------------------------------------------------- Tom Freeman Industrial Placement NISS, Eduserv Tel: 01225 323789 Fax: 01225 826177 Web: http://www.niss.ac.uk

4 4

HiperDom ImportError
by Jonathan 10 Feb '01

10 Feb '01

Hi all, Installed PyXML 0.6.3 from RPM, Python version is 1.5.2. Unpacked HiperDom 0.4.0 (DC version) into my Products folder and started Zope (v2.3.0 compiled from source). I get the following traceback: Traceback (innermost last): File "/usr/local/devel/zope/lib/python/OFS/Application.py", line 530, in import_products product=__import__(pname, global_dict, global_dict, silly) File "/home/serva/Development/zope/lib/python/Products/HiperDom/__init__.py", line 3, in ? import HiperDomTemplate File "/home/serva/Development/zope/lib/python/Products/HiperDom/HiperDomTempl ate.py", line 17, in ? import HiperDomStrategies, DomWrapper, utils File "/home/serva/Development/zope/lib/python/Products/HiperDom/HiperDomStrat egies.py", line 3, in ? from xml.dom.Node import Node ImportError: No module named Node Any ideas? Am I missing some vital bit of documentation, a README or am I not the only one running into problems? Cya Jonathan

5 5

html events without Java
by Axel.Missbach＠t-online.de 10 Feb '01

10 Feb '01

Hi to all, im looking for a way to handle the html-events like ondblclick or onfocus, without using java or javascript. Is there a way in callin python-functions? with regards Axel

2 1

Re: [Zope] "finished" product guidelines
by Dieter Maurer 10 Feb '01

10 Feb '01

Chris McDonough writes: > I'd like input on a proposal to standardize a little more on product > distribution and packaging at > http://dev.zope.org/Wikis/DevSite/Proposals/FinishedProductGuidelines. The > idea is to come up with a set of packaging and documentation guidelines > intended to be followed by product developers in order to provide a better > user experience to people attempting to locate products and use products > they get from Zope.org. : All product documentation (besides API documentation) should be : written in Structured Text format. See : http://www.zope.org/Members/millejoh/structuredText for an explanation : of this format. I do not like structuredText very much unless for very simple texts. Especially, inline Python code is a pain. You will recognize this, when you look at Zope's own structured text documentation (--> API, default string argument values). I would suggest, to allow for structuredText or HTML. : Interfaces When I write code, the Interfaces can be directly extracted from the implementation (a long standing fight between me and DC). : Optional: General Coding Style : : When possible and reasonable, each class declared in the product : should live in its own module file. Module files with many (> ~ 5) : classes should be refactored into separate modules. Hugh, Python is not Java. Why should classes be separated into different files? You speak about meta-data standardization but in fact, the proposal suggest few standards. What about using something like Lars M. Garshol's "xsa" XML DTD? You will get more acceptance, when you not only state principles and guidelines but also explain their reason. For example: "Why it is desirable to separate logic from Zope wrapping"? Probably because it facilitates testing, increases application domain, makes for a clearer structure. Dieter

1 0

Re: [Zope] Linux, Zope, Python versions not playing well together?
by Dieter Maurer 10 Feb '01

10 Feb '01

Gary Perez writes: > .... Linux 2.4.1 > kernel, Python 2.0, Zope 2.2.2. (Call it "ProdBox"). > ... > WARNING: Python C API version mismatch for module cStringIO: > This Python has API version 1009, module cStringIO has version 1007. Quite a good error message! Python's C API has changed from 1.5.2 to 2.0. You will see this for all shared objects. What you could try to do: Fetch a Zope source distribution. Compile it with Python 2.0. This will not work out of the box. Have a look at the 2.3 Zope distribution. It has special generation scripts for Python 2.0. Try to patch your Zope 2.2.2 accordingly. Or speak with your Powers to switch to 2.3. Dieter

1 0

Re: [Zope] Display TraceBack in the standard_error_message
by Dieter Maurer 10 Feb '01

10 Feb '01

Olivier Deckmyn writes: > I wonder how I can display error traceback inside standard_error_message (in > fact, it's only to automatically email it in case of error, with REQUEST, > errortype, etc...) > ... > I need to display/use it through a <dtml-var xxx> tag, so that I can insert > it in the body of my debug email. Not too easy. The traceback is generated by "RESPONSE._traceback". As you see, it has an "_" prepended, thus you can not use it from DTML. There is also a "RESPONSE.exception", but it modifies the response body directly. You could try to create an external method that has "RESPONSE" as parameter and returns "apply(RESPONSE._traceback,sys.info())". Dieter

1 0

Re: [Zope] The HOW-TO "Build a Searchable Job Board"
by Dieter Maurer 10 Feb '01

10 Feb '01

Rubinstein Fredrik writes: > .... > <dtml-with "Dokument_skapa.createInObjectManager(REQUEST['id'], REQUEST)"> > .... > Zope Error > Zope has encountered an error while publishing this resource. > Error Type: AttributeError > Error Value: _setId Is it possible that your ZClass "Dokument_skapa" does not inherit from "ZObject" (include standard Zope persistent classes, or so)? Dieter

1 0

Re: [Zope] reading mail with attachment with eudora
by Dieter Maurer 10 Feb '01

10 Feb '01

aZaZel writes: > .... Mail reading problem with Eudora mail reader .... > This is the file's header of the mail produced by that method > > ....... > ..... > Subject: Someone completed the join us form > Content-Type: multipart/mixed; > boundary="216.103.250.202.33.472.981725980.091.23878" > > > --216.103.250.202.33.472.981725980.091.23878 > Content-Type: text/plain > Content-Transfer-Encoding: 7bit > > ..... > --216.103.250.202.33.472.981725980.091.23878 > Content-Type: image/jpeg; > Content-Disposition: inline; > filename="azazel.jpg" > Content-Transfer-Encoding: base64 There needs to be an empty line here! > ...... > ...... At the end, you should have --216.103.250.202.33.472.981725980.091.23878-- > Next an header of a mail with the same file as attachment sent with Mozilla: > ........ > ....... > Subject: PROVA > Content-Type: multipart/mixed; > boundary="------------040707070001010108070700" This is invalid MIME. There needs to be white space before the "boundary", as it is a continuation line. Two ideas: * I did not see the "MIME-Version: 1.0" header. * The MIME standard requires "\r\n" sequences as line separators. However, I would expect few mail readers (and transports) to be picky about that. Dieter

1 0

Re: [Zope] ZClass Containers
by Dieter Maurer 10 Feb '01

10 Feb '01

Harald Scheirich writes: > ... image not displayed through acquired index_html ... In what way is the image not displayed? Does it appear as broken, do you get an exception, do you receive a different object? If the acquired "index_html" is a DTML document (rather than method), then it brings its own context with it. It may then well be that you get a different object. Dieter

1 0

RE: [Zope] Excavating for Clues
by Spicklemire, Jerry 10 Feb '01

10 Feb '01

Dieter Maurer replied: > > Spicklemire, Jerry writes: > > When I call "REQUEST.redirect(other_url)", the REQUEST isn't destroyed, > > in fact all the parameters are retained, right down to the original > > method, so that a "get" method passes parameters appended to the URL, > > and a "post" method includes all the original REQUEST parameters in the > > header. > > The HTTP/1.1 specification is unfortunately very vague with respect > to what should be done with the request parameters. > Thus, browsers have some freedom what they do about them. Oh joy, I haven't even gotten around to testing cross-browser yet! This could very well be an MS Expoder problem. I'll try NS today. > I am unsure what behaviour I would favour: > > If I have a GET method, I would usually not like the > browser to append the old request parameters. > For, if I would like them available, I can easily > add the QUERY_STRING myself. > > However, if I have a POST method, I cannot provide > the request body in the redirect. > It would be natural when the browser would send > the original request body just to the new location. > > I think, the second behaviour is more in line with the > notion of redirection: send the same request to a different > URL. However, my browser (Netscape 4) implements the first > behaviour. The bottom line for me is how to get Zope to do what is needed. It's very possible that I'm once again blurring the line between client side and server side behavior. Symptoms of late stage Javascript burnout. In simplest terms, how can I leverage Zope to point from one page to another and make certain that the troublesome parameters are no longer around to cause problems? > Why are you unhappy about the parameters. > Usually, they do not hurt. My guess is that it's the Acrobat plug-in isn't happy about them, so it can't just display the .PDF file, instead it generates an error message. However, all I have to do is to hit <shift> <refresh> and the .PDF displays normally. Yet another mystery . . . Thanks, Jerry S.

2 1