Do your users have the permission, to edit their own content objects? Maybe you should grant <b>Content/edit</b> with limitation to Owner=Self to the specific user class.
Thanks for the suggestion. That's one of the many things that I tried and at which I failed. Giving the user edit/self permissions won't work, becuase the user objects were created and are owned by the administrator user.
One option would be to create a new user class, with additional fields, and use those fields to populate the profile. That's probably a good starting point. Copy the existing user class and change it to suit your needs.
More complex options:
Would it be possible to change the ownership of the user object to itself?
I've never tried it, you may be able to create an event that fires after publish and changes the owner of the user object to itself.
Another approach would be to use a backend PHP script to do it.
I wish I had the code to give you, but I don't, and I'm sorry neither of these suggestions are easy to implement.
I experienced this problem until I added the last policy shown here to the role:
Guest Self Edit user selfedit No limitations
Guest Self Edit user password No limitations
Guest Self Edit user preferences No limitations
Guest Self Edit content edit Section( Users ) , Owner( Self )
While the owner is shown as administrator, this seemed to work. I can edit the user account under which I am logged in, but get a permission denied error when trying to edit any other user account or other content object.
