Closed (fixed)
Project:
Content Profile
Version:
6.x-1.0
Component:
User registration module
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
25 Jan 2011 at 00:00 UTC
Updated:
17 Mar 2011 at 20:26 UTC
Jump to comment: Most recent file
Comments
Comment #1
fenstratThis is a content_profile module issue and is documented in the readme on line 220:
Also see #451654: Filefield upload during registration
Comment #2
guntherdevisch commentedHi fenstrat,
Thanks for your reply,
I'll take a look at #451654: Filefield upload validation during registration,
Thanks,
Gunther
Comment #3
guntherdevisch commentedHi fenstrat,
I've looked at the issue above (#451654), but there the filefield upload is displayed. In my case it's not visible.
Do you know why?
Thanks,
Gunther
Comment #4
guntherdevisch commentedSorry but my problem isn't fixed,
Does someone has the same problem or can someone reproduce?
Thanks,
Gunther
Comment #5
fenstratHi Gunther,
I've just tested this and it works fine for me. One thing I did notice was that unless the "Use on Auto Assign Role paths:" was checked for the correct profile on admin/content/node-type/your-profile-name/profile then no cck fields showed up on the registration form, not just filefield fields. Can you see other cck fields on the registration page (e.g. text fields)?
But it appears to be working fine here. I've custom coded filefields on user registration pages a number of times previously, but it now appears you can do it all through point and click with aar and content_profile.
p.s. Make sure you're using aar 6.x-2.0-beta1 as aar by paths is broken in 6.x-1.2.
Comment #6
guntherdevisch commentedHi Saul,
Thanks for your help.
I looked if everything was set right, then watched my registration page, but again the cck field wasn't visible. So i reinstalled the AAR module (6.x-2.0-beta1) and the Content Profile module (6.x-1.x-dev) and tried again, but still the cck field won't show up. I tested it with other cck fields (image, text-field); enabled the content profile (Use this content type as a content profile for users) and then checked the "Use on Auto Assign Role path", but also these profile fields aren't visible on the registration page, strange!
I made some screenshots of my content profile type, AAR settings (assign from-path), registration-form. I also made a screenshot of the Logintoboggan settings page, because i thought that maybe this would be the cause?
Thanks for having a look,
Greets,
Gunther
Comment #7
guntherdevisch commentedHi Saul,
Thanks for your help.
I looked if everything was set right, then watched my registration page, but again the cck field wasn't visible. So i reinstalled the AAR module (6.x-2.0-beta1) and the Content Profile module (6.x-1.x-dev) and tried again, but still the cck field won't show up. I tested it with other cck fields (image, text-field); enabled the content profile (Use this content type as a content profile for users) and then checked the "Use on Auto Assign Role path", but also these profile fields aren't visible on the registration page, strange!
I made some screenshots of my content profile type, AAR settings (assign from-path), registration-form. I also made a screenshot of the Logintoboggan settings page, because i thought that maybe this would be the cause?
Thanks for having a look,
Greets,
Gunther
Comment #8
fenstratSomething went wrong with your screenshot uploads, however I found all of them apart from registration-form.jpg.
Sorry to say I can't see anything that is glaringly wrong. Try stripping it right back, just enable one piece of functionality at a time (certainly disable logintoboggan to begin with).
Given that you cannot see any cck fields on the registration page this is not a filefield specific issue. That's where I'd start testing.
Comment #9
guntherdevisch commentedOkay thanks Saul,
I will have a further look and testing,
I'll keep you updated, when i found the problem,
Thanks for your help and quick reply,
Greets,
Gunther
Comment #10
guntherdevisch commentedHi Saul,
I found the problem, i had to enable the module 'Content Profile User Registration'. Stupid, but i didn't knew it.
Greets,
Gunther
Comment #11
fenstratGlad you found the problem Gunther. I actually think it's a joy when the source of the problem is that simple!