BuddyPress.org

I can’t believe that such a problem is not discussed to the point of being already solved.

I am sure that there are so many people who got wp installed in a subdirectory.

Two days ago I wrote an in-depth topic about just that. Please read it here.

It was TOTALLY ignored by the community.

I don’t care if it is the discussed here or there, as long as IT IS discussed, and not ignored.

Really, is there only 3-4 people with wp in a subdirectory and don’t want a permalink configuration such as: mywebsite.com/wordpress/activity?

C’mon…

(Oh, by the way my site does work with that setup, I just don’t want the subfolder in the permalinks, and yes, that represent a big issue for me).

Okay, is WordPress working fine before installing and activating BuddyPress?

Also, which version of WordPress and which version of BuddyPress are you using?

You need to look at your error logs to find out more details–both PHP and Apache logs. Your host should be able to give you access.

Finally, you can try adding this to the top of your .htaccess file:

### Set PHP directives ###

php_value memory_limit 96M

You may need to decrease that if your hosting company has not allocated that much memory for your account. You can try 60 then 30, for instance.

Ok, here I am.

For making buddypress a private commmunity, do the following:

-Create a new page in the admin interface.

-Make the page not to show in navigation with one of these: (http://www.kimwoodbridge.com/how-to-exclude-pages-from-the-wordpress-navigation-bar/ ) (https://wordpress.org/extend/plugins/exclude-pages/)

-Fill the page with HTML (as you wish). If you want Widgets, you can follow this: http://wpmu.org/how-to-widgetize-a-page-post-header-or-any-other-template-in-wordpress/

-Now, use this in the top of ALL PAGES NOT TO SHOW TO GUESTS: (https://buddypress.org/forums/topic/securing-components-from-non-logged-in-users/page/2)

if (!is_user_logged_in() ){

bp_core_redirect( $bp->root_domain.’/register’ );

}

AND REDIRECT THEM TO THE PAGE YOU CREATED BEFORE.

AND THAT’S IT!

How are you installing BuddyPress. Are you using the plugins search form in WP admin and automatically installing it from there? Are you manually installing it yourself? Or, are you using a service, an install script, that some Web hosting firms provide?

Also, can you confirm for me that WordPress works fine before you installing BuddyPress.

Okay, let’s try something else. Back up one step by deactivating BuddyPress once again. Next, make sure that you are using the default WordPress theme. We are trying to make sure that WordPress is working by itself without issue. I assume it is, since you have to activate BP from the Admin panel. But, let’s do this anyway.

Once again, before doing anything, make sure you have backed up your Data and have offsite copies of any non-default themes and your plugins. It is just a standard precaution that makes it much simpler to restore your environment if anything goes wrong.

Next, you’ll want to remove all your plugins from the “plugins” directory. Of course, you first have to be absolutely sure that you have deactivated them all before doing this. You should copy your existing, deactivated plugins into a temporary folder. That way, you can add them back into your empty “plugins” directory after everything is back up and running.

Now, you should have WordPress with the default theme and zero plugins in the “plugins” directory. Make sure that the plugins folder is still there. It should just be empty.

Does WordPress work without issue in this bare-bones setup?

If so, now you reupload the BuddyPress plugin into the empty “plugins” directory. Then, activate it. What happens?

@kanefulton-

Worrying about HD space is not relevant at this stage. Although the HD space is an issue once things are working, I was under the impression that you could not even get WP with BP working, that you kept receiving a Error 500. If this is the case, the allocated HD space is a moot point at this time.

Are you still having Error 500 issues? If so, that is where we need to be focusing the attention, unless you are planning on switching to a different host. Please read the threads that I linked to above. Is your site running under PHP 4 or PHP 5? Also, as @hnla states, there can be other issues with PHP memory limits.

Finally, I am a little concerned that you have manually edited your .htaccess file. If you’ve deactivated and uninstalled all plugins, then the . htaccess file that comes with WP should work fine. Is WordPress working fine by itself once you’ve distilled your WP install down to the lowest common denominator as I detailed in my first post above?

Let’s get WP working first and worry about BP later.

Delete the plugin to fix any admin issues.

Do you have wordpress mu or wordpress single user? Perhaps the call is different in single user?

Thanks,

Dave

tbh having looked at your hosts site as well I wouldn’t have been able top pass a judgement as to whether they were big or small, there are a lot of factors involved in good hosting and these are not necessarilly apparent just by looking at a site.

If they have offered to tweak settings to you requirements that is a good sign, good customer support counts for a great deal with hosting.

If your happy with this host I would stick with them, especially if they are willing to tune things as you need them.

As for basic requirements you need Apache to allow overide so that .htaccess rules will work, you need mem limits for scripts in PHP set quite high (higher than default) PHP version is best at 5.2 or above.

There are probably guides to optimum and required settings if you look around buddypress.org and wordpress.org and perhaps other members will chip in with min requirements for a healthy installation.

Out of interest what sort of hosting account do have presently and what do you plan to upgrade to? and are you intending running WPMU for it’s blog creation capabilities.

If MU and SU merge in 3.0 what does this mean for Buddypress. Maybe I should wait? Does this mean there will be no separate download and installs?

That reminds me of Lester Chan’s Post Ratings plugin – https://wordpress.org/extend/plugins/wp-postratings/ as well as this other one https://wordpress.org/extend/plugins/vote-it-up/ , but both are for posts and the latter one is reported broken.

What good about Lester’s plugin is that you could call the highest rated posts in a page via template tags or using the widget in sidebar http://lesterchan.net/wordpress/readme/wp-postratings.html

First of all, an Error 500 (internal server error) message usually means something is not working properly with one of the software components on you server. It is not directly a WordPress or BuddyPress issue.

I’m guessing it’s an issue with your PHP install. Forcing the server to run PHP 5 instead of 4 may do the trick–assuming your site is being served under PHP 4. This is just an initial guess. See these threads for more detail:

https://buddypress.org/forums/topic/error-500-internal-server-error-an-internal-server-error-has-occured-please#post-23821

https://buddypress.org/forums/topic/500-error-after-uploading-buddypress-102#post-18421

However, there could be something else causing the problem. What you need to do is distill your environment down to the lowest common denominator. Make sure WordPress is working fine by itself before installing BuddyPress. To do that, you deactivate all other plugins and test WP by itself. If it is working without issue, then you reinstall BP and activate. You should not have any other plugins besides BP activated and you should be using the default theme that comes with BP when testing.

By the way, I suggest doing a clean install of BuddyPress. This means making sure the entire BP directory is removed and then starting over with a clean install of BP. Of course, as always, backup any data before you do any upgrades or reinstalls.

If you do not have any issues with WP running only the BP plugin using the default BP theme, then you know it has something to do with a custom theme, one of your other plugins, or some combination of the two.

You then start going back up the ladder one step at a time. Switch the default BP theme to your custom theme. Does the problem return? It not, then is has to do with your plugins. Activate one plugin at a time until the issue returns.

But, with an Error 500, I’m guessing it is something outside of WP and BP causing the issue. Show the links above to your hosting firm. They are the only ones that can help you.

Also, as another resource, search the WordPress forums to see if anyone there has reported a similar issue.

Hmm..

The BuddyPress Group forum system is actually powered by bbpress so it should be able to handle anything bbpress can. It is up to you whether you want to use the group forums system or work on integrating a standalone bbpress install into wordpress.

Ok, this particular problem really sucks. You use bp_core_load_template() in a plugin to load a theme file, using the filter ‘bp_located_template’.

If you’re modelling your plugin on the default BuddyPress components, or even the skeleton component, you could use the above to load an index page for your directory, and use a “loop” file to display each item within your directory index page.

However, the whole purposes of the ‘bp_located_template’ filter is that it allows theme authors to override your plugin’s theme file by adding it to their WordPress theme directory. The problem is that you cannot use bp_located_template() to include your loop file (henceforth referred to as a “plugin sub-template”).

Why? Because bp_core_load_template() just sets up the data for the template to load; nothing happens until the WordPress ‘template_redirect’ action is called, which only happens once on page load (.e. when it loads your index page).

Quick fix? After calling bp_core_load_template( ‘plugin/sub-template.php’ ), just call bp_core_do_catch_uri().

Proper fix? Working on it.

bp_core_load_template is not working when trying to load plugin’s sub-templates from within that plugin’s template file(s)

Look at the html source of the page. He’s made 3 columns with css. Each one pulls a custom loop pulling posts from a particular category.

It’s purely theme dev here. You may have more success searching elsewhere for this particular technique used in WordPress themes in general.