Invalid argument supplied nukesentinel.php on line 1109

New Member Joined: Apr 24, 2006 Posts: 4

After installing everything, I get this warning that a Invalid argument supplied for foreach() in /usr/home/includes/nukesentinel.php on line 1110. There was one other error on line 1128 but fixed that by adding a "$" in front of fwrite. Can anyone come up with a solution for this issue.

Posted: Tue Jul 25, 2006 10:31 pm

That would turn fwrite into a variable and disable the function of fwrite, Which I believe in sentinel is to write to the .htaccess.

Something all should remember is that a host can disable any function within php they like.

I believe your host may have disabled fwrite or you did not chmod the .htaccess correctly.

Posted: Wed Jul 26, 2006 6:09 pm

ok ...I took out the $ in front of fwrite and it went back to error in line 1128. I chmod everything correctly. Think if I just reinstall instead of updating it will resolve this issue? and place the original .htaccess during initial install?

Posted: Wed Jul 26, 2006 6:13 pm

Ask your host if fwrite is allowed. The host using safe mode can disable preset functions but also they can disable ANY function

Posted: Wed Jul 26, 2006 7:27 pm

thanks ...I'll check with them, more likely they are for now due to server move to different location.

Posted: Sun Aug 13, 2006 8:25 am

Is this a warning or a fatal error? That block starts out

Code:




  foreach($floodarray as $floodwrite){


    if(!strstr($floodwrite, $floodarray[$floodcount-10]))


    fputs($floodopen, $floodwrite);


  }

For some reason, $floodarray is not being read as an array here

Code:




$floodarray = file($ab_config['ftaccess_path']);

So either.. the ftaccess file doesn't exist, the file function is not allowed to access it, or the file contents is not an array.

On a seperate issue, fputs may not be allowed by your server. Putting an @ symbol in front of fputs (@fputs) may suppress the error... but of course, the functionality of ftaccess file won't work.

Posted: Sun Aug 13, 2006 2:43 pm

Thanks for the input, I got it corrected by suppressing with "@"