I have not been able to reproduce this issue. Are you using the access pages manager? or using the page access server behavior?
What is your OS?
What version of Dreamweaver are you using?
If you are using the access pages manager, make sure that the registration is not open in dreamweaver before applying the page restriction.
-Passwords MUST be entered on user update pages:
on the user update pages, the password and confirm password form elements should be set so that the initial value is coming from the users recordset like all of the other elements on the update page. this way the original password will be remembered.
This happens when the Page Access Manager is opened at the end of the creation of these pages. Thus the wizzard has left the file open - this therefore is a bug in how this all works. Not to mention that the Page Access manager opens the file in question in order to add the code (this does work succesfully in this manner however.) Seems like an odd bug to me as the end user.
When using encryption it takes a pile more code for me as the end user to get the password to remain. I have to determine if it is the same hashed code, otherwise the hashed code will get rehashed. :) Is there really no way to make this more seamless for us, so that we can avoid needing to add a whole pile of other code?