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?

CommentFileSizeAuthor
#14 realname.fields.patch832 bytesfranz
#3 realname.fields.patch753 bytesfranz
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Anonymous’s picture

Yeah I'm having this exact problem.

roball’s picture

Category: support » bug

I 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.

franz’s picture

Status: Active » Needs review
FileSize
753 bytes

I 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

smscotten’s picture

I 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.

franz’s picture

Status: Needs review » Reviewed & tested by the community

I think this is RTBC

mikeker’s picture

Just 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!

cgmonroe’s picture

This 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.

jdwfly’s picture

I 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.

Dave Reid’s picture

Status: Reviewed & tested by the community » Postponed (maintainer needs more info)

Hrm, 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.

franz’s picture

Does 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.

codekarate’s picture

The patch in #3 works for me. Thanks.

AaronBauman’s picture

Version: 6.x-1.3 » 6.x-1.4
Status: Postponed (maintainer needs more info) » Reviewed & tested by the community

Same 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?

Status: Reviewed & tested by the community » Needs work

The last submitted patch, realname.fields.patch, failed testing.

franz’s picture

Status: Needs work » Needs review
FileSize
832 bytes

Re-rolled

franz’s picture

Status: Needs review » Reviewed & tested by the community
Dave Reid’s picture

Status: Reviewed & tested by the community » Needs review

Can someone else please confirm #14 works for them (it's bad form to RTBC your own issue)?

franz’s picture

It 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.

John Franklin’s picture

Status: Needs review » Reviewed & tested by the community

Same 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.

drein’s picture

this 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!

joelpittet’s picture

Version: 6.x-1.4 » 6.x-1.x-dev
Issue summary: View changes

Let's bump the version to dev.

hass’s picture

Status: Reviewed & tested by the community » Closed (outdated)

Please upgrade to D7/D8.