The sql in function user_relationships_request_relationship() is:

    " SELECT 1 
      FROM {user_relationships} 
      WHERE rtid = %d
        AND ((requester_id = %d AND requestee_id = %d) 
          OR (is_oneway = 0 AND requestee_id = %d AND requester_id = %d)
        )", 

There is no is_oneway column in the user_relationships table. This function is used by core things such as the relationship request page, so many things are broken (e.g. the relationship request page times out).

Looking at CVS logs, it looks like a sql correction in revision 1.6 of user_relationships_api.inc took away the join against user_relationship_types, which has the is_oneway column. A patch with modified sql is attached.

CommentFileSizeAuthor
#1 user_relationship_api_0.patch743 bytesgwen
user_relationship_api.patch306 bytesgwen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

gwen’s picture

FileSize
743 bytes

It's probably not super important since it's a one line change, but I originally attached a standard diff. Attached is the unified diff.

sprsquish’s picture

Status: Needs review » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)