default "user_relationships_content" View doesn't work for one-way relationships

Try this starter view - it works with any relationship type. Be aware that it shows only one direction for one-way relationships.

Is there any way to get this working? Without one-way relationships showing up in the view, what's the purpose of having one-way relationships?

Is there a view that can accomplish this? I recently upgraded to the dev version to test something out that alex.k had fixed (which he did wonderfully!) and I can't get a view to work that shows nodes from users that a user is following (1-way relationship that doesn't require approval). The one provided in comment 2 doesn't do the trick. I can't remember if I ever got it working right before the upgrade or not. I know the module is keeping track correctly of users that user A is following because the block showing them is correct. There just doesn't seem to be a way to pull info about them into views. Thank you.

subscribe

Subscribe. I'm a little bummed out to see that this isn't possible with UR.

Not 100% sure if this solves your problem, but I was able to build a view that does what you're trying to do.

To do so, I had to patch the user_relationship_views.views.inc file.

here's what I did:

1. In your user_relationship directory, find user_relationship_views/user_relationship_views.views.inc file
2. Open it in an editor.
3. Go to line 26.
4. Change the word "requester" to "requestee."
5. Save and close the file.

6. Create a new view.
7. Add a "relationship" to the view: "User Relationship: Requestee user"
8. Add an argument to the view: "User Relationships: Requester user"
9. Under "action to take if argument not present" select "Provide default argument" and under that, select "User ID from logged in user"
10. Set the validator to "user" and choose "allow both numeric and string IDs
11. Save the argument.
12. Set a path for where you want this view to show up using the controls in the views editor.
13. Save the view.
14. Voila!

Here's an export of the view that I made:

$view = new view;
$view->name = 'following';
$view->description = '';
$view->tag = '';
$view->view_php = '';
$view->base_table = 'node';
$view->is_cacheable = FALSE;
$view->api_version = 2;
$view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */
$handler = $view->new_display('default', 'Defaults', 'default');
$handler->override_option('relationships', array(
  'requestee_id' => array(
    'label' => 'requestee',
    'required' => 0,
    'id' => 'requestee_id',
    'table' => 'user_relationships',
    'field' => 'requestee_id',
    'relationship' => 'none',
  ),
));
$handler->override_option('fields', array(
  'title' => array(
    'label' => 'Title',
    'alter' => array(
      'alter_text' => 0,
      'text' => '',
      'make_link' => 0,
      'path' => '',
      'link_class' => '',
      'alt' => '',
      'prefix' => '',
      'suffix' => '',
      'target' => '',
      'help' => '',
      'trim' => 0,
      'max_length' => '',
      'word_boundary' => 1,
      'ellipsis' => 1,
      'strip_tags' => 0,
      'html' => 0,
    ),
    'empty' => '',
    'hide_empty' => 0,
    'empty_zero' => 0,
    'link_to_node' => 0,
    'exclude' => 0,
    'id' => 'title',
    'table' => 'node',
    'field' => 'title',
    'relationship' => 'none',
  ),
));
$handler->override_option('sorts', array(
  'created' => array(
    'order' => 'DESC',
    'granularity' => 'second',
    'id' => 'created',
    'table' => 'node',
    'field' => 'created',
    'override' => array(
      'button' => 'Override',
    ),
    'relationship' => 'none',
  ),
));
$handler->override_option('arguments', array(
  'requester_id' => array(
    'default_action' => 'default',
    'style_plugin' => 'default_summary',
    'style_options' => array(),
    'wildcard' => 'all',
    'wildcard_substitution' => 'All',
    'title' => '',
    'breadcrumb' => '',
    'default_argument_type' => 'current_user',
    'default_argument' => '',
    'validate_type' => 'user',
    'validate_fail' => 'not found',
    'break_phrase' => 0,
    'not' => 0,
    'id' => 'requester_id',
    'table' => 'user_relationships',
    'field' => 'requester_id',
    'validate_user_argument_type' => 'either',
    'validate_user_roles' => array(
      '2' => 0,
    ),
    'relationship' => 'none',
    'default_options_div_prefix' => '',
    'default_argument_user' => 0,
    'default_argument_fixed' => '',
    'default_argument_php' => '',
    'validate_argument_node_type' => array(
      'drigg' => 0,
      'page' => 0,
      'story' => 0,
    ),
    'validate_argument_node_access' => 0,
    'validate_argument_nid_type' => 'nid',
    'validate_argument_vocabulary' => array(
      '1' => 0,
      '2' => 0,
    ),
    'validate_argument_type' => 'tid',
    'validate_argument_transform' => 0,
    'validate_user_restrict_roles' => 0,
    'validate_argument_php' => '',
  ),
));
$handler->override_option('filters', array(
  'status' => array(
    'operator' => '=',
    'value' => '1',
    'group' => '0',
    'exposed' => FALSE,
    'expose' => array(
      'operator' => FALSE,
      'label' => '',
    ),
    'id' => 'status',
    'table' => 'node',
    'field' => 'status',
    'override' => array(
      'button' => 'Override',
    ),
    'relationship' => 'none',
  ),
  'type' => array(
    'operator' => 'in',
    'value' => array(
      'drigg' => 'drigg',
      'blog_post' => 'blog_post',
    ),
    'group' => '0',
    'exposed' => FALSE,
    'expose' => array(
      'operator' => FALSE,
      'label' => '',
    ),
    'id' => 'type',
    'table' => 'node',
    'field' => 'type',
    'override' => array(
      'button' => 'Override',
    ),
    'relationship' => 'none',
  ),
));
$handler->override_option('access', array(
  'type' => 'none',
));
$handler->override_option('cache', array(
  'type' => 'none',
));
$handler->override_option('title', 'From my citizens');
$handler->override_option('use_pager', '1');
$handler->override_option('row_plugin', 'node');
$handler->override_option('row_options', array(
  'relationship' => 'none',
  'build_mode' => 'teaser',
  'links' => 0,
  'comments' => 0,
));
$handler = $view->new_display('page', 'Page', 'page_1');
$handler->override_option('path', 'following');
$handler->override_option('menu', array(
  'type' => 'none',
  'title' => '',
  'description' => '',
  'weight' => 0,
  'name' => 'navigation',
));
$handler->override_option('tab_options', array(
  'type' => 'none',
  'title' => '',
  'description' => '',
  'weight' => 0,
));

Remember you have to patch the file before this will work properly. Good luck!

THANK YOU! enough said!

bflora this works for Fan "(You to Them)" but not the other way around.

I can only speak to my use case. I never thought about wanting to see the latest nodes from people following you. That might be kind of interesting.

Thanks bflora, your fix from #8 worked for me.

Happy to help!

bflora, are there any side affects to changing the file? I posted a bug report here: http://drupal.org/node/806732 since I found the same problem (before finding this). If there are no side affects and it's indeed a bug, we should try to get it committed.

Hi @cerup, I think there would be a side affect. I had the same problem. The code change in #4 fixes this issue, but also breaks other views.

Basically, for some use cases you want to join on the requester_id field and sometimes on the requestee_id field.

I therefore added another relationship 'User relationships reversed' which this change in it. (see screen shot)

I've only just started using the user_relationship module and I'm no views expert, so I think this patch needs some work. For instance, this patch doubles the number of possible arguments and filters.. but I'm sure some of these combinations don't make any sense.

Anyway, here's the patch.

I have tried the solution #8 but no luck. Plus you have to hack the UR module! Also - I don't want this to work just for the currently logged in user. I need it to be based on the user you(anyone) is viewing. Meaning, if I goto /user/4/following I can see a list of content of the user that user/4 is following.

This seems like a pretty vital feature of the UR module. Being able to view content from the users you follow is ALL i need this module for.
Are there any other updates or any progress on this?

thanks!
-=b=-

I can confirm there is something not working correctly here.

Here are the steps I followed to reproduce this bug locally that can be used for testing any patches or new views designed to fix this.

• Create a few test users
• have a your user account follow all of them (1 way relationship no approvals).
• Jot down the usernames of everyone that you just followed.
• Create a brand new node view
• add a title field user name field and a User:name filter
• Add the usernames of all the users you followed to the filter.

This will give you the correct listing of all nodes created by these users.

Compare that list to the list at user/my user id/associates and you get a very different list.

Closed #806732: user_relationships_content view is broken as a duplicate, but there is some useful information there about this issue.

Has there been any head way regarding this

Really?! No one has any idea?
I have tried so many other options but cant seem to get what I need. I wish I knew enough to write my own modules but don't have the chops yet.

Here is exactly what I need - if anyone knows of how to do this with UR OR with any other module you would get a gold star!

1) One way relationship with any user on the site (become a fan)
2) then a view of the content that a user is a fan of. This is not just MY fan's content (that is handled well in the friendlist activity feed) I need to be able to go to anyones user page and see a list of content from user of which THEY are a fan. ie. I'm user 3 but I go to user/4/activity and see content from user 6, 8, and 2 because those are the users that user 4 is a fan of.

If UR was not BROKEN! It would be the perfect solution. But I don't know enough to fix it to display the content from a one-way relationship.
ANY ANY ANY help would be great... thanks

-=b=-

I posted how to do it up in comment #8. Follow the directions.

It seems it is necessary to modify the default relationship (as in views relationship) to get this type of view working properly (see: Comment #8). This gives you essentially the same result as modifying the query directly to use the requestee id at the correct time (see: #806732: user_relationships_content view is broken)

Should we create a new UR views relationship specifically for one way relationships (see: Comment #15), or is there a way to modify the existing relationship and still allow current views to work properly (including custom views not provided by UR)? The major downside to creating a new relationship is that it becomes even more confusing than it already is when trying to decide which relationship to use.

To get this committed we'll need a patch that includes a working one way view as well as any necessary modifications to the views relationships. That patch will need to be tested very thoroughly especially on custom views using the current relationships.

Ideally any patch would also fix the current content view to not show incorrect content for 1 way relationships but that is not completely necessary if the new view is documented well.

As I said before I tried #8 with no luck. I modified the code and imported the view provided
created the one-way relationship
then made some connections
going to the page link did not show anything...
and like mrf said - it breaks the rest of the module
Seems like this is a key feature for UR - would be great if this could get patched!
-=b=-

suscribe

Has anyone gotten this to work? I tried #8, but as others have mentioned it doesn't work (not sure if the file has changed since only "line 26" is mentioned).
There's been enough ongoing desire for this that it seems worthy of attention. If it would help out, I would be more than willing to offer a small bounty and any help I could offer in development toward a solution.

Marked #504926: How to build View of User PLUS Users Friends' content, #627928: Create a view of my relationships' content, and #1020882: Join error on view filter? as duplicates of this issue.

Confirmed that the view is still not showing the expected results in 7.x

Moving this to 7.x, 6.x is in maintenance mode and it would be great to solve the problem in 7 where there is a little more flexibility to include any necessary changes and then backport the solution.

In my case its not working even for two way relationships

Subscribing!

Really need View for one-way relashionships.

Closed #671734: Create a view of my relationship's nodes? as a duplicate but have a look at that issue for a view export that purportedly solves this problem.

We have a large patch in the queue to help solve a major issue with one-way relationships. Please review if you have a chance so we can move forward with some of these related issues.
#651502: clarify reciprocal & one-way relationships

Hi all. I've get to this issue with the same problem as the other ones. If I've understood all the thread, there's no way right now to do:

1. Create a one-way relationship.
2. Create a view which nodes are filtered to show just them which users are related to the logged user.

In other words, Twitter.

I works for me if I use a reciprocal relationship but I need a one-way one.

There's no way to do this?
Is there any plan to solve this?
Can I do anything to help?

Thanks in advance!

Hi,

Please apply the attached patch,it may be helpful to you.

Regards,
Hardik