Closed (duplicate)
Project:
Content Profile
Version:
6.x-1.0-beta4
Component:
User registration module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Jun 2009 at 15:28 UTC
Updated:
29 Jun 2011 at 09:28 UTC
Jump to comment: Most recent file
Comments
Comment #1
haiou commentedComment #2
haiou commentedanyone has any clue on this?
how to debug this?
Comment #3
haiou commentedconfiguration problem, not a bug
resolved by uncheck "Use this content type as a content profile for users" in page
admin-> content mgmt -> content type -> page/story etc. -> edit, at the bottom click "content profile"
Comment #4
arnaudfischer commentedI have the same "This user has already a content profile " issue when either i) adding a user through [User MGT > Users > Add User] or ii) creating a new Content Profile. I am using the Content Profile as a node to beef up user profiles with CCK fields. If I uncheck "Content Profile" I can then go and add a user but I mess up the user profile so I then have to go back and recheck the "Content Profile" after adding a user. I am most probably doing something wrong ... new to Drupal and no coding experience.
What am I doing wrong? Thanks for any guidance.
Comment #5
jrabeemer commentedI get this error: "This user already has a content profile of this type. You can only create one profile per user."
The new user I am creating is new and *not* a duplicate of an existing user.
I am creating a new user with my "scholar" content type which is the only one checked off for use with content_profile module.
I have this feature checked on "Use on administrative user creation form" which shows all my extra content profile fields in my user add form @ /admin/user/user/create If I check off "Use on administrative user creation form", this error goes away, however I have to manually go to the user's profile node and fill in the data missed.
Also, when using an anonymous user and using the registration form @ /user/register with this feature checked on "Use on Registration" The form works as expected!
Comment #6
jrabeemer commentedRebasing..
Comment #7
sammy-node commentedI believe this is pretty straight forward - good module, but it only works in one direction and everyone else on this thread is coming in from the other direction.
e.g. this is where I'm falling over
I want to create "Contacts" (custom CCK defined node) of whom some will have logins to the site (Type A) and some won't (Type B). I could add all the Contacts as Users and set some of them not to have access - BUT you need to have an email address to create a user and some of my Type B contacts won't have always provided them. This means I CAN'T create them as a Drupal User.
Therefore - I need to create them as a Contact (the custom CCK defined node) - HOWEVER - the module won't work in this direction and this is where the error messages on this thread come in.
Solution??
I'm not an architect or coder so I can't suggest a detailed fix, but maybe a workflow solution could include something like >>
Step 1: Create a new "Contact" (CCK node type)
Step 2: Fill in the custom CCK Fields
Step 3: Have user fields also show in the Create Node form and MAKE THEM OPTIONAL
Outcome - if the User Values are entered, then a site user is created that is linked to the contact node, but if no user is created the Contact data is still valid as an unattached node.
Comment #8
vett commentedI'm having the same problem.
Only one content type (profile) is selected to use as a profile content type. I'm trying to log in as admin and edit a user's profile (user/103/profile/profile), and then I get the error.
Comment #9
suydam commentedThe module does duplicate checking by seeking another node with the same NAME. That seems like the wrong way to handle it (to me).
My node names != username for content profile so if I get a user with the same name as someone else (e.g. John Smith) then content_profile complains about duplicates.
The workaround I'm using is not a best-practices workaround by ANY MEANS, but I've included it just in case it helps you.
It's working fine for me but be warned this isn't anything fancy... just disabling the node-name duplicate check when node-name is empty.
Comment #10
Bilmar commentedsubscribing
Comment #11
wOOge commentedI have the same problem — seems related to the formfilter module.
If I enable any form filtering on the content type that I've chosen for my user profiles, it throws back this error upon updating the node.
Comment #12
wilgrace commentedMomendo, this is exactly the issue I'm having - did you find a fix for it? The other messages in this thread seem to be talking about something else, I specifically get the error message when an administrator creates a new user with the Profile fields in the user creation form.
Any help appreciated
Comment #13
hansrossel commentedDuplicate of #313135: Author is anonymous on admin create new user
Comment #14
sinasalek commentedSame problem here
Comment #15
boabjohn commentedYep: Confirming...
D6.16
Content Profile 6.x-1.0-beta4
Form Filter 6.x-1.0
Turning Form Filter off avoids the error. Not sure where the conflict is: these two modules have played very niccely together in the past.
Will upgrade to dev/downgrade and experiment over the weekend unless someboody has a fix?
(How to cross-post this to the FormFilter folks?)
Comment #16
paskainos commentedsubscribing
Comment #17
jozzhart commentedI'm getting the same problem....... If form filter UI module is enabled, I get "This user already has a content profile of this type. You can only create one profile per user."
Turn it off and it's fine......
Comment #18
scotwith1tI can second that the formfilter module is the culprit here. I turned off everything the FormFilter UI was doing and it still was giving me this error, actually disable the module and the error goes away. Luckily, formfilter isn't critical to my site, so I'll just leave it off :) Would love to see a solution to this though.
Comment #19
anaperes commentedHello
I have the same problem here but I don't have FormFilter UI module.
I will describe my problem:
I'm the administrator of my website and normally is me who create a new profile for a new user and when I type 'admin' on 'Authoring information' I get "This user has already a content profile of this type. You can only create one profile per user." and I can't save that profile
Drupal seems to be confused and instead of reading authoring information he is reading user name... maybe?
My website is online for a couple of years and only a few months ago I get this error.
Any suggestion?
I'm using drupal 6.2.
Content Profile 6x-1.0
and Compact Forms 6x-1.3
Thank you.
Comment #20
lekvarnik commentedI have the same problem as anapres. Anybody who solved this problem?