I have several problems with this module, one appears to be a bug:
>If I edit the "profile" content type then edit the "Content profile" [changing the default display style to anything but the default] submit then edit the "profile" type [changing default permissions] the "Content profile" display styles will reset themselves to default again [Display the content's teaser=selected, Include an edit link to the display=checked]

The second issue I have appears to be permissions:
>I am trying to set the permissions so that a user can edit their own content profile but not another users. I can enable/disable view/edit permissions to the various CCK fields I have included, but these do not seem bound to the user? If I enable edit on a given field then any user can edit any other users CCK fields ... [!]

The third issue appears again to be permissions:
>There is no longer a link in the "my account" page to that users content profile when a user clicks edit. If I check "Include an edit link to the display" in the content profile type then when a users views another users profile they are able to select edit for another user! However in no event does the link to the content profile appear in the top "Account Personal Information" section.

Fourth issue:
>In every scenario if a user can edit a content profile [any content profile] they are able to edit the "Title field label" how do I disable this field [or even better provide a default and hide it from the user]??

-sean

Comments

sean69’s picture

sean69 commented

I just now have a new issue....

After updating to the latest version the new user registration page is broken.... I get a php error.

Fatal error: Call to undefined function content_profile_get_setting() in /*SERVER_PATH*/modules/content_profile/content_profile.module on line 119

-sean

sean69’s picture

sean69 commented
Title: bug? + permissions problems... » Permissions Bug

did some more work on the permissions problem, it appears to be a bug?

Users permissions are not updated when changing node permissions in admin. i.e. all users created before content profile was installed have the default content profile permissions. if permissions are changed in admin -> permissions [and I tried the rebuild node permissions in admin as well] the old users still have the default content profile permissions. If a new user is added after the default permissions are changed then that new user has the new permissions so:

user permissions are not updated when node permissions are changed in admin.

-sean

blinko’s picture

blinko commented

I think I can confirm this. I played with permissions & now existing users have lost them (although they are enabled in admin). Pretty dangerous bug.

blinko’s picture

blinko commented
Version: 6.x-1.0-beta2 » 6.x-1.x-dev

I think I managed to better define my issue... It took me a long time to find this... On my Drupal 6.6 + the lastest dev version of the module, I had to give all users FILTER ADMIN permissions (= i suppose this is the ability to post in full HTML) in order for them to be able to edit their Content Profile & see the edit link... If I don't, then they loose the permission to edit their Profile... I guess it's a pretty small bug once you know it can be solved by giving those filter admin permissions... (can anyone confirm this bug?)

sean69’s picture

sean69 commented

Not I, I basically had to remove all my users [luckily still in dev and all users were test users] - set the correct permissions then add users again, I won't be changing anything in content profile till a stable release is ready and tested.

sorry.

blinko’s picture

blinko commented

Not sure it's the same bug. I have recreated all the profiles & prefer not test again if it's still there or not :)

+ I wish I didn't HAVE to give "filter permissions" to users...

czeky’s picture

czeky commented

Hi, any news about "filter permissions" thing?

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Closed (works as designed)

content profile doesn't touch the permission system, you just have to configure drupal's permissions appropriate.

>user permissions are not updated when node permissions are changed in admin.
content profile's are usual nodes - so updating their permissions is either not necessary or if you use a node access module - has to be handled by that module.

@title field: try the auto nodetitle module
@problem 1: upgrade to the dev snapshot, this is already fixed there.