BuddyPress.org

A start would be to follow the installation guides!
https://codex.buddypress.org/getting-started/setting-up-a-new-installation/

What have you tried thus far?

Buddypress is as simple as downloading the plugin to your plugin directory and in the dashboard enabling the plugin. You can download the plugin from within WP!

Seems to be a bug or conflict between BuddyPress and qtranslate. https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/qtranslate-and-buddypress-problems/

Seems you’ve found the solution.

If you aren’t seeing any errors in the javascript console of non-Firefox browsers.. very odd. Are you using unmodified BP files and the unmodified default theme? If you’re using a custom theme, you could check if the problem occurs on the default theme.

Please give us some more info — https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/when-asking-for-support/

@techguy thanks but i did try that and it only removes from adminbar not the member profile nav bar. what i’ve ended up doing that works i guess is to use css.

#blogs-personal-li {
display:none;
}

@r-a-y is there any method of testing whether the page concerned is a root component, that is the page lives in the root directory e.g example.com/groups/

reason for asking is as the plugin stands anonymous users only ever see a login page, that can tend to put people off? they may base their decision to join based on what they see going on on the site to that end my preferred approach (or at least a further angle to take in restricting access) is to allow visual access to all top level pages but not deeper into the site.

I had thought that one could check on whether a page is a root component but can’t track that down, I can take various steps to getting closer to this by adding bp_is_front_page() to the :
if (bp_is_register_page() || bp_is_activation_page() || bp_is_front_page() ) and could add is_page(‘wp page’) for blog created pages – although oddly a page created to act as the blog page while setting front page to say ‘activity stream’ doesn’t appear to work??

Also of course one can add directory paths to the exclusion array:

$this->exclusions = array(
'wp-login.php',
'wp-signup.php',
'/wp-content/themes/child-theme-name/groups/'

But that isn’t best approach as it fails if one changes themes and child themes override bp-default so one can’t set that if suing child themes.

Overall and ideally a check to see if the page/directory/componant lived at root level would seem the best approach.

@nahummadrid
To remove the blog component from the top menu bar I think you can do:
remove_action(‘bp_adminbar_menus’, ‘bp_adminbar_blogs_menu’, 6);

@M no I realise you are not forcing anyone into anything and yes it would be wonderful if more people would bother to learn a little coding, not just PHP but general coding, but they won’t, it’s the issue of ‘Time’ and ‘Focus’ few can be bothered with either nowadays, it’s an instant gratification society where things are ‘Free!’ no effort required!

Forgive my comments, they were – in part – prompted by my feelings towards a well known outfit that offers paid support. I fact I agree 110% with your sentiments expressed in that last paragraph, I too am dismayed at what I see as a reluctance to appreciate the value in work done to provide such things as plugins (not only plugins or BP but coding provided across the development world online) I would argue that we have created a rod for our own backs in many ways and engendered a belief in non coders that this work is something trivial trotted of ones editor in no time with little effort. I wish that everyone using a plugin would understand that in fact there was an absolute moral imperative to ‘Donate’ towards that time spent developing it, considering the download stats one can observe sometimes that are in the region of thousands of downloads for something popular, if people only donated $1.00 that would still mean the coders time was recompensed, perhaps generously?

I’m no lover of the culture that has sprung up but it’s a culture that has been created by us providing the means for the many to find an easy in to running apps / sites without having to expend any / too much energy. To some degree I would argue in favour of the ‘Donate’ aspect being expressed in a much better manner perhaps with a note of the development time to create or even a stipulated amount of such low value, at least a quarter the price of a cup of coffee, that people would in fact feel obliged and happy to have to pay so little for something that has so much value to them? Of course a hundred contra arguments around this sort of subject though.

Here’s an old thread with all the Facebook-like chat scripts:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/facebook-like-chat-plugin-for-buddypress/

I’m glad you asked the author and are contributing to the plugin!

One thing WP-reCAPTCHA will probably need is to make the plugin BP-aware. More info here:
https://codex.buddypress.org/how-to-guides/make-your-plugin-buddypress-aware-v1-2/

This BP-aware code could then also be used as a conditional check.

I’ll take a look at the code in the next couple of days. It is indeed a Friday evening

Btw, glad to hear you’ll be contributing to the codex in the future! BP is most definitely a fun script to pick up and learn!

Looks like it’s working, though you’ll need some knowledge of CSS to get it the way you want BP to look.

@kipprsnak1 Can you give us a link to the plugin. Sounds like an interesting plugin, but if we can see it we can better understand what you’re trying to do I think. Seems like there should be a better way.

@Shnooka30 You really should use s2member. There’s quite a bit to it, but it’s all very well documented and it sounds like it will do exactly what you want it to do.

@Shnooka30

Try this:

http://www.primothemes.com/post/s2member-membership-plugin-with-paypal/

s2member allows for both free and paid levels (up to 4), and you can get really creative with what you want to restrict; from simple URIs to custom conditionals, and all the way to a whole bunch of hooks & filters to play with. Oh,and it works just fine with BP. Just be sure to read the documentation… there’s a lot!

Well, with just “they are messed up” to go on, it’s kind of hard to give specific help.
Got a link?

Scratch that — spoke to Blaenk, and I’ll just contribute to his project. So R-a-y, if you have any more thoughts for improvements looking at that, let me know, as I’ll try to clean this all up this weekend and make it less of a hack.

The beauty of Friday evening (and maybe Mercury is no longer in retrograde), everything’s coming together.

Full code…
http://pastebin.com/mWUALgdD
And again, apologies if I’m a bit slow on this stuff; as I said, part of why I wanted to tackle this.

Just tested it; that code does indeed work. I did need to then add an error display function, of course; right now that looks like this:
http://pastebin.com/v65A8mrk

Some cleanup to do on CSS, but otherwise this is functioning! Thanks!

I’ll keep you posted.