Referenced Entities (Field Collections, References) need a way to integrate with Profile2 Privacy (hooks/alters)

While the Field Collection module might be somewhat popular, I currently have no plans to integrate Profile2 Privacy with it.

As I understand it, Field Collection simply creates an entity that is a group of fields, then one entity (user, node, profile2) can reference the Field Collection entity in order to receive all of the fields in the collection. Can you explain how Field Collection significantly extends profiles beyond what core fields are able to provide? if there's a compelling case to add the integration, especially to do something that you can't do with core and profile2, then I may consider adding it.

Thanks for the info. After doing more research on Field Collections, I don't think it's within the scope of this project to provide direct support for Field Collections... especially since this project does not require field collections and works without it. However, since field collections are somewhat similar to other referenceable entities, I think I could provide hooks and/or alters so that another module could bridge the gap and provide access to field collections or referenced entities.

I'll add some integration points when I get some time to work on this next month.

Sorry, I haven't had time to work on this and will not be able to in the immediate future.

Since you're relatively new to the Drupal community, you should understand a few things:

1. Drupal is open source and community driven, so if this is important to you and you have the programming skills, you're encouraged to write the changes yourself and submit a patch for review.
2. Nearly all contributors have full-time jobs and contributions are done in our spare time, which is often very limited. If a problem is urgent or a high priority for you and you are not able to add the functionality yourself, you could offer to pay for support (either to the project maintainer or another Drupal support provider (http://drupal.org/drupal-services)
3. Continuously posting "waiting" does nothing to speed the desired work and is more annoying than it is helpful... which in turn makes project maintainers less inclined to solve the problem. By creating or posting to an issue, you are automatically subscribed and will receive an email when any other posts are made or the issue status changes.

So in other words, if you can't contribute code or pay for code to be contributed, then just be patient.

Checking in on the status of addition of any hooks or alters for the field collections. Just being able to have those hooks, would extend the functionality and power of this module greatly.

Cheers
Murias