Support Forum

Mr Papa said

include_once(…/wp-content/sp-resources/forum-plugins/buddypress/library/sp-buddypress-component.php):
failed to open stream: No such file or directory in …/wp-content/sp-resources/forum-plugins/Buddypress/sp-buddypress-plugin.php on line 154

going to jump back to what I said at the beginning... assuming above is really the error message...

The directory name MUST be buddypress...  according to the error message its Buddypress...

buddypress is not the same as Buddypress...  unix directories are case sensitive...

Well, Mr Papa, if that is the case, and I've repeatedly stated that it is not, then it is because that is how the file is named in the infrastructure of YOUR plugin... I don't know what more you want me to do...

Yellow Swordfish said
First off - well spotted Steve. I didn't notice that errant capital 'B'. Still not sure that this would cause a 500 error but it sure would stop the plugin from working.

It is NOT how it is delivered. If it were then we would be hearing loudly from all the users who have this plugin active.  So - having said that - have you tried changing it?

I agree, that is not how it is delivered (see .png above), but I can assure I didn't change anything. Here is another screenshot of what is actually in the directory...

So, to answer your question, I haven't tried changing it because there isn't anything I can change. 

Yellow Swordfish said
So has that error gone away? Did the permissions check out and are you still getting a 500 server error?

And if you are still seeing that error in the error log with the capital 'B' then perhaps that is also a question for your host support.

I decided to completely uninstall simple:press and start over. I have successfully installed buddypress. Being that I never touched the names of the files, I'm inclined to suggest that the buddypress plugin didn't play nice with something else I had installed beforehand. Given that there are no other users with similar problems, this may not be anything you are interested in looking into. I will now begin reinstalling the other plugins and I will post back if the error returns (and let you know which plugin triggered it). Otherwise, thank you both for your time and attention.