Dev Computer: Windows XP Pro // IIS 5.1 // PHP 4.4.2 Running as CGI
IntegraMOD 1.4.0 // phpBB 2.0.19 // phpBB Security 1.0.3
Live Server: Windows 2003 // IIS 6 // PHP 4.4.2 Running as ISAPI
IntegraMOD 1.4.0 // phpBB 2.0.19 // phpBB Security 1.0.2
When I updated my Dev Computer to phpBB Security 1.0.3, the CGI module for PHP crashed and the ACP Panel returned a CGI Error. I haven't updated my live site for obvious reasons.
Now, when reading through information relating to this, I have tracked the error down to the following location:
File: admin/index.php
Line Number: Around 77
Line Value: $secfile = @file('http://phpbb-tweaks.com/secver.txt');
When I comment out the above line, the module no longer crashes, and I can open my ACP. Only problem is the feature for alerting me to if an update is needed for phpBB Security always says that it can't get the version data.
Now, the obvious work-around would be to comment out the entire section that was added to that file:
- Code: Select all
/*#======================================================================= |#==== Start]; $this_ver = $board_config['phpBBSecurity_version']; if ($newest_ver == $this_ver) $msg .= 'The newest release is <b>'. $newest_ver .'</b>. The version you are using is <b>'. $this_ver .'</b>. So I would have to say you are up to date!'; else $msg .= 'The newest release is <b>'. $newest_ver .'</b>. The version you are using is <b>'. $this_ver .'</b>. So I would have to say you need to upgrade ASAP!'; } $msg .= ' </span>'; $msg .= ' </td>'; $msg .= ' </tr>'; $msg .= ' <tr>'; $msg .= ' <th> </th>'; $msg .= ' </tr>'; $msg .= '</table>'; echo $msg;#====#==== Author: aUsTiN [austin@phpbb-amod.com] [http://phpbb-tweaks.com] = |#==== End: ==== phpBB Security ========================================= | #======================================================================= |*/
The problem with doing that is that the feature goes away. The thing is, the same feature works fine for phpBB and for IntegraMOD, and the update information is displayed as expected. So I know there is a way to get that to work without using @file to the remote site. Unfortunately, my knowledge of PHP is quite limited. That is why I post this issue here. Perhaps one of the PHP gurus here might be able to restructure this code to still work, so that users on Windows based systems won't have this issue.