I installed the latest Content Profile (6.x-1.x-dev) and tried to test it but I cannot get the users edit their profiles.
Here are the settings I am using:
- User page display style: Display the full content
- Include an edit link to the display: checked
- Show a link to the content profile creation page, if there is no profile: checked
- Use on Registration: checked
I added three test custom fields to the profile node type: first name, last name and about yourself.
The result:
- I tried registering two new users and both times the profile fields did NOT show on the registration page although the "Use on Registration" option was checked and I did not hide any of the fields.
- After successful registration, the new users can go to their "My account" page and there they can see a Profile section that is empty (the profile could not be configured on registration). There is a link "View" under it and that is all. When I click that link, I see an empty profile page and NO option to edit the profile. The new profile fields don't show even under the edit page of the main user account.
- When I log in as the administrator, I can see the new profile nodes created (for each of the new users) and I can edit them. The problem is that the users cannot edit their own profiles.
In summary: the profile fields don't show at registration time and later the new users cannot edit their own profiles.
Is this something that I am doing wrong or this is a bug?
Thanks!
Comments
Comment #1
kirilius commentedAny ideas?
Comment #2
scottrigbydid you give that user's role permission to 'create profile content' and 'edit own profile content' (in admin/user/permissions/ under 'node module')?
Comment #3
kirilius commentedThanks, that did it!
Comment #4
jgraham commentedComment #6
Thomas_Zahreddin commentedPlease provide reasonable defaults:
like users can create and edit their own profile.
Otherwise it needs time to work out how the module is used.
Comment #7
xurizaemonThomas, what are "reasonable defaults" on your site might constitute a security issue for another site. Modules typically take a conservative approach to installing user permissions for this reason.
If you feel the documentation isn't sufficient, then fago will probably appreciate patches to help fix that problem.
The README.txt currently says,
Perhaps it wouldn't hurt to include a link to the README.txt on the module homepage as a docs link.