On 2/1/99 6:46 PM , Jeff Bauer jbauer@rubic.com said:
Zope is first attempting to find ZPublisher, and then (for backward compatibility with Bobo) trying to find cgi_module_publisher. Here's my suggestion. Drop pcgifile.py into your cgi-bin directory after:
1. modifying it's #!/usr/local/bin/python header, if necessary 2. applying the following patch attached below.
Is there any possibility you have an old copy of Bobo or pcgi somewhere in your path?
I realize how frustrating setting up pcgi can be, which is why I wrote pcgifile.py in the first place. For more info, see http://starship.skyport.net/crew/jbauer/persistcgi/ or email me privately. Good luck.
Jeff, Thanks for the help and the patch. At least now I get 'from ZPublisher import publish_module' instead of cgi_ module_publisher... And from what i can tell, my problem seems to stem from the fact that my ISP has PyApache applied with an ancient Python. pcgifile.py has been showing me Python 1.4, and now I think I should finally pay attention. Seems they also are running an older Apache, so I may have my work cut out for me convincing 'em to change. Next question: Can anyone tell me if there is a way to by pass PyApache, or even if in fact the version number I'm seeing is actually Python or perhaps sumthin' weird PyApache tosses out? pcgifile.py output shown below. Thanks again Chris ---------- Python 1.4 (Feb 4 1997) [GCC 2.7.2.1] Apache/1.2b11-dev IOCOM/2.0.v PHP/2.0b11 PyApache/2.25 PCGI info file: Zope.cgi PCGI wrapper: /--deleted--/local/Zope-1.9.0-src/pcgi/pcgi-wrapper error attempting: 'from ZPublisher import publish_module' status: FAILURE Zope.cgi #!/--deleted--/local/Zope-1.9.0-src/pcgi/pcgi-wrapper PCGI_EXE=/--deleted--/local/bin/python PCGI_PUBLISHER=/--deleted--/local/lib/python1.5/pcgi_publisher.py PCGI_MODULE_PATH=/--deleted--/local/Zope-1.9.0-src/lib/python/Main.py PCGI_SOCKET_FILE=/--deleted--/local/Zope-1.9.0-src/var/pcgi.soc PCGI_PID_FILE=/--deleted--/local/Zope-1.9.0-src/var/pcgi.pid PCGI_ERROR_LOG=/--deleted--/local/Zope-1.9.0-src/var/pcgi.log PCGI_NAME=Main PCGI_DISPLAY_ERRORS=1 BOBO_REALM=Zope BOBO_DEBUG_MODE=1 INSTANCE_HOME=/--deleted--/local/Zope-1.9.0-src PCGI_INSERT_PATH=/--deleted--/local/Zope-1.9.0-src/lib/python/
Chris Larson wrote:
---------- Python 1.4 (Feb 4 1997) [GCC 2.7.2.1] Apache/1.2b11-dev IOCOM/2.0.v PHP/2.0b11 PyApache/2.25
And from what i can tell, my problem seems to stem from the fact that my ISP has PyApache applied with an ancient Python. pcgifile.py has been showing me Python 1.4, and now I think I should finally pay attention. Seems they also are running an older Apache, so I may have my work cut out for me convincing 'em to change.
Next question: Can anyone tell me if there is a way to by pass PyApache, or even if in fact the version number I'm seeing is actually Python or perhaps sumthin' weird PyApache tosses out?
Chris, The version issue of Python is something we can work around, I think. You can (?) install your own copy of Python and have Zope.cgi use it. Actually, come to think of it, Python is installed as part of Zope. Change your #! line in pcgifile.py to point to your installed version. Note too, that you can override any environment variables your ISP has assigned in the .conf files by applying them as pcgi directives in the Zope.cgi file, i.e.: PYTHONPATH=... Your ISP's version of Apache is more problematic, however. PyApache will probably only be invoked based on specific path patterns (i.e. .py files or paths from a particular directory). You'll want to avoid this, as experience with PyApache indicates that it's not very stable (no offense to anyone who feels otherwise). It's possible that you could still get the mod rewrite trick to work using the above version of Apache, but I'm not familiar enough with it to offer any useful advice. Perhaps some other oldtimer on this list can recall what this version of Apache is capable of. Best regards, Jeff Bauer Rubicon, Inc.
participants (2)
-
Chris Larson -
Jeff Bauer