I still have the problem. And now the site went live, so I am in deep dung! The production location requires me to login to the folder even though all Access Rules and SiteRoots have been deleted. Zope redirects the URL to the old dev location. If I rename the old dev folder, then I cant even log into the production folder. So there is some kind of artifact tying the 2 folders together. I had an Access Rule previously on the dev folder. And it had a proxy_role anonymous. After I deleted the AccessRule and SiteRoot, I copied the dev folder to establish the new production location. But I deleted the Rule, so the role should have been deleted, too, correct? -Trevor
-----Original Message----- From: Evan Simpson [mailto:evan@4-am.com] Sent: Wednesday, October 10, 2001 9:30 PM To: Trevor Toenjes Cc: zope@zope.org Subject: Re: [Zope] Suggestions for finding possible SiteRoot artifact
Trevor Toenjes wrote:
I recently deleted all my SiteRoot instances in favor of enhanced VHM. However, one folder still wants me to log-in in Zope, as if the SiteRoot still exists.
You're sure this isn't just a security setting? Anyhow, if you create and then delete a blank SiteRoot in that directory, it should clean out any possible dangling hook.
Cheers,
Evan @ Zope