Closed (fixed)
Project:
User Related Content
Version:
4.6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Jan 2006 at 09:09 UTC
Updated:
5 Feb 2006 at 04:30 UTC
Whenever a user accesses the user-related content in the user tab, this shows up in the log:
mysql_real_escape_string() expects parameter 1 to be string, array given in /home/[account]/public_html/includes/database.mysql.inc on line 239.
The module seems to be working, although the relationship only shows up on the user side -- for other users, there is no indication on the node of the relationship. (The related user does have a "remove..." link.) I've triple-checked permissions on this part.
If the error is causing a functional error, I suppose this would be serious.
(Drupal 4.6.5. - user_related_content.module,v 1.3.2.3 2005/09/07 15:08:16)
Comments
Comment #1
laura s commentedChanging to critical because, between this error and/or the error reported in http://drupal.org/node/44646, this module does not store any relationship info. In other words, it does not function properly. When you're working with it, the user related content links seem to be created. But they disappear between sessions.
Further info (perhaps related): In phpMyAdmin, I am given this error warning for the mysql table user_related_content_relationship_type_content_types:
PRIMARY and INDEX keys should not both be set for column `rtid`Hope this helps. (Cross-posting this info on http://drupal.org/node/44646. My apologies if these to issues turn out to be two sides of the same bug.)
Comment #2
ejort commentedUnfortunately work has taken me away from dabbling with PHP lately so I haven't been able to follow up this (and some other) issues. I'm not seeing any of these issues on my production site, but I'll try to reproduce the problem over the weekend and see what I can find.
Cheers,
Eric
Comment #3
laura s commentedOne other piece of information: This error is happening on a site currently running without clean URLs. FWIW.... Thanks!
Comment #4
ejort commentedThis should be fixed in the 4.6 version of this module now.
Cheers,
Eric
Comment #5
laura s commentedConfirmed fixed. Thank you!
Comment #6
(not verified) commented