user relationships

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.