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.

Comments

lemuelsantos’s picture

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

webankit’s picture

+1

Syph’s picture

+1

rurri’s picture

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

MHLut’s picture

+1

minoroffense’s picture

Status: Active » Needs review

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

rurri’s picture

Not 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

rurri’s picture

StatusFileSize
new4.71 KB

Attached is a new patch.

  • This patch does the following:
  • Adds a new checkbox to choose whether to use the Profile module or fields
  • Makes Profile module no longer required
  • If Profile module is not found, will not allow use of Profile fields (only fields directly on the account)
  • Adds an update_7101 that sets all currently installed sites to default to using Profile fields
  • Future installs default to Account Fields (not using Profile module)
rurri’s picture

Category: task » feature
Priority: Normal » Major
sanduhrs’s picture

Title: Use 'Account' fields » Add support for user fields
Version: 7.x-1.5 » 7.x-1.x-dev
Status: Needs review » Reviewed & tested by the community
StatusFileSize
new4.76 KB

Rerolling against latest dev.

sanduhrs’s picture

Priority: Major » Normal
Status: Reviewed & tested by the community » Fixed

Commited to 7.x-1.x.
Thanks.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.