The 7.x module requires using profile, which is in core but is legacy. It doesn't work as an entity- you can only add a small number of field types. I'd like to use this module with Accounts fields (admin/config/people/accounts/fields), which other modules are developed for, and where you can use all the new D7 entity benefits.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | vcard-1049174-10.patch | 4.76 KB | sanduhrs |
| #8 | vcard-1049174-8.patch | 4.71 KB | rurri |
| #4 | vcard-1049174-accountfields-insteadof-profilefields.patch | 2.16 KB | rurri |
Comments
Comment #1
lemuelsantos commentedTotally agreed.... if there is no way of adding fields provided by the NEW FIELD API this module is USELESS for Drupal 7... since the core profile module is DEPRECATED on D7 and recommended not using it at all... please work on having this module really working on D7.
Comment #2
webankit commented+1
Comment #3
Syph commented+1
Comment #4
rurri commentedThe attached patch REPLACES profile fields with the fields on the account.
This patch will NOT support legacy systems using the profile module, so will probably need some work before added to this module, unless this module no longer wants to support the profile fields, but guessing this is not the case.
In any case, if you are a new setup, and not using the profile fields this patch should work for you.
Comment #5
MHLut commented+1
Comment #6
minoroffense commentedI'm all for this as well.
However, maybe this belongs as a sub-module of vcard so it doesn't completely break the existing functionality.
Comment #7
rurri commentedNot Sure it is worth a su-module with only 200 installs currently, but definitely seems weird that we have to use profiles instead of standard fields.
I would suggest either a major version change that keys off of fields on accounts instead of profile fields, or adding a settings option in vcard to choose which fields to use.
Or perhaps automatically use Profile fields if the profile module exists, otherwise use account fields.
Any chance of getting any of these methods above committed if a patch is made? This is kindof blocking me on another module: http://drupal.org/project/diaspora
Comment #8
rurri commentedAttached is a new patch.
Comment #9
rurri commentedComment #10
sanduhrsRerolling against latest dev.
Comment #11
sanduhrsCommited to 7.x-1.x.
Thanks.