BuddyPress.org

It all depends on how the plugin functions. if you have WP options saved and then use bp_include to load plugin your settings won’t load fast enough for BuddyPress to use options.

bp_include is used for code that accesses BuddyPress code. So you know that BuddyPress is loaded before you execute code. It should not be used to detect if BuddyPress is active.

you can use https://codex.wordpress.org/Function_Reference/is_plugin_active

or check if ( class_exists( ‘BuddyPress’ ) )

@mgrmn There should be a “Create a Group” button beside the page title in the Groups Directory page. https://codex.buddypress.org/user/buddypress-components-and-features/groups/#groups-directory

If the “Create a Group” button doesn’t show up in your theme, that’s because the_title tag of page template is not within the WordPress loop. To resolve this issue, you can create your own link to the Create Groups page, just append /create to the URL of your groups directory page
e.g.
groups page -> http://example.com/groups
groups create page -> http://example.com/groups/create

Alternatively, if you prefer, you can instead add the patch to include the groups/create link in BP MyAccount section of the WP Toolbar https://buddypress.trac.wordpress.org/ticket/1838 – coming out in BP 1.8

Not sure, but I believe you need to add get_currentuserinfo(); for the part getting user info.

Try something like this to debug and see if you get any reponse at all.

function debug_userinfo() {
	global $current_user;
      	get_currentuserinfo();
	echo 'Username: ' . $current_user->user_login . "\n";
      	echo 'User email: ' . $current_user->user_email . "\n";
      	echo 'User first name: ' . $current_user->user_firstname . "\n";
      	echo 'User last name: ' . $current_user->user_lastname . "\n";
      	echo 'User display name: ' . $current_user->display_name . "\n";
      	echo 'User ID: ' . $current_user->ID . "\n";
}

See wp codex https://codex.wordpress.org/Function_Reference/get_currentuserinfo

@mike245 by default, there’s only one instance of BuddyPress per WordPress (single or multisite) installation. What you want – multiple BuddyPress installations in one Multisite install – is not possible without a BP multinetwork plugin. There are two plugins available and of those two, since you want a shared userbase, you would need https://wordpress.org/plugins/bp-multi-network/

yeah the hostile trick is a good way to “trick” your computer thinking a domain exists somewhere its doesn’t thus allowing you to not need to change the domain in the first place. that being said as Hugo mentions the codex pages tend to try to address the entire learning curve of any particular process meaning that they are giving you a bunch of options on that page you don’t need to be able to follow the entire thing to employ one of the listed techniques.

Another thing you may want to consider (depending on the amount of content your site will have prior to going public) is to simply build out on a dummy domain then reconstruct on a fresh install as soon as you are able to grab the domain. Regular wordpress content can even be exported from the construction site and then imported into the new site. Unfortunately no such process exists for buddypress data (groups, non post creating users and activity) but generally speaking those things shouldn’t take all that long to recreate unless your community section is going to be gigantic.

Shuklaamar- Be aware that if you edit core files as that web page suggests, you’ll have to make that same edit every time you update WordPress.

Honestly, my experience with WordPress on IIS hasn’t been that great. The rewrite/redirects are one thing, but the FastCGI implementation is not very robust, which can cause grief.

Polly- Your problem doesn’t appear to be related to the original question. I think you’re right that the problem is the theme, so contacting the theme author would be a good start.

-David

There isn’t a button or setting that will move everything for you. You could pay someone to do it if you’re not comfortable with doing it yourself. The cost involved for moving a stand-alone WordPress install (files and db) should be reasonable.

Even though your plugin is BP related, it might be worth also posting the question in:

https://wordpress.org/support/forum/plugins-and-hacks

Your reach will be extended to the WP plugin dev community

BP also hard-codes urls all over the place instead of making them relative.
Dunno why. Perhaps there is some setting to avoid this?
And what about serialized strings?

So use this:
search / replace

@4ella

$query = new WP_Query( 'post_type=portfolio' );

More info on how you can use the WP_Query class:

https://codex.wordpress.org/Class_Reference/WP_Query

There is a Codex page which will talk you through the steps you need to do when the time comes…

https://codex.wordpress.org/Changing_The_Site_URL

all of that is handled by the wordpress side of things, buddypress shouldn’t have any trouble handling a domain change. obviously any permalinks would change however.

i’d ask @jjj about it.

ah, ok so the plot thickens! now why can’t I see my own post then? very strange! I’ve also tried logging out and viewing the thread as well as viewing with another browser with no history of buddypress.com/support

@synaptic I can see your post for what that’s worth also thanks for the link neat tool!

@richardicanie your response sounds like you got my original message but I can’t see it on this thread (the forum here stopped it from being published and gave me an error when I tried to resubmit it).

anyway, about the site you mention: http://community.babycentre.co.uk/

it doesn’t look like they are using wordpress at all. my guess after looking at the source code is that it is drupal

in the future you can also check with builtwith.com

as far as why other sites are doing things the way they are we are making a bunch of assumptions right off the bat but from outside appearances the site you mentioned does not appear to be using buddypress. often times the forum/community software is a different platform from wordpress this is not the case with buddypress, that might explain why some other site would be compartmentalizing their community sections.

the only reason to use multisite is to create totally separate blogs/sites under one network setting. if you do not want to create (or let your users create) other sub-sites then chances you want to go multi are not great. You can also switch to that later if you choose (i had buddypress on a site for over two years before i took it multi).

once you go multi, new users are actually added to the network first they may then be added to a particular site either when you as either super admin or one of your sub-site admins manually adds them to a site or automatically based on activity i believe, that part still baffles me a bit honestly.