Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Content Profile seems currently limited to one profile node per content type, which I am fine with. Upon trying to add another node for an existing type users are normally redirected to the node edit page. Except for when a user has the 'administer nodes' permission, then strange things start to happen:
function content_profile_nodeapi(&$node, $op, $a3 = NULL, $a4 = NULL) {
if ($op == 'prepare' && is_content_profile($node) && !isset($node->nid) && $node->uid && !user_access('administer nodes') && arg(0) != 'admin') {
// Check if this nodetype already exists
if ($nid = content_profile_profile_exists($node, $node->uid)) {
// This node already exists, redirect to edit page
drupal_goto('node/'. $nid .'/edit', 'destination=user/'. $node->uid);
}
}
Because of that (bogus?) user_access() check, anybody with administrator privileges is actually allowed to create more than profile node (which will never be displayed anywhere, though). This looks like a bug to me.