Hi guys. I'm trying to install BBPress on a subdomain. At first I thought it was due to the site having SSL so I removed that, deleted the subdomain and started again. However the same issue is presenting itself (see below output from the script installation).
Downloading http://bbpress.trac.wordpress.org/changeset/4522/tags/1.2?old_path=%2F&format=zip (348 bytes) ..
Found http://scripts.virtualmin.com:80/bbpress-1.2.zip in cache ..
Downloading http://backpress.trac.wordpress.org/changeset/354/tags/backpress-1.2-bbpress?old_path=%2F&format=zip (369 bytes) ..
Found http://scripts.virtualmin.com:80/backpress-1.2.zip in cache ..
Found http://scripts.virtualmin.com:80/pomo.zip in cache ..
Configuring webserver PHP settings ..
Applying web server configuration ..
Now installing bbPress version 1.2 ..
bbPress database setup failed : HTTP/1.1 500 Internal Server Error
More information on using this script can be found at http://bbpress.org/.
.. installation was only partially complete.
Re-loading Webmin ..
Applying web server configuration ..
Funny thing is the database is actually created yet when I try and run the installer nothing happens. Nothing rendered on the page subdomain.domain/bb-admin/install.php. Any ideas? The error log shows two lines [Fri Mar 31 10:23:56.408386 2017] [fcgid:warn] [pid 35988] [client xxx.xxx.xxx.xx:60326] mod_fcgid: stderr: PHP Parse error: syntax error, unexpected 'new' (T_NEW) in /home/domain/domains/subdomain.domain.com.au/public_html/bb-admin/includes/class.bb-install.php on line 1283. The other line is the same except it has my ip address.
Installing Wordpress in the same directory doesn't cause an issue. Maybe there is a problem with the script.
Submitted by andreychek on Thu, 03/30/2017 - 22:18 Comment #1
Howdy -- hmm, it actually looks like our script for that is fairly old... I think that's at least 5 years old.
Jamie, rather than updating that to the newest bbPress, would we be better off allowing that to be installed using WordPress instead?
WordPress has gotten really good at managing WordPress plugins, and may be able to do that better than we could
Submitted by JamieCameron on Fri, 03/31/2017 - 10:26 Comment #2
bbPress should still work. Are you trying to install it into a sub-domain, or a sub-directory?
Also, on which Linux distribution and version.
Submitted by andreychek on Fri, 03/31/2017 - 10:49 Comment #3
Jamie, the error he's receiving is a PHP syntax error... I'm figuring that this bbPress script is old enough that it's just not working on modern PHP versions.
He's using PHP7 on Ubuntu 16.04 -- it looks like the bbPress version we're shipping is from at least 2012.
Submitted by JamieCameron on Sat, 04/01/2017 - 00:47 Comment #4
That may be it - if you can select a different PHP version (like 5 instead of 7), it would be worth a try.
Submitted by aremdee on Sun, 04/23/2017 - 19:15 Pro Licensee Comment #5
Tried installing in a subdomain on an Ubuntu 16LTS server using PHP7. I tend to agree with Eric in that BBPress is now a plugin for Wordpress, not a stand alone install. I'm figuring that it is best to leave this one given it's age. Thanks for the help anyway.
Submitted by andreychek on Sun, 04/23/2017 - 21:04 Comment #6
aremdee, is there a more modern WordPress plugin for that which can be installed using WordPress itself?
For example, I'm seeing this here:
That looks like it's being maintained.
Would that perhaps do what you're after?
Submitted by aremdee on Sun, 04/23/2017 - 22:06 Pro Licensee Comment #7
Yep that's the only way now I believe. It's no biggy, just saw it in the list of available scripts and thought I would play with it to see if it was what I was after for a particular domain. As it wouldn't install that's when I posted the initial issue (not realising it was failing because of age - bit like us all really :). I just reckon you need to get rid of the one available though as it is so old. It may be riddled with security holes by now.
And you can mark this as closed now if you like.
Submitted by JamieCameron on Mon, 04/24/2017 - 18:59 Comment #8
Did you manage to confirm that PHP 7 is the cause? Because we could add a test to limit this script to PHP 5.