August 2003 - Zope - Zope lists

Re: [Zope] Zope on HP-UX 11.11, startup error
by Chris Withers 28 Aug '03

28 Aug '03

(keep replies on the list so other people can pitch in and help out) Roger Beavans wrote: > Thanks for the tip. I am a bit confused though. I did as you suggested, > starting zope with the follwing command line > > ./start -u zope -X -w80 (I'm assuming this is what you meant). > > the server starts fine. Cool :-) > My confusion comes from, I configured Zope with the > "wo_pcgi.py", program. I ran it again to make sure that's what I did. Which > I thought configured zope wo/pcgi? Why does the pcgi server try to start > anyway? No idea, maybe someone else can help? Chris

1 0

Need Functionality of Zope Book
by Brady Joslin 28 Aug '03

28 Aug '03

Hey guys, This one is probably an easy question if you know the answer. I need the exact functionality of the Zope book. I need to dump large amounts of text from books into the CMS and allow comments after each paragraph, which looks to be the exact functionality of the code that runs the book. The perfect example is this page: http://zope.org/Documentation/Books/ZopeBook/2_6Edition/AppendixB.stx Can anyone tell me how I can get that code? Many thanks, Brady __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

3 2

RE: [Zope] Can't build resource file for PCGI on Zope 2.7b1
by Tiller, Michael (M.M.) 28 Aug '03

28 Aug '03

> -----Original Message----- > From: Jens Vagelpohl [mailto:jens@zope.com] > Sent: Thursday, August 28, 2003 9:06 AM > To: Tiller, Michael (M.M.) > Cc: zope(a)zope.org > Subject: Re: [Zope] Can't build resource file for PCGI on Zope 2.7b1 > > > > If PCGI is gone, how can we accomplish the same thing > without opening > > up a > > port? I don't doubt that "[PCGI] is almost never an appropriate > > solution", > > but I cannot seem to figure out what is an appropriate > solution in our > > case. > > Very simple if the frontend webserver sits on the same machine: Have > Zope listen on a port on localhost only. Then your frontend server > simply redirects/rewrites/whatever to that port on localhost. > Thus Zope > won't be reachable on any external interface. Ah...good point. Thanks for reminding me. That is a step in the right direction. BUT, it still seems to me that it isn't as good a named pipe (although I'd be glad to be proven wrong) because with a named pipe *you can control the permissions of the pipe* whereas anyone can connect to the localhost port if they have an account on the machine. Am I missing something again? :-) > jens -- Mike

3 2

Re: [Zope] Zope 2.7.0b2 Released
by Eugene Morozov 28 Aug '03

28 Aug '03

On Thu, Aug 28, 2003 at 09:12:07AM -0400, Chris McDonough wrote: > On Thu, 2003-08-28 at 07:39, Eugene Morozov wrote: > > Unfortunately, problems with languages and encodings other than > > English and latin-1 aren't solved in this beta. There're even no signs > > that someone started to solve this issue. > > I'm not sure what the issues are, but to my knowledge, doing > internationalization work was never on the table for this release. But what's the point in having Internet server which only understand English language and can serve only documents in English? I'm sure that there're many users of Zope using languages other than English, but evidently very few developers. > If there are specific patches or collector issues you can point me at, > perhaps I can help (or at least tell you I can't ;-) There's a patch for Zope 2.7 that adds support for encodings other than latin-1, but it was sent to the zopyrus mailing list so there's no an URL to point you at. I'll check if there're relevant collector issues.

2 1

2.7.0-b2 install failure (setup.py defect, I think)
by Derrick 'dman' Hudson 28 Aug '03

28 Aug '03

I've been using 2.7.0-b1 for a while, so I figured I'd take a look at b2 now. However : $ python2.3 setup.py install --prefix /usr/local/opt/zope-2.7.0-b2 running install running build running build_py running build_ext running install_lib running install_data running install running build running build_py running install_lib running install running build running build_scripts error: mkpath: 'name' must be a string (got None) $ The build succeeds but the install fails. Is something wrong on my system or has the setup.py script changed in some way? -D PS. This is on a debian testing/unstable system. PPS. You don't see any actions in the steps that didn't fail because they already completed successfully the first time. If you want to see more output I can clean out the build and run it again. -- In his heart a man plans his course, but the Lord determines his steps. Proverbs 16:9 http://dman13.dyndns.org/~dman/

3 3

RE: [Zope] Can't build resource file for PCGI on Zope 2.7b1
by Tiller, Michael (M.M.) 28 Aug '03

28 Aug '03

> From: Chris McDonough [mailto:chrism@zope.com] > Subject: Re: [Zope] Can't build resource file for PCGI on Zope 2.7b1 > > > On Mon, 2003-08-11 at 22:33, Jens Vagelpohl wrote: > > > > > > Is PCGI being deprecated from Zope? > > > > It is not receiving much attention anymore, to put it like > that. With > > mechanisms like mod_rewrite and mod_proxy PCGI is almost never an > > appropriate solution anymore. > > Yes, PCGI is being deprecated. Past 2.7 it will no longer > available in > the source distribution (nor in any binary distribution I'm aware of). Hmmm...then I have a question. I've often seen statements like yours above that "[PCGI] is almost never an appropriate solution", but I'm still puzzled by something. For our needs, the fact that request to Zope can be redirected through a named pipe with PCGI (at least that is my understanding, we are in the process of setting this up right now) is very useful because we are looking at using Zope internally on our corporate intranet and the server will *NOT* be behind a firewall. By using a named pipe, it is much easier for us to direct access to the Zope server than if it were hanging off a port. Our current plan is to have iPlanent (not under my control) be the "front end" web server. The iPlanet server will be responsible for authentication. Then, the requests will be redirected to Zope using exUserFolder. Currently, the plan is to do this redirection through PCGI using named pipe. If PCGI is gone, how can we accomplish the same thing without opening up a port? I don't doubt that "[PCGI] is almost never an appropriate solution", but I cannot seem to figure out what is an appropriate solution in our case. Thanks for any help. > - C -- Mike

2 1

Pound web site & mail
by Robert Segall 28 Aug '03

28 Aug '03

During the period August 19th - 27th 2003 we have experienced severe problems with our ISP. The Apsis site may not have been accessible during this time and mail messages sent to us may have vanished or bounced. We apologize for these problems and believe them to be resolved at the present time (we have also switched Internet providers). If you tried to contact us during this period and you received no answer it may well be the case that your message was simply lost - we have certainly not ignored it on purpose; please send it again and we'll do our best to answer it at the earliest. -- Robert Segall Apsis GmbH Postfach, Uetikon am See, CH-8707 Tel: +41-1-920 4904

1 0

Zope 2.7.0b2 Released
by Chris McDonough 28 Aug '03

28 Aug '03

Zope 2.7.0 represents a concentration on software configuration and installation improvement over older versions. It requires Python 2.2.3. Zope 2.7.0b2 is the latest release in the 2.7 development series. You may download Zope 2.7.0b2 from Zope.org at http://zope.org/Products/Zope/2.7.0b2/2.7.0b2 Users should note that Python 2.2.3 is now the required platform. Experimental RPM release An experimental release of Zope RPMS accompany the 2.7.0b2 release. This RPM has been tested under Red Hat Linux 7.3, 8.0, and 9.0. Be aware that the Zope RPM requires the Python 2.2.3 RPM which may or may not be available for your particular platform. See http://www.python.org/2.2.3/rpms.html for more information. A Zope source RPM is also provided for those who choose (or need) to create their own RPM binaries. Particular features of interest in Zope 2.7.0: - DBTab integration (mounted databases for Zope). - New logging module support. - ./configure; make; make install installation from source - configuration-file-driven configuration - integration of ReStructuredText - OrderedFolder support - Many bugxfixes For more information on what is new in this release, see the CHANGES.txt and HISTORY.txt files for the release: - http://www.zope.org/Products/Zope/2.7.0b2/CHANGES.txt - http://www.zope.org/Products/Zope/2.7.0b2/HISTORY.txt For more information on the available Zope releases, guidance for selecting the right distribution and installation instructions, please see: http://www.zope.org/Documentation/Misc/InstallingZope.html

2 1

objects not visible if owner is deletet?
by Elena Schulz 28 Aug '03

28 Aug '03

Hi, ff User_C creates myZPT, i.e. gets the role Owner and I delete User_C after a while, myZPT is not visible any more, even if users (i.e. (User_A, User_B) of other roles (i.e. Role_A and Role_B ) have view-permission. Is that wanted? Do I have to change the ownership of all objects created by User_C or is there an other way to overcome this problem? -- thanks for your hints, Elena My folder structure: root | - content(SecuritySettings: View: Aquired unchecked, only Role_A and Role_B checked) | - Folder1(myZPT, SecuritySettings: View: Aquired checked) | - Folder2 | - acl_users(User_A, User_B, User_C deleted (Owner of myZPT))

2 1

Zope on HP-UX 11.11, startup error
by Roger Beavans 28 Aug '03

28 Aug '03

I have the following problem. HP-UX 11.11, python 2.1.3. I'm trying to start zope with the ./start -u zope, command. the user "zope" has rights to the var directory. 2003-08-28T16:10:22 PANIC(300) z2 Startup exception Traceback (innermost last): File /usr2/usr/local/zope/z2.py, line 748, in ? File /usr2/usr/local/zope/ZServer/PCGIServer.py, line 255, in __init__ TypeError: open() argument 1 must be string, not None any help appreciated, thanks, roger(a)beavans.org

2 1