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.
There is a straightforward error in the _user_relationship_process_query_argument() function after the preg_match for a relative operator such as < or >=. The value is got from $matches[3] though inspection of the pattern shows that $matches[2] must be meant. Patch attached.
Comments
Comment #1
BerdirSorry for pinging the participants.
Now that Drupal 7 is out, there is no support for Drupal 5 and the corresponding modules anymore. Therefore, I'm closing all old issues which are still open.
I suggest you upgrade to Drupal 6 or 7 and figure out if you're feature is still needed or the bug still exists and open a new issue in that case.
Comment #2
greenmachine CreditAttribution: greenmachine commentedI can confirm that the same bug is present in the 6.x-1.0 version of the module.
View the file here: http://drupalcode.org/viewvc/drupal/contributions/modules/user_relations...
Line 183 sets the value to $matches[3] when (at least for created_at) it should be $matches[2]
Comment #3
mrf CreditAttribution: mrf commentedTagging for a closer look.
Comment #4
mrf CreditAttribution: mrf commentedFixed in latest 6.x dev
http://drupalcode.org/project/user_relationships.git/commit/08e15a2
Moving to 7 in case its still present there.
Comment #5
mrf CreditAttribution: mrf commentedWell crap this is a duplicate of #985672: user_relationships_load not handling date-based parameters correctly which already had a patch, oh well guess its good to confirm from two different perspectives that we had the right fix...