_SUPPRESS_SITEROOT and _SUPPRESS_ACCESSRULE do not work. The only way I could work around the problem was to create a new folder inside the problem folder. And then I copied "ALL" the contents to this folder and exported the new folder. The import worked fine. I then renamed the offending/corrupt folder and moved the newly created clone in its place. And the site now runs fine. I kept the offending folder in hopes that I can get any input from the community that has seen this problem. I would like to solve this to better understand if this is a volatility of SiteAccess before using it again. I have no idea where to start to trace the problem on the offending folder. Another admin looked at it, and agreed that it behaves like an AccessRule artifact. Thanks for any feedback, Trevor
-----Original Message----- From: Trevor Toenjes [mailto:zope@toenjes.com] Sent: Thursday, October 11, 2001 5:21 PM To: Evan Simpson; Trevor Toenjes Cc: zope@zope.org Subject: RE: [Zope] Suggestions for finding possible SiteRoot artifact. Site down!!
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