Cant access 'real' root folder in ZMI
Hi, I recently installed plone 3 on a RHEL 5 server and did some mucking around to get apache working with it. I mostly followed the 'apache-with-plone' tutotial on plone.org to do this. The way it is currently set is as follows: - Plone and zope installed on my server ( eg serverA or 10.10.10.1) running on port 8080 - DNS set to point www.me.com to serverA - Apache set to ProxyPass requests from "me.com:80" to "localhost:8080" (I followed the turtorial mentioned above) - My Plone site accessable from either serverA:8080 or www.me.com However, both these methods lead me straight to the plone website, not to the "Zope Quick Start" page and while i can access the ZMI from plone, serverA:8080/manage or www.me.com/managae, the root folder shown there is the plone site's root folder. Even when i stop apache and access through servera:8080 i still get the plone site. I need access to the 'real' root folder, ie the one with "Control_panel", to set some user roles and permissions, but i cant find a way. I think i must have changed a setting while trying to get apache going, but cant remember what I did and I cant seem to find anything solving this problem on the internet. Can anyone point me in the right direction to solve this problem. Thanks Heaps, Fergus
u4302283@anu.edu.au wrote at 2008-1-30 14:07 +1100:
... I recently installed plone 3 on a RHEL 5 server and did some mucking around to get apache working with it. I mostly followed the 'apache-with-plone' tutotial on plone.org to do this. The way it is currently set is as follows:
- Plone and zope installed on my server ( eg serverA or 10.10.10.1) running on port 8080 - DNS set to point www.me.com to serverA - Apache set to ProxyPass requests from "me.com:80" to "localhost:8080" (I followed the turtorial mentioned above) - My Plone site accessable from either serverA:8080 or www.me.com
However, both these methods lead me straight to the plone website, not to the "Zope Quick Start" page and while i can access the ZMI from plone, serverA:8080/manage or www.me.com/managae, the root folder shown there is the plone site's root folder.
You should ask Plone related questions on the Plone mailing list. The magic you see is the effect of an "AccessRule" -- installed by Plone. I hate this kind of magic and my first activity has been to get rid of it. AccessRules can be disabled by an envvar. Then, you can access the Zope Root Folder. You can then see the AccessRule and delete it. I forgot the name of the envvar. Looks at the code. -- Dieter
(Wed, Jan 30, 2008 at 02:07:47PM +1100) u4302283@anu.edu.au wrote/schrieb/egrapse:
I recently installed plone 3 on a RHEL 5 server and did some mucking around to get apache working with it. I mostly followed the 'apache-with-plone' tutotial on plone.org to do this. The way it is currently set is as follows:
Please follow the information on http://wiki.zope.org/zope2/ZopeAndApache and then get your rewrite rule from http://betabug.ch/zope/witch
- Apache set to ProxyPass requests from "me.com:80" to "localhost:8080" (I followed the turtorial mentioned above)
Nobody really uses ProxyPass any more nowadays. apache's RewriteRules are just more flexible. That tutorial is outdated in this respect.
However, both these methods lead me straight to the plone website, not to the "Zope Quick Start" page and while i can access the ZMI from plone, serverA:8080/manage or www.me.com/managae, the root folder shown there is the plone site's root folder.
Even when i stop apache and access through servera:8080 i still get the plone site.
My guess: You probably mucked around with the "Mappings" tab in the Virtual Host Monster. Bad idea. The VHM is to be left alone, any Mappings should be set up using RewriteRule in the apache config. I don't know how you can un-muck this situation in the VHM. Deleting the VHM (e.g. through ftp or webdav) will likely not change anything, but maybe give it a try after a good backup of the Data.fs. Maybe there is a secret request variable to suppress the VHM mapping? But I don't know it.
I need access to the 'real' root folder, ie the one with "Control_panel", to set some user roles and permissions, but i cant find a way.
I think i must have changed a setting while trying to get apache going, but cant remember what I did and I cant seem to find anything solving this problem on the internet. Can anyone point me in the right direction to solve this problem.
If accessing Zope through port 8080 shows the same problem, it's unlikely a problem in the apache config. Regards, Sascha
On Jan 30, 2008 4:07 AM, <u4302283@anu.edu.au> wrote:
However, both these methods lead me straight to the plone website, not to the "Zope Quick Start" page and while i can access the ZMI from plone, serverA:8080/manage or www.me.com/managae, the root folder shown there is the plone site's root folder.
Even when i stop apache and access through servera:8080 i still get the plone site.
Sounds like either an AccessRule or the VirtualHostMonster (VHM) is putting you into Plone directly. You can disable both AccessRules and the VHM by an environment variable or with a URL path element: - set the SUPPRESS_ACCESSRULE environment var - add _SUPPRESS_ACCESSRULE to your URL. So http://servera:8080/_SUPPRESS_ACCESSRULE should solve this for you; double check your VHM configuration if this works, it should be empty. -- Martijn Pieters
--On 31. Januar 2008 13:28:36 +0100 Martijn Pieters <mj@zopatista.com> wrote:
On Jan 30, 2008 4:07 AM, <u4302283@anu.edu.au> wrote:
However, both these methods lead me straight to the plone website, not to the "Zope Quick Start" page and while i can access the ZMI from plone, serverA:8080/manage or www.me.com/managae, the root folder shown there is the plone site's root folder.
Even when i stop apache and access through servera:8080 i still get the plone site.
Sounds like either an AccessRule or the VirtualHostMonster (VHM) is putting you into Plone directly.
You can disable both AccessRules and the VHM by an environment variable or with a URL path element:
- set the SUPPRESS_ACCESSRULE environment var
- add _SUPPRESS_ACCESSRULE to your URL.
So http://servera:8080/_SUPPRESS_ACCESSRULE should solve this for you; double check your VHM configuration if this works, it should be empty.
Or by a rule within your etc/zope.conf. Andreas
participants (5)
-
Andreas Jung -
Dieter Maurer -
Martijn Pieters -
Sascha Welter -
u4302283＠anu.edu.au