Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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.
Comment | File | Size | Author |
---|---|---|---|
#1 | user_relationship_api_0.patch | 743 bytes | gwen |
user_relationship_api.patch | 306 bytes | gwen |
Comments
Comment #1
gwen CreditAttribution: gwen commentedIt's probably not super important since it's a one line change, but I originally attached a standard diff. Attached is the unified diff.
Comment #2
sprsquish CreditAttribution: sprsquish commentedhttp://drupal.org/cvs?commit=80579
Comment #3
(not verified) CreditAttribution: commented