I installed the the module and when I go the 'Add Relationship Type' tab I get the following error serveral times (once, I believe, for each content type):

warning: in_array(): Wrong datatype for second argument in /home/mysite/public_html/drupal/modules/user_related_content/user_related_content.module on line 532.

line 532 follows:
if (in_array($type, $edit['content_types'])) {
this line is in the function (starting on line 521):
_user_related_content_admin_relationship_type_form($edit = array())

this function is called twice in the module: on lines 426 and 474

I tried several searches on the Drupal Site to see if anyone else has encountered this problem. I am very new to Drupal.

Everything to my best knowledge is 4.6.x My host is opensourcehost.com, php version is 4.3.11 database is MySQL version 4.0.25-standard

Can anyone help, I would really appreciate it.

Comments

ejort’s picture

Hi,

Thanks for the report. This modules fairly new so it hasn't had a heap of testing outside of my own work. I'll look into this in the next day or two and hopefully get a fix soon.

Cheers,
Eric

ejort’s picture

OK, I realised pretty quickly what the error was. All fixed in the 4.6 version of the module now (may take a while to get onto the project page though).

Cheers,
Eric

ejort’s picture

Status: Active » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)
chaos21in’s picture

Title: warning: in_array(): Error on line 532 » warning: in_array(): Error on line 522
Version: » master
Priority: Normal » Critical
Status: Closed (fixed) » Needs review

I installed drupal 4.6.5 and activated this module...i took the recent version from cvs...in admin/user_related_content/add the warning message is comming...

warning: in_array(): Wrong datatype for second argument in drupal/modules/user_related_content/user_related_content.module on line 522.

can anybody please correct it..

--rafi

ejort’s picture

Priority: Critical » Normal
Status: Needs review » Active

Changing the status. It's causing a warning message, so it's not a critical bug, and there's no patch attached to this issue.

ejort’s picture

Status: Active » Fixed

Just committed a fix for this.

Anonymous’s picture

Status: Fixed » Closed (fixed)