BuddyPress.org

Hi,

Same here. For me the error lied in the Frisco theme. The Twenty Fourteen theme worked just fine. The fix discribed here:
https://codex.buddypress.org/themes/bp-default-theme-moving-forward-with-bp-1-9/ worked for me “with Frisco” just fine.

But a future proof solution would be nice in preparation to the complete bp-default absence.

BuddyPress Social Network

Seems to be what you’re looking for.

So you’re creating an additional Members page ?

If not, you don’t need an override.

If you are, you need to change this hook in that override
do_action( 'bp_before_directory_members' )
And call the new hook in the example below.

You need to know the id of the xprofile field that stores gender.
You need to know the value that is stored for Males.

Then you can tweak this code and put it in your theme functions.php or bp-custom.php

http://wordpress.stackexchange.com/questions/125754/buddypress-conditionally-filter-directory-based-on-xprofile-field/126553#126553

The terminology is important here. WordPress ‘pages’ shouldn’t be confused with the more loosely termed web ‘page’. Although BP ‘pages’ are webpages, they aren’t WordPress pages so is_page() isn’t going to work *most of the time*. The exception is register, activate etc.

For a list of template tags you can use with BP ‘pages’ take a look at:

Template Tag Reference

’m really not sure… but it *would be* really cool if those functions were integrated in such a way that nothing more would be required other than to install WordPress, Buddypress, then a theme… and call it a day. Not that I’ve had a problem with needing to copy the templates over to other themes in the past, but it’d be really awesome to see this worked out

This is the whole point of BP theme compatibility and has now been in existence since BP 1.7, you need to keep abreast of development changes on the BP blog and/or the codex documentation.

Right on.

So… after this update (the fixed version), will anything need to be copied to the ‘theme in use’ before it’ll pick up Buddypress’ template-pages, such as Activity, Groups, Members, and so on?

I may be misunderstanding here… I’m really not sure… but it *would be* really cool if those functions were integrated in such a way that nothing more would be required other than to install WordPress, Buddypress, then a theme… and call it a day. Not that I’ve had a problem with needing to copy the templates over to other themes in the past, but it’d be really awesome to see this worked out so that regardless of what theme was applied that the Buddypress template pages would simply be available and work correctly with no further configuration required to get those things working. For myself, as I say, it’s no problem… but for some of the locals that I host for… wow man… they need help! 🙂

[background: I’ve worked with Linux since 1997, Apache since 1998, and WordPress for about 5 or 6 years now… I’ve lost track of how long it’s been, actually.]

In my case I had to investigate thoroughly as possible, because the site I was building out when I noticed this problem is a site that is only available via Tor (with a .onion address). Building OnionNet sites using a nailed down Apache, WordPress, and Buddypress can be very tricky at times, if you’ve never done it before. But once the differences are learned, it’s pretty easy… not really any more difficult than any other wordpress site… it’s just a matter of a slightly different configuration, and email is worthless in these instances, so things must be done to eliminate the need for a valid email address during signup, but it’s do-able using some of the plugins that are available.

Anyways, you guys keep up the great work! 🙂
And…
Thanks for your help!

Same problem here.

I thought at first that it might be the security plugin I had installed today, but after removing that and finding the problem still existent, I began searching around and found your post and a few others like it.

So, from an SSH connection to the server, I dropped down into my wordpress-plugins folder, and ran “wget https://downloads.wordpress.org/plugin/buddypress.1.8.zip”, then renamed the old folder, extracted v1.8, verified that it was working after the reversion, and then deleted the 1.9 folder.

Maybe it’s just a conflicting plugin, but from what I’ve gathered so far, the problem appears to be an issue with a template file that should have been included with 1.9, but wasn’t. At the same time, there’s talk of EOL-ing the bp-default theme, which… ok… I can understand that, provided there’s something to take the place of it or at least a clear and concise way to provide the needed templates to other themes now that it seems the Buddypress Template Pack is no longer available (I certainly couldn’t find it, if it *is* still available).

Either way, this is an aggravating problem, especially considering that I run a large number of WordPress+Buddypress sites.

There will be a 1.9.1 put out quickly to address this.

The reason this is happening is because bp-default was deprecated with this release of BuddyPress and the notifications templates are not included in bp-default. This is your warning to phase bp-default out of your sites. BuddyPress works with almost any theme now so your options are plenty.

Same issue as I’ve posted here: https://buddypress.org/support/topic/buddypress-1-9-bp-default-theme-or-child-themes-notifications/

In vast preference to changing the core files ( where any changes that you make will be lost on updates ) you should look at creating a language file with your custom labels in

Customizing Labels, Messages, and URLs