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
BuddyPress themes require PHP tags like “bp_head”, but if an admin attempts to run such a theme without BuddyPress, WordPress will automatically prevent theme from being activated. Is there any way around this?
I’m trying to build a theme that’s customized for BuddyPress as an option rather than a requirement.
@laurentdesserrey no idea why it would break, works fine for me and many other people – I found it on a blog with many comments saying it works great!
Hentry’s code is a bit more complex and roundabout but it accomplishes the same thing. If you’re happy with it, great 🙂
@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.
Sorry while Im backing up, I already upgraded wordpress since doing that, this error pops up above one of my forms. Please understand I have taken over looking after these blogs and Im trying to update everything so any advice would be much appreciated.
Warning: Missing argument 2 for wpdb::prepare(), called in /home/railafr1/public_html/wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-classes.php on line 117 and defined in /home/railafr1/public_html/wp-includes/wp-db.php on line 992 –
@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
Hi @henrywright-1 again,
your logic is right, but I wanted to avoid editing templates. That’s the reason why I use Buddypress xprofiles acl plugin. This makes it possible to choose which role can see and use the different profile tabs. For the music embed I use BP Profile Widgets, the needed input fields are only visible to members with the userrole “band”, all other members can only see the output of the widget – music.
Your last post makes me think about other things that could be done beside those plugins I use, but that goes too far at the moment. As I tried to explain before, the really important thing about passing over the roles to xprofile-fields would be the possibility to show the roles for each member in a searchable and clickable way that always leads the user to the right member-directory.
Maybe you have more ideas, however, thanks for your ideas and help.
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.
Fredrick Townes mentions fragment cache or partial page caching here:
27 min mark
So I’ve been through the the template creation parts of the Codex, but I’m still having trouble figuring out what file I need to work with to change the look.
On the Buddypress profile page I would like to add an image to the right of each users avatar and name. I cannot for the life of me figure out what file I should modify to do that. Is it one of the PHP files or is that done in the style sheet? I swear I’d found the answer a week ago but now I can’t find the link again.
You can see my test site here:
http://www.strange-child.com/test-site/members/guest/
It currently has the most recent versions of WordPress, Buddypress and the theme is a child of Graphene.
Also, if there are any tutorials you guys would recommend I’d welcome the links. The only ones I’ve found are 3 years old.
@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:
- 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.
- 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.
- Low-hanging fruit. Often there are relatively easy tickets, something I can knock off in an hour or two.
- 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.
BuddyPress utilizes WordPress’ version of jQuery.
But I can see how this would be a problem for custom themes relying on something like Zepto.
You can try adding some javascript directly after the Zepto library is called to declare the jQuery variable as an instance of Zepto.
Something like:
<script type="text/javascript">
if ( typeof jQuery == "undefined" )
var jQuery = Zepto;
</script>
Not sure if that will work at all, since Zepto is a lightweight-alternative to jQuery, but hopefully that gives you an idea.
I get this JS Error after activation.
Everything is working except the Ajax stuff ( sorting – Groups, Activity … )
My starters theme is Foundation For WordPress – it’s a Zurbs Foundation 4.
http://fwp.drewsymo.com
I know Foundation uses Zepto.js instead of jQuery.js when a browser supports it but is this the real problem of this Error?
I think I have to change the name of the JS Variable but how does it work ?
i think i’ve tracked it down. there seems to be a conflict between buddypress and ‘Take Control Of The WordPress Toolbar’ plugin.
i’ve posted a support question but it doesnt look like the author is answering support questions any more. if anyone has any idea of how i might be able to fix this it would be brilliant as i am reluctant to delete the plugin, although i expect that will be the only option in the end.
Hi @laurentdesserrey
You can usually update content of these emails via a filter. See the Codex for more info https://codex.wordpress.org/Function_Reference/add_filter
For example, to filter the email body for message notifications, use messages_notification_new_message_message. To filter the subject line, use messages_notification_new_message_subject
Hope this info helps.
Hello! This thread is mostly accurate, but just to wrap things up —
@jjj has been working at 10up.com since August, and I’ve been at Automattic since the beginning of 2013. John and I had been contributing to BuddyPress for years before we started at Automattic. Our day jobs only affect our contributions to BuddyPress in a positive way; as @henrywright-1 pointed out, John’s built a whole new notifications component since he’s been at 10up! Wow!
While Automattic does own BuddyPress and the trademark in a very legal sense — and it’s my personal wish that one day the BP trademark is transferred to the WordPress foundation — they have no influence over the day-to-day of the plugin, and John remains in charge of the ship.
I’m also having the same issue as mentioned above.
BuddyPress 1.8.1
WordPress Multisite 3.7.1
The button works from the main Groups page, but not when on a single group page.
JJJ’s work on the notifications component pretty much answers that question. If you look at the updates in the Trac ticket you’ll see just how much time and effort he has put in over the past month.
