The module underwent a major rewrite and simplification for Drupal 7 and now depends on the core token API and the Token module for its functionality. See http://drupal.org/node/1068734
This (appears) to allow any field to be used via token support.
As of Name field module 7.x, mimicking the functionality of the Real Name module can be done under the field instance setting without needing to use this module for most use cases.
Original request
I was trying to integrate the Name module (field module for CCK) with the RealName module, but I can't get it to work.
First, I tried adding a name field to a Content Profile (I used the Advanced Profile Kit), but it won't show up under the fields tab when content profile is selected under the modules tab.
Then I tried bypassing the content profiles and going straight to the Name Module by following
http://drupal.org/node/329662. The radio button for the name module appears under the modules tab, but under the fields tab, the fields are all brought in from Content Profile. What do I need to do?
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 948672_realname_name_module_support.patch | 847 bytes | guypaddock |
| #7 | 948672_realname_name_module_support.patch | 847 bytes | guypaddock |
Comments
Comment #1
nancydruThe Name module should not show under the RealName modules tab. CCK field modules cannot be used on their own; they must be used within a content type. Name would have to be used to add a name field to a Content Profile node type and then RealName set to use Content Profile.
If that doesn't get you going, I will have to try to figure out how to set up a site to test on; I don't currently have any test sites using Content Profile.
I do not have any sites using APK. If there is an issue using RealName with APK, you will have to open an issue in that module's queue.
Comment #2
alex8810 commentedUnder the fields tab, it says this:
Then below that is a list of fields displayed on the content profiles, but Name does not appear.
Comment #3
alex8810 commentedIt would appear that RealName only pulls from fields that are of the 'text' type. The name module creates fields of the 'name' type. Does that seem like it might be the cause?
Comment #4
nancydruThat would certainly explain it. I didn't know that "name" was a valid type. When I get the time to look at it, I may be able to fix that.
Comment #5
alex8810 commentedComment #6
guypaddock commentedIt looks like this is still the case... any chance of getting this support?
Comment #7
guypaddock commentedThis was much easier to add than I anticipated... here's a patch for dev.
Comment #8
guypaddock commentedSame patch... setting to "needs review".
Comment #9
alan d. commentedFor Drupal 7+, adding a name field to the user entity using the "Name Field" module (a bit confusing sorry) will provide an option to set the user name.
The approach is similar to RealName, so it is a race by system weight to what module will set the name, but after that point they will both work in harmony.
Comment #10
hass commentedComment #11
alan d. commented