Closed (duplicate)
Project:
Content Profile
Version:
6.x-1.0-beta4
Component:
Base module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Jan 2010 at 15:44 UTC
Updated:
25 Sep 2012 at 05:04 UTC
Jump to comment: Most recent file
Comments
Comment #1
zserno commentedTry the 'administer nodes' permission.
Comment #2
aschiwi commentedDoes that make sense though? Shouldn't a user with the permission to create the content profile content type's nodes be able to see that as well?
Comment #3
greg.1.anderson commentedI just ran into this bug recently -- odd that I missed it for so long, as I have been running content_profile on a D6 site for a couple of years, and only just noticed that 'administer nodes' is required to create content profile nodes.
The function content_profile_page_access is too restrictive;
node_access('create', ...)should be sufficient to create a new content profile node. The attached patch allows semi-priviledged admins with 'createcontent' perms, but not 'administer nodes' perms, to be able to create profile nodes for other users.
Comment #4
greg.1.anderson commented#3 was posted too hastily; I did not notice that, while the change above does in fact allow the menu item to be displayed for the content profile form, clicking on the menu item will bring a user to their own profile rather than a new, empty profile form, unless the profile exists, or they have the 'administer nodes' permission. It seems that perhaps the limitation here is masking a problem in some other module. I haven't had time to track it down yet, though.
Comment #5
zserno commented@greg.1.anderson: hi, there's a long-time running issue about this topic: #697856: Introduce new permission: 'administer content profiles'
Please join and share your ideas.