BuddyPress.org

Whenever you want to have multiple loops on a page, you’ll have to define your own WP_Query. Here’s a good tutorial: http://weblogtoolscollection.com/archives/2008/04/13/define-your-own-wordpress-loop-using-wp_query/

It sounds like the key in your case will be ‘post_type=post’.

See this codex article https://codex.wordpress.org/Template_Tags/query_posts for info on what arguments you can feed to WP_Query (they are the same as query_posts() )

Yeah, I saw that WP.org thread and Andrea_r gave answer there and Ipstenu as well
@wp_y2m5tr take time to read the link given you in that thread

Saw your post in WP.org forums https://wordpress.org/support/topic/creating-rows-in-mysql-tables?replies=4

The best solution is to re-do the whole installation manually, as Andrea_r mentioned. If you’re getting into BuddyPress where you would have to add some configurations manually in htaccess/wp-config.php etc., then manual WP install and making it multisite would be good knowledge to have and good practice to boot.
https://codex.wordpress.org/Create_A_Network

“I recently used the plugin Enable Multi-Site to configure WordPress Multi-Site for my Buddypress install. “

Seriously – this is not recommended. I always recommend people set it up manually. the plugin only does 2 or 3 things for you – not the whole business and it doesn’t do any server checks that need a human eye.

‘If I try to navigate back to the main URL, I get nothing but a blank screen. Strange….”

No, not strange – it’s a common error called a white screen of death. It means you have some php messed up somewhere.

Can you get in to admin? Go in there, disable plugins. 90% chance something in there does not work with multisite.

well eevryone is i just posted as well…and im using all the latest updates both wordpress and BP

@bcade someone posted the same thing about “Enable Multisite Plugin” in WordPress.org forums, see if solution provided there will work for you.
https://wordpress.org/support/topic/plugin-enable-multi-site-enable-mult-site-only-partially-worked?replies=3

The GPL only applies to *distribution*. If your client plans on packaging up the website somehow… then worry about it.

“Does that mean that all of the code for this project would have to be GPL licensed and made available for free because we use BuddyPress for social networking? “

no, it does not. only if you actually *release * it. Just having it as part of your website is not releasing your code.

think of it this way – Buddypress is a plugin for WordPress. Anyone who build a site on WordPress itself is also not required to release their code.

(and I will note that GPL doesn’t mean it has to be free either. There’s plenty of for-sale GPL plugins and themes.)

If you want to use a WP network install, you need to install WP in the root and not a subdirectory:
https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

Read the red notice.

@jwack

hi, I had similar issues… even after removing the blog signup at registration, spammers would sign up, activate their accounts, and then create a new splog. to help cut down, I tried these steps:

– changed my registration slug in bp-custom.php:
define ( ‘BP_REGISTER_SLUG’, ‘join’ );

– also added a redirect of wp-signup.php inside bp-custom.php:
function register_redirect() {
if (strpos($_SERVER, ‘wp-signup.php’) !== false ) {
$url = ‘http://www.mysite.com/join’;
wp_redirect($url);
exit;
}
}
add_action(‘init’, ‘register’);

those two helped but didn’t completely remove the issue, this plugin really nailed it for us though:

– installed this plugin: https://wordpress.org/extend/plugins/invitation-code-checker/ (since we have a local comm site, we just used a zip code as the invite code)
Not sure how your site is set up but perhaps you can find a way to use it too, may even allow you to re-enable blog sign up at registration. It says Tested up to: WordPress MU 2.8.4 but I have WP 3.0.3 with network enabled and BP 1.2.6 and still seems to be working just fine.

Most of these suggestions were pulled from helpful posts on BP, hopefully they help you out a bit

Paul, I would like to know how to force my WordPress installation to run BuddyPress on only the Super Admin site, and not the member blogs. Could you guide me through the process. Thanks.

I have updated the BuddyPress Auto Group Join plugin to work with WordPress 3.0. I haven’t looked at r-a-y’s Welcome Pack, but I’m sure it does a wonderful job too!

Just to give a quick summary:

– current standalone bbPress plugins are possible to use with BuddyPress, but they need to be ported over to WordPress/BuddyPress. Check out Rich’s BP Forum Extras plugin, which combines a few of them:
https://wordpress.org/extend/plugins/buddypress-group-forum-extras/

– forum editor tutorial:
http://etivite.com/groups/buddypress/forum/topic/quick-tip-adding-markitup-to-group-forum-textareas/

or:
https://wordpress.org/extend/plugins/bp-tinymce/

– lastly, like Paul mentioned, bbPress is getting a major rewrite from an external script to a WordPress plugin. This will directly impact BuddyPress in version 1.3/1.4. Don’t worry too much about it now. Just use the BuddyPress’ forum setup as-is. Everything will sort itself out!

@ninamorena Wow, I’m not sure. That’s not a good thing to change. I assume you have a good reason for not installing WordPress at http://example.net/?

@mercime I think so, I’ve not come across this before.

Just checking in; haven’t had time to look, but haven’t forgotten.

I’ve not seen any. Is this reproducible, and does it only apply to certain user accounts? If so, anything special about those accounts — how they were created, etc

First of all, it’s not a database version. CSS in WordPress and BuddyPress has those “get” parameters in the URL as a means of forcing browsers to refetch the file rather than use its cached version. For example, when BuddyPress is upgraded in v1.3, you don’t want people to be loading the browser cache version of the CSS for v1.2. This is exactly what hnla told you above four weeks ago.

Secondly, if your theme is trying to load two versions of that file, it’s because in your child theme (or customised version thereof) is calling it twice. I can’t comment where or how this could be happening as we can’t see any custom script you’ve put into your theme.

Finally, you should be safe to copy and paste the php snippet r-a-y gave you two weeks ago into your functions.php; just be sure to paste it before the “?>” line at the bottom of the file.

1. Go to Google.com
2. Search for “tinychat wordpress”
3. Click on link “WordPress > Tinychat < WordPress plugins"

WordPress 3.0.3
BuddyPress 1.2.6
BP Group Documents 0.3.5

Plus a custom functions.php file which makes the autocomplete pick up all members not just friends, but this bug was happening before I created this file.

I don’t believe Giving WordPress its own directory works with BuddyPress showing up in the root when your WP is actually in the directory. Much like WP Multisite won’t work when you give WP its own directory. Calling on devs @DJPaul @boonebgorges @johnjamesjacoby. Is this a warning we should also add in Codex?

I am having this problem with bp, I am hosted by bluehost