- Zope - Zope lists

force charset in HTTP header from ZPT
by Hong Yuan 16 Aug '04

16 Aug '04

Hi, I have a master template in ZPT for my site with <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> in the <head> section. However, some versions of IE will automatically detect some of the pages rendered with the template as charset of GB2312, although they will identify other pages using the same template correctly. Using 'curl -I' to view the HTTP header sent by ZServer, I found the following: HTTP/1.1 200 OK Server: Zope/(unreleased version, python 2.3.4, linux2) ZServer/1.1 Plone/2.0.3 Date: Mon, 16 Aug 2004 14:04:45 GMT Content-Length: 21824 Etag: Content-Type: text/html It seems that the 'charset=utf-8' part is not sent to the browser in the http header. Is there an easy way to force Zope to send this part in the HTTP header to the client? I was trying to use request.RESPONSE.setHeader method in the ZPT to set this in the HTTP header, but the following syntax <div tal:define="dummy python:request.RESPONSE.setHeader('content-type', 'text/html; charset=utf-8')" /> leads to the error below: EOL while scanning single-quoted string (html", line 1) in expression "python:request.RESPONSE.setHeader('content-type', 'text/html", at line 2, column Zope is taking the semicolon after 'text/html' as a separator instead part of the string. I tried to assign the string to a variable with <div tal:define="content_type string:text/html; charset=utf-8" />, but it doesn't work neither. How can I work around this? Hong Yuan

2 2

win32 install XP SP1 no service installed.
by Paul Gimpelj 16 Aug '04

16 Aug '04

I just downloaded the win32 zope 2.7.x and there was no service installled on XP SP1. Is there a way to install zope as a service. I want to run other linux win32 systems also like tsw wamp. I wish to use the zope web server together with apache. and zope's python. Its an hp 560 with 512mb 160gb 2 pentium system. Any advice would be apreciated. thanks

3 3

RE: [Zope] Zope 2.7.2 still doesn't run as a service in w2k
by Passin, Tom 16 Aug '04

16 Aug '04

> -----Original Message----- > From: Tim Peters [mailto:tim.peters@gmail.com] > Sent: Monday, August 16, 2004 2:18 PM > To: Passin, Tom > Cc: zope(a)zope.org > Subject: Re: [Zope] Zope 2.7.2 still doesn't run as a service in w2k > > [Passin, Tom] > > In almost all cases I have had, surrounding the file name with double > > quotes takes care of any problems. For the same reason, it is good > > practice to write "%1" (with quotes) for the argument placeholder of > > command lines. > > > > I recommend trying this first, before resorting to the 8.3 syntax. > > It probably won't help. Things executed from the shell do quote > processing, because the *shell* does quote processing. Things passed > directly to a Win32 API call often don't get that (mixed) benefit. > The basic Win32 API CreateProcess() call splits arguments on > whitespace, even when the whitespace is inside double quotes (well, > except for the first part of the command line passed to it -- it does > special-case quotes to get at the executable path, but quotes don't > mean anything on the rest of the command line passed to it). Running > as a service eventually has to call CreateProcess() under the covers. Hmm, my version of Zope (the one that installed with Plone2) runs fine as a service using paths with spaces. Doesn't CreateProcess() want the command line parameters to go in a separate arg from the executable? It's been a long time and I might not be remembering right, but I seem to recall vaguely from long-ago Delphi and Powerbuilder days that I had to use a separate arg for the parameters, and then they got handled right, spaces or no. Well, maybe it's been too long. Anyway, Plone2 works on my Win2000 system with long file names. Cheers, Tom P

1 0

RE: [Zope] Zope 2.7.2 still doesn't run as a service in w2k
by Passin, Tom 16 Aug '04

16 Aug '04

> Tim Peters > > [Ausum Studio] > > I ran the service in debug mode and apparently the problem was in > > the path. > > I had already updated it according to > > http://www.zopelabs.com/cookbook/1091948185 , but I had used long > > names with spaces in between: > > "G:\Archivos de programa\Zope27\lib\python" > > > > Changed to 8.3 format and that made > > it.("G:\ARCHIV~1\Zope27\lib\python") > > I don't know all the details, but that makes sense.so far as I do. > Some basic Win32 API calls have no idea what to do with a > space-infected pathname (which is one reason you can still use 8.3 > alias names on the newer Windows filesystems, none of which have an > *obvious* need for them). In almost all cases I have had, surrounding the file name with double quotes takes care of any problems. For the same reason, it is good practice to write "%1" (with quotes) for the argument placeholder of command lines. I recommend trying this first, before resorting to the 8.3 syntax. Cheers, Tom P

2 1

www.zope.org
by Dennis Allison 16 Aug '04

16 Aug '04

www.zope.org responds to pings but cannot be reached by browser.

3 2

urllib.urlopen
by David Siedband 16 Aug '04

16 Aug '04

I'm trying to grab a data file using urllib.urlopen with this code: def powerData(self,REQUEST): import csv import urllib inFile = urllib.urlopen('http://www.davisenergy.com/zeh_data/A042304.DAT') return inFile but I get the error: global name 'inFile' is not defined I've also tried some variations on this: inFile = "".join(urllib.urlopen('http://www.davisenergy.com/zeh_data/ A042304.DAT').readlines()) Ideas on what's not working? thanks -- David

5 4

Programmatically authenticating users?
by Alec Munro 16 Aug '04

16 Aug '04

Hi List, I have an application where I need to have a large number of users. I don't want to override Zope's existing user authentication mechanism, but I am trying to wrap it in my own code, to access additional information about a user. Here's what I want to do: Present user with login form. Pass username and password to Zope to authenticate. If authenticated, retrieve additional information related to that user. One part of this is I would like a user to become an authenticated user as far as zope is concerned once they have logged in via my form. This is the part I am having trouble with. Right now, I simply pass authentication credentials to my acl_users.authenticate method, passing None as the 'request' argument. This seems to return either "None" or a user name, at least as far as the print command is concerned. I don't know a tremendous amount about how user authentication works in Zope, but my assumption is that when you login, say by going to /manage, it returns a cookie of some sort that marks you as authenticated and contains an id to identify who you are authenticated as. How would I provide this functionality in a script of my own making? Thanks for any help. Alec Munro

4 3

CookieCrumbler - default authentication dialog
by John Hunter 16 Aug '04

16 Aug '04

I'm using CookieCrumbler for authentication, and users are directed to login/login for the standard login form. However, when anonymous users try and access a protected resource, a standard http authentication dialog pops up. I want them to be directed to my login/login page instead. Is there some bit of zope pixie dust to enable this? Thanks, John Hunter Zope 2.7 CookieCrumbler 1.2

3 2

read-only visitor skin?
by Reinoud van Leeuwen 16 Aug '04

16 Aug '04

Hi, I am developing a Plone site that will have two skins: a visitors skin (http://www.domain.com) and a management skin (https://manage.domain.com) Simple enough in Plone, but I would like to really make the visitors site read-only, and disable the ZMI. What would be a good approach? - is there a way to disable all authentication at the apache site? - is filtering everything with '/manage' an option? - is there another way to disable the ZMI though a site access rule? or should I run a separate zope instance that mounts the same database read-only? (does this work?) but this would disable things like forums... -- __________________________________________________ "Nothing is as subjective as reality" Reinoud van Leeuwen reinoud.v(a)n.leeuwen.net http://www.xs4all.nl/~reinoud __________________________________________________

2 1

Zope X3 3.0.0 beta 3 released
by Stephan Richter 16 Aug '04

16 Aug '04

Dear Zope community, The Zope 3 development team is proud to announce the third beta release of Zope X3 3.0.0. Zope X3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. The "X" in the name stands for "experimental", since this release does not try to provide any backward-compatibility to Zope 2. Downloads http://zope.org/Products/ZopeX3 Installation instructions for both Windows and Un*x/Linux are now available in the top level README.txt of the distribution. The binary installer is recommended for Windows. Changes since beta 2 - Updated to use ZODB 3.3b2. - Reviewed security and fixed many outstanding open issues. This required some rearranging and writing of security-related code. - Removed several uses of 'removeAllProxies()' as this is considered a bad coding practice. - Added 'zope.security.proxy.removeSecurityProxy()' function to replace 'zope.security.proxy.trustedRemoveSecurityProxy()'. - Implemented rdb:gadflyRoot directive. You are now able to specifically point to a directory that should contain the gadfly databases. - When browsing the source code via the API doc tool's Class Browser, ZCML files are now shown as well. When viewed, a marked up version of the ZCML code is shown with links to other parts of the documentation. - Resolved or otherwise dealt with issues 112, 122, 130, 133, 139, 162, 190, 194, 202, 203, 211, 212, 219, 220, 221, 225, 228, 231, 234, 235, 238, 239, 245, 247, 249, 251, 252, 253, 255. - Fixed various bugs in the API doc tool. - Factory IDs have to be real IDs now, i.e. either a dotted name or a URI. - Cleaned up much of the source code. Now every module should have a module doc string with a title and 'id' tag in it. Goals The API is frozen for X3.0.0. We would like to ask all people to test this release and report any bugs or mis-behaviors! This might be the last beta release! The entire beta period will likely last for about 2 months. During this time we will try to complete the following tasks: - Fix outstanding bugs. - Optimize critical components to speed up the system. - Write and update documentation. - Add and complete translations. - Remove as many XXX comments as possible. Though much progress has been made since the second beta, there are still tasks to be completed! Even if you are not a programmer, you can help! Please send any bug reports and comments to zope3-dev(a)zope.org! Thank you very much in advance for your help! Contributors Jim Fulton, Fred Drake, Dmitry Vasiliev, Philipp von Weitershausen, Stephan Richter, Garrett Smith, Tim Peters. Thanks to everyone!

1 0