I added a profile field and used 'Profile' as a category name.
When I save the field I get this error message:

user warning: Duplicate entry 'user/%/edit/profile' for key 1 query: INSERT INTO menu_router (path, load_functions, to_arg_functions, access_callback, access_arguments, page_callback, page_arguments, fit, number_parts, tab_parent, tab_root, title, title_callback, title_arguments, type, block_callback, description, position, weight, file) VALUES ('user/%/edit/profile', 'a:1:{i:1;a:1:{s:18:\"user_category_load\";a:2:{i:0;s:4:\"%map\";i:1;s:6:\"%index\";}}}', '', 'content_profile_page_access', 'a:2:{i:0;s:7:\"profile\";i:1;i:1;}', 'content_profile_page_edit', 'a:2:{i:0;s:7:\"profile\";i:1;i:1;}', 11, 4, 'user/%/edit', 'user/%', '', 'check_plain', 'a:1:{i:0;s:7:\"Profile\";}', 128, '', '', '', 1, 'modules/node/node.pages.inc') in /Users/Sheila/Sites/drupal-name/includes/menu.inc on line 2423.

Comments

joachim’s picture

Title: Adding a category 'Profile' causes SQL error » Adding a category 'Profile' with core's profile module causes SQL error
Project: Drupal core » Content Profile
Version: 6.13 » 6.x-1.0-beta4
Component: profile.module » Base module

Ah, I think this is a clash with content_profile, not core... reassigning.

To give more context to the initial report:
I created a profile field with core profile module and gave it the category 'Profile'.
This clashes with content_profile module.
content_profile should check and prevent this, perhaps?

fureigh’s picture

For the sake of anyone stumbling across this: Changing the contents of the “Type” field from ‘profile’ to something else (such as ‘content_profile’) should eliminate the conflict.

(Drupal’s squawking because core already has something called ‘profile’ — namely, standard user profiles.)