Support (Entity) Fields in general, not only on nodes

I second this request. I need Employee ID on user profiles and need it to be unique. Thanks for your work on this module! I've found it useful on several projects. :)

+1. I need unique 'display name' text field for users.

Subscribing, I'd need unique adsense id in an adsense revenue sharing site for user profiles, so they can't put in existing adsense id. Thanks if you get around to do it.

It would be nice to have unique fields in comments too. :)

I agree, this seems like the logical progression for this module.

I like this idea, and will be looking into it as time permits. I'd welcome patches from others as well. I think this may be related: #1185904: Evaluate using EntityFieldQuery for content queries

That's a great idea ;)

I guess to implement this, hook_field_attach_validate() is the only way, instead of using hook_node_validate().

@see http://api.drupal.org/api/drupal/includes--common.inc/function/entity_fo...

Using field API functions should ease lot here, @see #1163924: Error with Node Reference Module.

edit: I hope to solve a similar issue (#1212766: promote taxonomy_path/entity_path to full module) soon. There we almost figured out, how to place the configuration form, for the entity bundles...

suscribe, I'd say one of the biggest issues here is how to place the settings form per bundle, as some bundles don't have edit form themselves and afaik there's no straight way to get the admin url for those that have.

sub

subscribe.
Other (duplicate?) requests are:
#1362444: Field collection support
#1416044: in profile field
#1365890: Allow setting unique constraint to fields in relation.

If this feature requires substantial re-writing, shouldn't we #1319396: Join forces with Field Validation ?

I need this for validation of a user textfield that is used for a membership-id and that must be unique... :-) Any timeplans for this case resolution?

My guess is not so soon, as the module as-is relies on hook_node_validate, and there is no such thing as hook_entity_validate.

Maybe it should go down onto the field validation, instead of up to entity validation?

Anyway, +1 for this feature.

I just tested field_validation module today and it works great. If I were you, I would stop re-inventing the wheel... just write a migration module for D6 users to field_validation and discontinue this module here to join forces over there... With this in mind I would be happy to be able to unsubscribe from this case or if we close it and point all users to field_validation... aka WONT FIX

I would be interested in writing a unique_entity module. At present I have a unique comments module - http://drupal.org/project/unique_comments that I've written to address some desire in the community to have unique comments. If people think a unique_entity module would be useful I'd be attentive to discussion about it.

any updates on this? im trying to get profile2 fields validated and nothing seems to work :(

+1

+1

Any progress on unique fields for custom entities, i.e. ECK entities?

If you look for more generic solution please look on my project entity unique https://www.drupal.org/sandbox/nimek/2704251

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks