Re: bbPress 1.0-alpha-2 released
Hi,
Installed a zip package of alpha 2 and it went OK and as I couldn’t quite get the logins to work for WP and bbP and tried installing it again.
I saw a few messages about install packages not being complete so I downloaded this second one.
Now when I try to install it, on the final screen it give the following PHP error – but the install seems OK.
Warning: chmod() [function.chmod]: Operation not permitted in /home/1295/htdocs/www.example.com/public_html/forums/bb-admin/class-install.php on line 1021
Warning: Cannot modify header information – headers already sent by (output started at /home/1295/htdocs/www.example.com/public_html/forums/bb-admin/class-install.php:1021) in /home/1295/htdocs/www.example.com/public_html/forums/bb-includes/functions.php on line 2902
I tried a few times but got the same thing, then I comared my first and second packagas and saw that bbpress/bb-admin/class-install.php is very slightl different from line 264
The file in the first package has 2 if statements and the second has 1 if statement as follows:
class-install.php from package 1:
if (!defined(‘BB_INC’)) {
// Define BB_INC
// Tell us to load includes because bb-settings.
php was not loaded
// bb-settings.php is generally not loaded on
steps -1, 0 and 1 but
// there are exceptions, so this is safer than
just reading the step
$this->load_includes = true;
define(‘BB_INC’, ‘bb-includes/’);
}
if (!defined(‘BACKPRESS_PATH’)) {
define(‘BACKPRESS_PATH’, BB_PATH . BB_INC . ‘
backpress/’);
}
class-install.php from package 2:
if (!defined(‘BACKPRESS_PATH’)) {
// Define BACKPRESS_PATH
// Tell us to load includes because bb-settings.
php was not loaded
// bb-settings.php is generally not loaded on
steps -1, 0 and 1 but
// there are exceptions, so this is safer than
just reading the step
$this->load_includes = true;
define(‘BACKPRESS_PATH’, BB_PATH . BB_INC . ‘
backpress/’);
}
But the weird thing is that when I put back the first class-install.php I still get the error. I’m not too fussed as the install goes OK but it could be quite off putting if users get this PHP error.