Needs review
Project:
Content Profile
Version:
6.x-1.x-dev
Component:
Base module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Sep 2009 at 17:56 UTC
Updated:
24 Mar 2011 at 13:59 UTC
Jump to comment: Most recent file
Comments
Comment #1
todd nienkerk commentedI've experienced this as user 1. Users with fewer permissions appear to be limited to one profile node.
Comment #2
todd nienkerk commentedCorrection: Any user with the "administer nodes" permission is sent to the node creation form but receives an error on submit. Line 377 appears to be the culprit:
Removing
&& !user_access('administer nodes')will force that user to edit the existing profile node. Here's the modified line 377:However, the module author is correct to include this code. Otherwise, and admin cannot create profiles on behalf of other users.
The real problem, it seems, is the default "Create content" menu item. Perhaps it's best if the "Create content" menu items for each of the profile content types is removed from the menu? Here's a
hook_menu_alter()that does it:Comment #3
fagoYep, administer nodes people can create profiles on behalf other users, that's supposed to work like that.
But removing the menu item makes sense to me? Could you file a patch? Anyone against this change?
Comment #4
Macronomicus commentedsubscribing ^_^
Comment #5
Philo72 commentedBefore the patch comes out where would i put this little bit of code you have written?
Phil
Comment #6
jeffschulerPatch to add functionality to content_profile_menu_alter() to hide Content Profile types in the Create Content menu.
Instead of unsetting, this sets the menu item's type to MENU_CALLBACK to keep it's path available (but not show it in the menu.)
Comment #7
thepanz commentedFollowing the previous patch I've added an option (a check box in the profile settings page) to choose if the profile should be hidden from the "Create Content" menu.
Comment #8
thepanz commentedSome minor fixes applied
Comment #9
ralt commentedGreat patch!