BuddyPress.org

@shubh14 It could be plugin conflict with the theme. The best place to ask for assistance is at the plugin’s forums. https://wordpress.org/support/plugin/buddypress-media

@rastarr
– There’s a free plugin but has not been updated in over 2 years https://wordpress.org/plugins/bp-ninja/
– There’s premium and maintained plugin http://buddydev.com/plugins/bp-stealth-mode-for-site-admin/

All the details can be found at the link I provided above, but essentially it utilizes PhoneGap which allows you to write in HTML, CSS, and JS. You can submit your code to App Store and Play store. I am writing the plugin needed to communicate with the application and the application that will be submitted to the store. With both of these pieces you will be able to have a mobile application in both stores and directly communicates with your WordPress/Buddypress website.

@pjbursnall

see: https://buddypress.org/support/topic/dashes-in-usernames/#post-169926

Though this looks like it might be resolved in bp 1.9

probably the right way to do that is turn registration off in the general wordpress settings.

@pjbursnall yeah that code replicates the notification element only (the only part that is somewhat confusing to replicate) you place the code in the plugins directory in bp-custom.php you may have to create the file yourself.

http://stackoverflow.com/questions/9953482/how-to-make-a-pure-css-based-dropdown-menu – shows you how to create a drop down menu, https://codex.wordpress.org/Function_Reference/get_currentuserinfo get the current users info so you can create links to their profile pages, etc.

Just a note, to add the notifcations to your custom bar your code will look something like <li><?php bp_notification_badge(); ?></li>

It may be a conflict with buddypress.css and the WordPress theme. Have you inspected the element in Google chrome?

I think what you’re really looking for is this plugin: BP Direct Menus. You can put a menu item or shortcode that links to any buddypress page. It even lets you customize the menu name with the user’s information.

Full disclosure: I wrote the plugin after I couldn’t find a more elegant solution to this same problem.

you set that in wordpress reading settings to whatever you want.

Theme compatibility lets you use BuddyPress with themes built for WordPress. So build your theme and when you activate or deactivate BP it will continue work seamlessly:

Theme Compatibility & Template Files

@chouf1
Oh sorry about that! I’m using:
Wordpress 3.7.1
Buddypress 1.8.1
bbPress 2.4.1

After having deactivated everything and tried things 1 by 1 and because i’m running a subscription based shin-dig, like i suspect a few others here are doing, running the show from the back end seems like the best course of action (althought the back end version works if i’m using another account with similar access).

The former is another work around if one wants to use less plugins.

Working great !

Thanks 🙂

@synaptic I didn’t realise the auto emails were sent from ‘wordpress’@mydomain so thanks for this!

@laurentdesserrey

The code does go into your theme’s functions.php file. This is what I have:

function custom_wp_mail_from( $email ) {
        $handle = 'laurentdesserrey';
	$find = 'http://'; 
	$replace = '';
	$link = get_bloginfo( 'url' );
	$domain = str_replace( $find, $replace, $link );
	return $handle . '@' . $domain ;
}
add_filter( 'wp_mail_from', 'custom_wp_mail_from' );

Note: change the handle. I’ve used ‘laurentdesserrey’ but you could use ‘admin’ or ‘support’ or ‘info’ – whichever works best for you.

Reference: https://codex.wordpress.org/Plugin_API/Filter_Reference/wp_mail_from_name

I wanted to avoid editing templates

I suppose you could achieve what you’re trying to do by using a bunch of action hooks although the advantage of theme template files is they are there to be edited.

Hopefully you’ll be able to get your plugin approach to work! Perhaps it might be worth throwing BP Profile Search into the mix. It offers some improvements over the standard BP member search.

Hi @synaptic,

I’ve the same issue. I tried to add this to functions.php but my site breakdown when I do that.

Could you be more precise on where you put the code ? 🙂

I’m not a (real) dev so not really comfortable yet with this.

Thank you very much 🙂

Laurent

https://wordpress.org/plugins/embed-rss/ works well.

It can also be done using https://wordpress.org/plugins/widgets-on-pages/
Add the Place the RSS Feed Widget Inside the Widgets on Pages Widget.

Hop this helps.

This file: https://plugins.svn.wordpress.org/buddypress/tags/1.8.1/bp-templates/bp-legacy/buddypress/members/single/member-header.php

@synaptic Thanks for starting this interesting discussion (and for doing it in a more sensible and measured tone than the linked article).

I agree that the current process for selecting and advancing features is not ideal. It is indeed a shame when a ticket like the CPT one gets punted release after release. I’m not sure that I can *justify* it, but I can *explain* it.

In brief, BuddyPress is maintained and developed by a small number of volunteers. (Contrast with WordPress, which has quite a large number of contributors, and a number of people who are paid to work exclusively on WordPress core as part/all of their day job.) So, the things that get developed during any given release are those things that the small number of volunteer developers have chosen to spend their time on. How do the developers choose? Personally, I tend to gravitate toward those items that fall into one or more of the following categories:

1. Items that other people have contributed code to, either in the form of an existing plugin, or a patch, or whatever. This is both because these items mean not starting from scratch, and because it validates those contributors’ time and effort. The new dynamic menu system (described here http://www.wptavern.com/buddypress-1-9-will-include-dynamic-menu-links) is a great example of this: community member imath contributed a very nice patch, so it got moved up in the list and will be part of the 1.9 release.
2. Items that someone is paying me to build anyway. I’m a consultant working on BP projects, and sometimes a client wants a feature that would be valuable in BP itself. If I’m not mistaken, the new notifications component for 1.9 is an example of this – jjj was working on it for a client, and so was much of the way toward having it ready for BP.
3. Low-hanging fruit. Often there are relatively easy tickets, something I can knock off in an hour or two.
4. Stuff I enjoy doing. There are some sorts of features I prefer to work on, and I’m more likely to spend my volunteer time working on them.

This isn’t an exhaustive list, but it gives you an idea of the kinds of motivations that go into the contributions of a volunteer. And it means that sometimes tickets that garner interest and conversation – your CPT ticket example is a good one – can fizzle. Sizable features like this really need to be personally shepherded by someone in order to be successful, and there is simply too little developer time to cover all worthy tickets.

Is our system for choosing features and fixes perfect? No, definitely not. Your voting idea is a nudge toward something missing from my list: “items that are wanted most by the community”. If you’re interested in pursuing something like this, please please please do – the Future Release pile has lots of good stuff in it, but it really needs people to read through tickets and pick out the stuff that should be presented to the community. Feel free to reach out to me if you want to talk more about this.

As a side note: Deciding on roadmaps, etc is really hard. We want to do what’s best for the project (whatever that might be, and however you might determine it), but at the same time we want to ensure that contributors – who, it’s important to remember, are giving their free time to the project – are working on things that they personally find valuable and enjoyable. I’m eager to work with interested members of the community do a better job at striking the necessary balance.