I haven't been very deep down into site access things, mainly because I get confused each time I try to set up a SiteRoot. :-) So it may be that some of the features I'd like are already availiable, but that I just didn't know. :-) Anyway, this is what I would like: The virtual hosts of Zope is managed from the Control Panel and not from several objects in several directories. This would mean that if you enter incorrect information, you don't have to reboot the server with SUPPRESS_SITEROOT=1 set in the environment to fix the stupid errors you made, you just go into the Control Panel and fix it.It also means that a customer of a web hotel can't fiddle around with his own SiteRoot. God eh? :-) This Control Panel thingy should also have a possibility to turn on and off individual virtual host mappings without removing the settings, as well as a global on/off. Hope these ideas are useful. ----- Original Message ----- From: "emf" <mindlace@imeme.net> To: <zope-dev@zope.org>; <evan@zope.com> Sent: Saturday, November 24, 2001 9:13 AM Subject: [Zope-dev] SiteAccess improvements
Hello,
There's a very nearly "orphaned proposal":
http://dev.zope.org/Wikis/DevSite/Proposals/SiteAccessUsuabilityImprovements
iMeme has already done some work towards these goals with "SiteAccessEnhanced": http://www.zope.org/Members/sfm/SiteAccessEnhanced
I am taking over this effort, and I have some near-term "goals outlined": http://dev.zope.org/Wikis/DevSite/Proposals/SiteAccessProposedSolutions
I intend to deliver the VHM improvements before the AccessRule
improvements.
Please give feedback on this proposal, and let me know what I need to do to move this into the project phase.