You can use the zope patches that Martijn helpfully posted to clean this up.... but then you'll be re-patching every time a new zope version is released. If you are willing to tolerate only one /ACLUG you can add one more rule to your rewrite rules: RewriteEngine on RewriteRule ^/ACLUG/(.*) /$1 RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule ^/(.*) /where/you/keep/your/Zope/Zope.cgi/ACLUG/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l] Careful not to put an ACLUG folder inside your ACLUG folder though. ;-) That should clear things up.... -steve
"John" == John Goerzen <jgoerzen@complete.org> writes:
John> Michel Pelletier <michel@digicool.com> writes: >> > How do the rewrite rules impact accessing things like >> /manage? >> >> They don't. I'll add this to the How-To. John> Unfortunately, they do. When I set up a virtualhost to John> point to a subdirectory of the Zope site, the manage screen John> goes berserk. It says things like "Folder at John> /ACLUG/ACLUG/ACLUG" when I ask for /manage on the John> virtualhost. The site is working OK (except for the darn John> base tag) but this isn't. John> Ideas? John> _______________________________________________ Zope John> maillist - Zope@zope.org John> http://www.zope.org/mailman/listinfo/zope John> (To receive general Zope announcements, see: John> http://www.zope.org/mailman/listinfo/zope-announce John> For developer-specific issues, zope-dev@zope.org - John> http://www.zope.org/mailman/listinfo/zope-dev )