Summary: admin web interface works for one site/theme in a cluster (tld2.com) but not another (tld1.com). What magic am I missing? Suspect there's some "connection" between Apache2 config and Zope/Plone/plone-theme that I don't yet understand....
Details: Relatively new to Plone here, far from becoming a "master," but know enough to be dangerous. Inherited maintenance role from previous admin/development of a Plone system, have having to solve problems without having previous admin's assistance. Have a non-production Plone server/system (a virtual-machine copy of a Ubuntu 8.04.4 LTS system), and trying to get a management/plone_control_panel/plone-admin interface to work for 2 sites/themes being served by the same zeocluster (Plone 4.1b2), 2 cluster "clients," one on :8080, the other (client2) on :8081... I think (judging by what the buildout.cfg says, specifically client2 = 8081). Works fine for http://devadmin.tld2.com (note said theme has 'devadmin.tld2.com' listed in its "Unthemed host names") but not for http://devadmin.tld1.com (which only takes me to the tld1.com "themed"/non-manged site). If I just could figure out how to get to the plone-admin interface for the tld1.com think I could get "over the hump," but haven't yet figured it out. Happy to use any combo of http://devadmin.tld1.com:8081/tld1/* ... but nothing works, all just lands at the themed/non-admin site. Note that install point on Ubuntu system is /usr/local/Plone, and each theme is in /usr/local/Plone/zeocluster/src/tld1.theme and src/tld2.theme. Trying to figure out he magic to link tld1.com theme to the tld1.com VirtualHost stuff below, but haven't connected the dots. Need help. Suggestions? Don't yet understand how the apache config below is specifically connected to the theme directories above. Or does it not work that way? Is there some setting in a config file (buildout.cfg seems correct, and I've rerun 'bin/buildout -N' and restarted the cluster)? Or am I just lost/clueless and need someone to show me the way? (Definitely think it's at least partly the latter... ;) ) Here's the pertinent apache2 configs for each tld*.com site/theme. <VirtualHost *> ServerName devadmin.tld1.com ServerAdmin [email protected] RewriteEngine On RewriteCond %{HTTP_HOST} !^devadmin\.tld1\.com RewriteRule ^(.*)$ http://devadmin.tld1.com$1 [R=301,L] RewriteRule ^/(.*) http://127.0.0.1:8081/VirtualHostBase/http/devadmin.tld1.com:80/tld1/VirtualHostRoot/$1 [P] ErrorLog /var/log/apache2/tld1-dev-admin-error.log CustomLog /var/log/apache2/tld1-dev-admin-access.log combined RewriteLog /var/log/apache2/tld1-dev-admin-rewrite.log <Location /watch-info> SetHandler watch-info </Location> <Proxy *> Order deny,allow Allow from all </Proxy> </VirtualHost> [...] <VirtualHost *> ServerName devadmin.tld2.com ServerAdmin [email protected] RewriteEngine On RewriteCond %{HTTP_HOST} !^devadmin\.tld2\.com RewriteRule ^(.*)$ http://devadmin.tld2.com$1 [R=301,L] RewriteRule ^/(.*) http://127.0.0.1:8081/VirtualHostBase/http/devadmin.tld2.com:80/tld2/VirtualHostRoot/$1 [P] ErrorLog /var/log/apache2/tld2-dev-admin-error.log CustomLog /var/log/apache2/tld2-dev-admin-access.log combined RewriteLog /var/log/apache2/tld2-dev-admin-rewrite.log <Location /watch-info> SetHandler watch-info </Location> <Proxy *> Order deny,allow Allow from all </Proxy> </VirtualHost> -- View this message in context: http://plone.293351.n2.nabble.com/4-1b2-http-requests-to-non-themed-site-works-for-one-theme-but-not-the-other-tp6811072p6811072.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-setup
