Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I have one content_profile content type 'profile' and I've set the module to this (I don't have the built-in profile enable). But the 'profile' content type fields are not showing up:
http://i6.photobucket.com/albums/y222/moyoungerman/post/realname-1.png
Here is my content_profile 'profile' content type definition:
http://i6.photobucket.com/albums/y222/moyoungerman/post/realname-2.png
What am I missing?
Comment | File | Size | Author |
---|---|---|---|
#14 | realname.fields.patch | 832 bytes | franz |
#3 | realname.fields.patch | 753 bytes | franz |
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedYeah I'm having this exact problem.
Comment #2
roball CreditAttribution: roball commentedI also ran into the same problem. Found out that it appears when you enable the RealName module before enabling the Content Profile module.
Thus the solution was to completely uninstall RealName and then re-install it again after Content Profile has been enabled.
Comment #3
franzI had this issue because I was reusing the fields from a content type into another. This cause the function realname_content_profile_get_fields to fail. My patch changes the way the fields are get and solves the issue, hopefully
Comment #4
smscotten CreditAttribution: smscotten commentedI had the same issue with reusing fields in multiple content types.
Patch works for me. Haven't discovered any drawbacks to it. Thanks franz!
I hope this can be rolled into the dev version of the module.
Comment #5
franzI think this is RTBC
Comment #6
mikeker CreditAttribution: mikeker commentedJust one more vote to get this committed. Verified on Drupal 6.17, Content Profile 6.x-1.0 and RealName 6.x-1.3
Thanks, franz!
Comment #7
cgmonroe CreditAttribution: cgmonroe commentedThis problem is also related to this http://drupal.org/node/875972 issue.
One main problem with content_profile not working fully with Realname is the array key name missmatch between the realname module and the content profile "plug-in".
Patch to fix this attached to the issue above.
Comment #8
jdwfly CreditAttribution: jdwfly commentedI also had this issue so I applied the patch, but ran into a message that said my content type had no fields. My content profile definitely had some fields so I ended up like #2, I completely uninstalled and then installed the Realname module and everything was fine.
Comment #9
Dave ReidHrm, I haven't been able to replicate this with the current code. I enabled content_profile after enabling realname and it had all the fields on my profile content type available, including fields I added that already existed on other content types.
Comment #10
franzDoes the existing fields already existed in another content type before creation? You could try the opposite direction too, if so. Place some field that exists in your content profile into another content type.
Comment #11
codekarate CreditAttribution: codekarate commentedThe patch in #3 works for me. Thanks.
Comment #12
AaronBaumanSame symptoms as in comments #3 and #4 for me after updating to 1.4
Reopening.
I understand that Dave cannot reproduce this issue.
To me it looks like the patch in #3 simply implements an equally-valid alternative to what is broken for some users.
Since the patch completely solves the problem for those of us who are having it, is there any reason that it should not be applied?
Comment #14
franzRe-rolled
Comment #15
franzComment #16
Dave ReidCan someone else please confirm #14 works for them (it's bad form to RTBC your own issue)?
Comment #17
franzIt is exactly the same patch that's on #3, so in my defence, it was tested by a lot of people before. It was just using old patch format.
Comment #18
John Franklin CreditAttribution: John Franklin commentedSame problem here: I reused the firstname/lastname fields in a couple different profile types and the fields disappeared from Realname's admin page. The patch restored them.
Comment #19
drein CreditAttribution: drein commentedthis patch is great. I didn't see some content_profile field, that was name, surname and other. With the patch, now the module works well!
Please include into the stable release!
Comment #20
joelpittetLet's bump the version to dev.
Comment #21
hass CreditAttribution: hass commentedPlease upgrade to D7/D8.