Yes, the access file was being created in the homeinstance. One thing I didn't do was run the zpasswd.py file when zope was stopped though, as I did with ./zopectl<br><br>
<div><span class="gmail_quote">On 9/29/05, <b class="gmail_sendername">J Cameron Cooper</b> <<a href="mailto:zope-l@jcameroncooper.com">zope-l@jcameroncooper.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">michael nt milne wrote:<br>> Hi<br>><br>> I appear to be having difficulty logging into the ZMI using the password
<br>> created on install. I did change some settings to my root login using<br>> the Samplex member product etc but didn't change the password, login etc.<br>><br>> Anyway I've followed all the instructions in
security.txt, telnetting in<br>> as the user that made the zopeinstance and running<br>><br>> python zpasswd.py access<br>><br>> using SHA-1 and then entering nothing for domains ( I presumed that this<br>
> would give access for all domains etc)<br>><br>> I then get an access denied message on running this and the access file<br>> is not created.<br>><br>> Any help would be appreciated. I guess I can always create a new zope
<br>> instance and delete the old one?<br><br>You must make sure the access file is in the right place (an instance<br>home, I believe) and you have to restart for it to take effect.<br><br> --jcc<br>--<br>
"Building Websites with Plone"<br><a href="http://plonebook.packtpub.com/">http://plonebook.packtpub.com/</a><br><br>Enfold Systems, LLC<br><a href="http://www.enfoldsystems.com">http://www.enfoldsystems.com</a>
<br></blockquote></div><br>