user relationships

What's the go-to solution for making profiles into nodes in Drupal 7?

The current standard for an enhanced profile module is Profile 2 and it is built on the Entity API. And there is no release of Content Profile for Drupal 7. What's the new way to make profiles into nodes?

In Drupal 6 it was easy to integrate the User Relationships module with Content Profile to create a private profile that other users needed to request to view. Now, I'm at a loss as to how to make this work in Drupal 7 since User Relationships does not provide Entity Access capability, just Node Access.

I would like Users to be able to grant a Proxy relationship to another User so that the recipient will be voting for both parties.

The goal is to use taxonomy to categories Vote Topics (nodes) and for a User to extend/grant a proxy right to another User to vote for them on a topic, a combination of categories, or all topics.

I picture the proxy holder voting on topics normally via votingapi (Up/Down in my case), using Rules to record the event, and a cron process to cast any proxy votes.

Hello,

May I ask some help configuring the following rule?
I've got User A and User B.
User A is a member of an organic group.
User B requests friendship from User A.
When User A applies B's friendship request this rule needs to make User B to be a member of User A's group.

Thank You for Your help!

Kind regards,
Szabolcs

Hello,
Is there a way to (relatively easy) make a user relationship based on the role a user has? For example users which have role A can become friends with everyone who is role A but not with role B. Simple question but hard to find any answers.

Thanks so much!

Just wondering what the latest thoughts are on whether to use the User Relationship module or the FriendList module.

I found this page: http://groups.drupal.org/node/14625

but that made me feel a little like 1) User Relationship is older 2) User Relationship is better 3) Some things may not have been evaluated such as "current community support", supported hooks, etc.

Any thoughts?

using user_relationships.module, a user can set their gallery content-type so that only related users can access to it. but a gallery of content-type like node_gallery and views_gallery are only referenced to their image content-type. (or am i wrong?)

so, this means that even when the author set their gallery to 'only related users', anyone else can still view all the images in the gallery if they know the URL.

is there any good ways to go around about doing this? an 'only related users' gallery should only be viewable to 'only related users'.

Hola a todos, escribo porque estoy investigando como encarar este problema y queria ver si alguien me puede dar una idea.
Estoy usando el modulo user relationship para el cual he creado varios relationships. Lo que necesito es que cuando un usuario se registre sea obligatorio que seleccione una de las relaciones disponibles y al elegirla automaticamente se agrege a la lista de todos los que la han seleccionado.

I posted this in the user relationships support queue, but I thought I'd throw this one out there to the group. Has anyone ever tried to migrate friendlist to user relationships? I guess I could write some sql scripts but if something already exists to do so I'd rather save the time.

There are modules and projects to allow users to give access to various pieces of content, or to create buddylists.

There do not seem to be any solutions for allowing users to place other users who offend them on a "blocked" list.

What would be really nice is a way for users to add people to a blocked list, so that modules could be configured to, for instance:

• prevent users from sending private messages to people who have blocked them
• prevent users from seeing profiles or nodeprofiles of people who have blocked them

Here is a first pass at documenting all of the use cases* to be touched on by the Events system. This list drew from the existing documentation that I could find and tries to be inclusive and exhaustive. I will update as people point out additions, mistakes etc.

• Use Cases are a notation meant to capture meaningful system capability from an end-user perspective. They can be used to document requirements and inform implementors as to the intent behind requirements. There are some standard ways to create and use Use Cases - but personally I feel that they are what you make of them. The image below does not contain Use Cases per se, but the titles of Use Cases. They are meant to describe the scope of the project in a way that is useful to all participants.