[Rukario]

Thanks Chouf1, but it didn’t work even without plugins. Oh and I didn’t know about whitespace errors! However, I checked through it all and there was no space, only a

ini_set( ‘display_errors’, 1 );

at 265 of load.php.

I refreshed the page and now it gives me many “Call-time pass-by-reference has been deprecated” warnings on countless files, but here’s an example of the two types:

Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of apply_filters(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /www/zxq.net/s/e/m/semperfortis/htdocs/wp-content/plugins/buddypress/bp-core.php on line 562

Warning: Call-time pass-by-reference has been deprecated in /www/zxq.net/s/e/m/semperfortis/htdocs/wp-content/plugins/buddypress/bp-core/bp-core-classes.php on line 228

Do I really have to go through every single file and make the fixes or is there an easier way to go about this? Also, the header errors are nowhere to be found now, only when I first startup the BP plugin.

[Rukario]

Okay, I finally got the debug running. Here are the errors.

Warning: ini_set() has been disabled for security reasons in /www/zxq.net/s/e/m/semperfortis/htdocs/wp-includes/load.php on line 265

Warning: Cannot modify header information – headers already sent by (output started at /www/zxq.net/s/e/m/semperfortis/htdocs/wp-includes/load.php:265) in /www/zxq.net/s/e/m/semperfortis/htdocs/wp-includes/pluggable.php on line 890

Warning: Cannot modify header information – headers already sent by (output started at /www/zxq.net/s/e/m/semperfortis/htdocs/wp-includes/load.php:265) in /www/zxq.net/s/e/m/semperfortis/htdocs/wp-includes/pluggable.php on line 890

[Rukario]

I’m sorry, I finally found https://codex.wordpress.org/Editing_wp-config.php#Configure_Error_Log
but even that didn’t help. I don’t understand why my website is being so stubborn. BuddyPress worked flawlessly on my test server. I mean, I would have expected a little error here and there with maybe some quick fixes. I’ve been at this for weeks and it’s starting to get ridiculous. I might have to change hosts or find a different social community setup. I’d really hate to not use BP though, it’s so amazing and the best free one I’ve ever seen.

EDIT
Problem solved. All I had to do was set the WP_DEBUG to true in the WP_Config file and the errors showed up.

[Rukario]

I can’t seem to find the error log in the control panel or in my website file directories. If you don’t mind me asking, what exactly am I looking for?

[Rukario]

Actually, I just found out that I do have it and I was mistaken. Sorry about that.

So now I’m back to my original problem.

I understand that this is an issue known as “The White Screen of Death” rather than FTP install problems. I’ll just search around the other posts for an answer now that I know what I’m dealing with.

Thank you for all of your input and advice.

[Rukario]

I got a white screen on every web page (including the dashboard) and had to delete the BP folder through the FTP just to get my website back. Is there some sort of error-checking method I should use to pinpoint the problem? I know that my host has some sort of PHP safety on, but I’m not sure about other restrictions. My WP install works fine, so I thought BP would be compatible as well.

Now I’ve already installed and used BP on a XAMPP test server and saw that it goes through an install process, even after uploading the folder. What I’m forced to do on my host is upload the folder, with no install available, and activate it through the plugins page. I thought that the missing step was what was causing the problem, but are you saying it should work automatically?

I read this before trying it out too, and my host enables everything (to my knowledge) but the Apache Module mod_rewrite.
https://codex.buddypress.org/getting-started/before-installing/

Regardless, thank you for the quick reply.