We just installed the following modules on a Drupal 5.1 server:

nf_registration_mod
http://drupal.org/project/nf_registration_mod

nodeprofile
http://drupal.org/project/nodeprofile

nodefamily
http://drupal.org/project/nodefamily

subform_element
http://drupal.org/project/subform_element

pageroute
http://drupal.org/project/pageroute

We enabled those all at one time, and got the following errors in a red box:

    * warning: Invalid argument supplied for foreach() in /home2/recovery/christians-in-recovery-www/modules/nf_registration_mod/nf_registration_mod.module on line 1241.
    * warning: Invalid argument supplied for foreach() in /home2/recovery/christians-in-recovery-www/modules/nf_registration_mod/nf_registration_mod.module on line 1241.

The site's status report is as follows:

Drupal	5.1
Configuration file	Protected
Cron maintenance tasks	Last run 16 min ago
You can run cron manually.
Database schema	Up to date
File system	Writable (private download method)
GD library	bundled (2.0.28 compatible)
MySQL database	4.0.26
PHP	4.4.4
Unicode library	PHP Mbstring Extension
Web server	Apache/1.3.35 (Unix) ApacheJServ/1.1.2 PHP/4.4.4 FrontPage/5.0.2.2635 Rewrit/1.1a

(shrug) ????

TIA!
Michael

Comments

rconstantine’s picture

rconstantine commented
Category: bug » support

Right. You didn't follow the readme. Not to be short with you, but read it and try again. If you still have problems, I'll be happy to help.

mdlueck’s picture

mdlueck commented
Status: Active » Closed (fixed)

Indeed, after four hours of setting up the various modules, we were able to enable this module successfully. I am going ahead an closing this ticket.

rconstantine’s picture

rconstantine commented

Glad to hear you got it. It is a long process to setup the content types and pageroutes first, but since this module depends on data being there that was created by them, I don't see a ready way to install this module without it. That said, the line of code you pointed to was simply a function call to one of the required modules and I think you only had a problem because the order in which they were activated had this module ahead of the one it needed and so when Drupal parsed the file and found functions it didn't know about, it freaked out. I'm pretty sure you could have installed this module right after installing the other two.

Anyway, good luck.