- Zope - Zope lists

- RE: first install, first connect
by Dave Goodrich 10 Dec '98

10 Dec '98

Yahooooooo Reinstall as user set file and dir permissions to user start server as user I can connect, "Mom, I'm home!" Thanks y'all DAve. This should go into the install instructions, most all other software asks you to be root to compile and install, the instructions for Zope said nothing different so I followed what I thought to be "the norm".

1 0

RE: [Zope] - Killing versus shutting down??
by Jeff Bauer 09 Dec '98

09 Dec '98

> When shutting down Zope, will there be an averse effects if > the serve.py process is killed with a Ctrl-C, as opposed to > shutting down the process using the management screem (assuming > of course, no requests are being handled when this is done!) If you're using INET sockets, the socket may not be immediately available for use after the process has been killed. I think this is an issue with Win32. If using PCGI, you will want to delete the socket and pid files in the var directory. There is a utility .../pcgi/Util/killpcgi.py that can be used to kill the process from the command line. It's argument is the name of the pcgi info file (in this case Zope.cgi). killpcgi terminates the running process and removes the socket/pid files. Regards, Jeff Bauer Rubicon, Inc.

2 1

- first install, first connect
by Dave Goodrich 09 Dec '98

09 Dec '98

Install an compile went fine with no errors (running ZopeHttpServer on a Slackware Linux box) First connect after an easy install , I request "http://myhostnamewenthere:8080/manage" and netscape returned, "Document contains no data". My first guess was that I didn't have permissions to the dir Zope needed, but I checked and I do. So is Zope serving a broken header file? or is this a common first time error? I checked the list archive with no luck. I couldn't find a file/dir "manage" anywhere, even tried a search from "/" with no luck. DAve. The server log shows the following errors. <log> Publishing module Main Serving HTTP on port 8080 ... ---------------------------------------- Exception happened during processing of request from ('xxx.xxx.xxx.xxx, 2194) ---------------------------------------- -------------------------------------er.py", line 295, in publish_module File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 321, in get_environment File "/usr/lib/python1.5/SimpleHTTPServer.py", line 87, in translate_path path = os.getcwd() error: (13, 'Permission denied') Traceback (innermost last): File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 355, in handle_request File "/usr/lib/python1.5/SocketServer.py", line 239, in process_request self.finish_request(request, client_address) File "/usr/lib/python1.5/SocketServer.py", line 243, in finish_request self.RequestHandlerClass(request, client_address, self) File "/usr/lib/python1.5/SocketServer.py", line 362, in __init__ self.handle() File "/usr/lib/python1.5/BaseHTTPServer.py", line 258, in handle method() File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 288, in do_GET File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 295, in publish_module File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 321, in get_environment File "/usr/lib/python1.5/SimpleHTTPServer.py", line 87, in translate_path path = os.getcwd() error: (13, 'Permission denied') </log>

4 3

RE: [Zope] - first install, first connect
by Jeff Bauer 09 Dec '98

09 Dec '98

>> File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", >> line 321, in get_environment >> File "/usr/lib/python1.5/SimpleHTTPServer.py", line 87, in translate_path >> path = os.getcwd() >> error: (13, 'Permission denied') > For some reason os.getcwd is failing. > > Can anyone think of a reason why os.getcwd > would fail? Jim, I can think of a couple reasons: 1) The directory that the program is running in gets deleted. Unlikely, but it sometimes happens when buggy scripts are doing mkdir/chdir stuff. That is not the problem here, unless Dave moved the directory after started his server. 2) I think Dave originally installed Zope as 'root' user, so he may have a directory that server can't access. My earlier advice to him was to scrub Zope and reinstall it as a regular non-root user. Maybe the README should advise not to run Zope as root. Best regards, Jeff Bauer Rubicon, Inc.

1 0

- Advantages of Folders
by Scott Robertson 09 Dec '98

09 Dec '98

Well, after several hours of reading various peoples source code, writting some really stupid products, and drinking way to much coffe. I think I have a pretty good understanding of the Zope basics. (Is it obvious I just broke up with my girl friend or what?) I need to make a collection object. I was planning on inhereting from a folder for this purpose, but I wanted to limit what kinds of objects can be added to this folder. What are the advantages of inheriting from a folder versuses rolling my own collection. I want to try to make my app as consistent to the Zope way of managing things as possible, so I would like to support cutting,pasting, deleteing, roles, etc... My concern is, if I inherit from the Folder and remove the methods to add other objects other than the ones I define is there something that I might be missing that might introduce another object into the folder without my knowledge? -Scott Robertson CodeIt Computing

1 0

RE: [Zope] - RE: First install, First connect
by Paul Everitt 09 Dec '98

09 Dec '98

Janko writes, concerning Dave's "Document Contains No Data" post: > Uh, from someone with Zen-level 0.1. All the information your site > wants to publish and a lot more are in exactly these data.* files, > which are objectstores. Manage is not a html-form or page but > a method > of Zope which evaluates in the current context and gives you a > managment screen for the parent object. Point of clarification here. Many of the built-in things in Zope are class methods. The templates for "manage" (the frameset), "manage_menu" (the left hand navigator), and "manage_main" (the right-hand folder contents) are all class methods. Thus, they don't go into the object database until you edit them in a folder. While it probably doesn't seem possible to create a new "main" method for a folder, well, it is...but not yet documented. *One* of the features of Zope classes is that they allow you to define your own Documents as the management interface for instances of your class. Thus, the "manage" document is actually manage.dtml which is bound as a class method to the Zope folder class. Of course, I haven't been allowed to write Python code in a year, so I might be all wrong :^) Here are two debugging steps that I suggest: 1) telnet to 80 and do "GET /index_html HTTP/1.0" then hit return twice. Email the results to the list. 2) Harness the True Power (tm) of the now-barely-documented Zope Debugger. When we get complete documentation this will be perfectly clear. The Zope Debugger is basically the Python debugger (already documented) with a number of conveniences for Zope built in. After shutting down the server, with one command you could launch the debugger with all the request information such as authentication and step straight to the "manage" object. --Paul

3 2

- Killing versus shutting down??
by Andy Smith 09 Dec '98

09 Dec '98

When shutting down Zope, will there be an averse effects if the serve.py process is killed with a Ctrl-C, as opposed to shutting down the process using the management screem (assuming of course, no requests are being handled when this is done!) Cheers, A.

2 1

- View DTML source on Zope site
by Amos Latteier 09 Dec '98

09 Dec '98

Hi: OK, finally you all can view the DTML source of documents on the Zope site. Look for the "DTML source" link in the lower right of every page. If you're wily, you can find documents that aren't part of the public interface, like standard_html_header, and even the source of the source viewing page! Not everything will make sense, but hopefully you will find it useful. -Amos

1 0

RE: [Zope] - RE: [Zope] -Zope in an RPM
by Jeff Bauer 09 Dec '98

09 Dec '98

Jeff Rush: > I don't have PCGI working yet, as there is no standard > dir structure for cgi-bin stuff, but the standalone > ZopeHTTPServer works ok. Thanks, Jeff. Zope RPMs are a good way to get people to play with Zope. Digital Creations probably already has some ideas about how they want these built and distributed. Here are some random thoughts/observations. The only necessary C program for PCGI is pcgi-wrapper, which defaults to /usr/local/bin, unless specified otherwise in configure. The current Zope distribution leaves it -- along with everything else -- in the install directory. Here are some possible permutations of Zope RPM's: 1. Built-in Apache 2. Use existing Apache setup 3. No Apache Number 1 will be available in non-RPM format at the end of this week. It will be the quickest way for users to get up to speed with Zope/Apache. Number 2 would be for sites that have existing an Apache server running or for users who don't want to depend upon a pre-built version of Apache in their Zope distribution. As part of #2 RPM configuration, it should check that Apache has been installed and that mod_rewrite has been compiled into it. Number 3 isn't strictly necessary, but it might be less confusing to users who want to download Zope, but don't want to use it with Apache, i.e. just use ZopeHTTPServer. something-for-everyone-ly yr's Jeff Bauer Rubicon, Inc.

1 0

- RE: [Zope] -Zope in an RPM
by Jeff Rush 09 Dec '98

09 Dec '98

On Wed, 9 Dec 1998 08:10:08 -0500, Paul Everitt wrote: >Note that our binary kits will *also* include Python, I believe. >Realize that we are aiming Zope at an audience outside the Python >community as well as inside. > >Anyway, our goal is to allow people to *quickly* get something working. >When they see what it does, they can then decide to make the commitment >to use their Python, their Apache, etc. Our plans to get their include: > >o pre-built extensions > >o pre-built Python > >o pre-built, pre-configured Apache, just type "start" > >o recommending the use of the ZopeHTTPServer for evaluation > >o sample apps targetted at both content managers and programmers FWIW, in the past few hours I've downloaded Zope, packaged it as a Red Hat RPM and got it installed successfully. While RPMs don't cover your entire market, they would fit into much of it. Most of the work in doing an RPM was converting the .py makefiles back into sh scripts within the RPM, figuring out dependencies between subsystems and reworking the directory structure in the Zope tar file into the Standard Linux layout. I don't have PCGI working yet, as there is no standard dir structure for cgi-bin stuff, but the standalone ZopeHTTPServer works ok. Oh, and the various extension modules are all built as .so files, so there is no need to mess with the Python interpreter itself. I'll post the RPM, or at least the .spec file in a few days, in case anyone would like it. Now off to learn how to -use- Zope... -Jeff Rush

1 0