Zope 2.2.0 and SiteAccess 2.0.0b2 -- doesn't work?
Hello everybody, I've looked through the mailing list archives and saw one individual who had this problem but seemed to be able to fix it by removing and then re-installing SiteAccess. I haven't been that lucky. I have just freshly installed Zope 2.2.0 on a Red Hat Linux 6.2 machine. The first thing I did after installing Zope was start it up to verify that I can access it (http://localhost:8080/.) Everything works fine. I then stop Zope and install SiteAccess by untaring in the Products directory. I restart Zope. SiteAccess is listed in the products section. I then proceed to add a SiteRoot object in my / folder. After filling in the fields in the creation screen, I press create. At that point I get an error stating that the folder already has a SiteRoot object (even though I am POSITIVE there wasn't one when I started.) I press OK, and the SiteRoot object is there in the folder. However, when I access the / folder with my browser, none of the URLs are modified as I expect them to be. I have tried removing and re-installing SiteAccess, as well as blowing away my Zope install and re-installing. Neither has worked. Furthermore, when I go to delete the SiteRoot object from the directory, I get the following errors: 2000-07-20T17:17:27 ERROR(200) Zope manage_beforeDelete() threw Traceback (innermost last): File /usr/local/EMtech-Zope/lib/python/OFS/ObjectManager.py, line 294, in _del Object (Object: ApplicationDefaultPermissions) File /usr/local/EMtech-Zope/lib/python/Products/SiteAccess/SiteRoot.py, line 4 5, in manage_beforeDelete (Object: SiteRoot) AttributeError: meta Can anybody help me with this? -- Michael Monsen | Due to lack of interest, phydoux@xmission.com | next week has been cancelled. http://www.xmission.com/~phydoux |
How do I get HTTP headers and environment variables on Zope I know that <dtml-var REQUEST> shows me everything, but I only want to get 1 specific variable. thanks in advance Leonardo Kenji Shikida Webmind - Brazil Office
Works great for me. Did you read http://www.zope.org/Members/4am/SiteAccess2/upgrading and do the steps listed there? The one thing I did have to change was my access rule. I had been using the hack where you append /Z/ to manage interface URI's so they don't get rewritten. What I had was using REQUEST.setURL() to put the /Z/ back in, well that method went away. I just changed it to REQEUST.setVirtualRoot() and it worked great. The install docs have apparently been updated to use setVirtualRoot(), as well. -Otto. Michael Monsen wrote:
Hello everybody,
I've looked through the mailing list archives and saw one individual who had this problem but seemed to be able to fix it by removing and then re-installing SiteAccess. I haven't been that lucky.
[snip]
Thanks for responding. On Thu, 20 Jul 2000, Otto Hammersmith wrote:
Works great for me.
Did you read http://www.zope.org/Members/4am/SiteAccess2/upgrading and do the steps listed there?
I am not upgrading from an earlier version of Zope or of SiteAccess. This is a fresh install of Zope 2.2.0 with SiteAccess 2.0.0b2. I suppose I could try these steps even though they don't seem to apply to my situation.
The one thing I did have to change was my access rule. I had been using the hack where you append /Z/ to manage interface URI's so they don't get rewritten. What I had was using REQUEST.setURL() to put the /Z/ back in, well that method went away. I just changed it to REQEUST.setVirtualRoot() and it worked great.
Since I have a brand new fresh install, this doesn't seem to apply to my situation either. (I'll also admit that it's slightly over my head.) This is particularly frustrating to me because I have installed both pieces of software (Zope and SiteAccess) "out of the box", so to speak, with default configurations, and I can't seem to get it to work. I figured that in such a stock environment it would work immediately. -- Michael Monsen | Due to lack of interest, phydoux@xmission.com | next week has been cancelled. http://www.xmission.com/~phydoux |
I just found out why I am having the problem with SiteAccess (and the fix. Many thanks to the author of SiteAccess for responding to me privately with an updated version that helped me find the problem.) I'll post details to the list later tonight, as right now I am a bit pressed for time. Thanks to everybody that responded to my query. -- Michael Monsen | Due to lack of interest, phydoux@xmission.com | next week has been cancelled. http://www.xmission.com/~phydoux |
I'm sorry I didn't post back to the list like I said I would. The issue I was having with Zope 2.2.0 and SiteAccess 2.0.0b2 has been resolved. In short, it was user error. Being new to Zope I didn't realize that the superuser account has special status. I thought it was just the name of the default user that gets created when you install Zope. When I created the SiteRoot object I was using the superuser account, and Zope was complaining that the superuser cannot be the owner of the object. SiteAccess 2.0.0b3 fixes the error reporting so that it doesn't cover up the error with a generic "this folder already has a SiteRoot object." Once I saw the real error I easily resolved it by creating a new account and using that to add the SiteRoot object. Thanks again to those who helped me out. I am learning more and more about Zope, slowly but surely. -- Michael Monsen | Due to lack of interest, phydoux@xmission.com | next week has been cancelled. http://www.xmission.com/~phydoux |
participants (4)
-
Chris Withers -
Leonardo Kenji Shikida -
Michael Monsen -
Otto Hammersmith