[@johnjamesjacoby Keymaster 16 years, 8 months ago]

Did you do this:

https://codex.buddypress.org/how-to-guides/wordpress-to-buddypress-theme/

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

Have you gone through the bbPress installation process in your wp-admin yet?

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

This problem comes from the bp_has_custom_signup_page function.

It checks to see if your theme can locate_template( array( 'register.php' ), false ) or locate_template( array( '/registration/register.php' ), false ) )

Since your child theme has neither of those files, naturally it will return false and give you wp-signup.php as the link. To counter this, BuddyPress attempts to be smart and redirect to BP_REGISTER_SLUG.

If you always want to bypass this check all together, you could try putting this in your bp-custom.php file…

function bp_custom_get_signup_page( $page ) {

global $bp;

return $bp->root_domain . '/' . BP_REGISTER_SLUG;

}

add_filter( 'bp_get_signup_page', 'bp_custom_get_signup_page' );

Note that bp_get_activation_page and bp_has_custom_activation_page work the same way, and the same rules apply if for some reason you want to bounce people from a different activation page.

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

@darbymanning It looks like you’re using an old BuddyPress theme, with bits and pieces of theme in the wrong spot. Maybe try reuploading BuddyPress and the bp-default theme and try again?

@nathankisanski BuddyPress by default doesn’t use your displayname for the URL, rather it uses either your nicename or login (I forget which at the moment and it switched a few versions ago.)

I think the variations of this issue might come from custom themes and how they’re handling the functions that handle the template loading locations. If BuddyPress looks for a template file in a directory, but that file does not exist, you will get bounced back to the root URL of the installation.

A good example of this happening is if you’re using the old BuddyPress template directory structure, and have the new bp-default theme installed, or vice-versa. Since the old file directory for the members directory was /bp-default/directories/members/index.php (or something like that) and it’s now /bp-default/members/index.php, if BuddyPress is looking for one when really the other is there, you’ll get bounced back to the root when trying to access that page.

If you’re using an old style theme, there’s a global that needs to be set. ‘BP_CLASSIC_TEMPLATE_STRUCTURE’ will tell BuddyPress to look in the old locations for the template files. Set that in your functions.php for your theme.

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

Check out https://trac.buddypress.org/ticket/1970 and see if those fixes help?

I know there are lots of different server setups and installation types we’re trying to account for, so it’s possible that something could need adjusting.

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

It broked my guestbook. 1 star.

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

A few other actions were added in 1.2 to help plugin authors hook into the correct places within BuddyPress.

bp_setup_globals

bp_setup_nav

bp_setup_root_components

bp_setup_widgets

The intent of those hooks for plugin authors, is to not load your code before BuddyPress does, potentially putting your navigation menus or global component setups out of alignment with BuddyPress. Typical WordPress priority rules apply, so it is still possible to bump your plugin ahead of BuddyPress if you need to.

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

Can someone file a ticket on this if you haven’t already. This is a bug that will need to be addressed pretty quickly.

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

/* Bounce user to their profile when logging in */

function custom_login_redirect_to_profile( $url, $isset, $user ) {

return bp_core_get_user_domain( $user->ID );

}

add_filter( 'login_redirect', 'custom_login_redirect_to_profile', 11, 3 );

You could also make a child theme of your own, and use home.php as members/single/activity.php. Or instead of using home.php, make a custom page template and assign that page as your front page.

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

https://trac.buddypress.org/browser/trunk/bp-core/bp-core-activation.php#L79

There are two ways for this email to still get sent:

1.) Your active theme does not have either /register.php or /registration/register.php in it.

2.) You are an admin that has just added a user to your site.

If either of those things are true, the email will get sent out.

---

If you are hard pressed to make this issue go away, try adding this to your functions.php or bp-custom.php.

/* Unhook BuddyPress wpmu email blocker */

remove_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );



function block_wpmu_email() {

if ( is_admin() && $_GET['e'] )

return true;



return false;

}

/* Rehook custom function */

add_filter( 'wpmu_welcome_user_notification', 'block_wpmu_email' );

The above routine doesn’t help us test this issue any, but it does stop the email from going through unless you add a user yourself.

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

bp_is_my_profile() …will tell you if you’re viewing your own profile…

bp_is_member()…will tell you if you’re viewing any user, including yourself…

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

It sounds to me like the upgrade (or FTP) didn’t add and/or replace all of the included files.

Can you BACKUP and completely remove the entire plugins/buddypress directory from your installation, and install a fresh copy of 1.2?

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

Have you tried turning your internet connection off completely?

I had this issue as a result of the anti-virus and firewall I was running at the time. Turned off the firewall and anti-virus, and all was well. I’m sure there’s a better solution, but that did it for me.

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

http://premiumbpthemes.com is shaping up to have some nice offerings soon. Otherwise there’s always https://buddypress.org/extend/themes/

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

BuddyPress.org is the insider community. If you’re registered and paying attention, then you’re one of the cool kids.

There’s a few reasons why BuddyPress.org works and looks different than a usual BuddyPress installation does out of the box. I’ll do my best to explain them for you (and everyone else) but I can assure you, there’s nothing stopping anyone from mimicking this or infinite other kinds of hybrid installations.

1. This site uses the old and very yucky deep integration method with bbPress. Before BuddyPress 1.1 that was the only way to do it. With 1.1 Andy wrote an abstraction layer for bbPress to seamlessly bring its functionality into a WordPress installation.

2. The decision was made that forums made the most sense when linked directly to a group of users. Rogue forum categories without a group of users to attach them to, have taken a back seat for the time being. This has been the topic of debate for a while, but it won’t change for 1.2 and probably won’t change until bbPress as a whole gets a little more attention.

2. Because BuddyPress.org links directly with WordPress user and usermeta tables (which is why your 1 login works at all WP related sites), upgrading and shifting around over a million registered users isn’t a task to be taken lightly.

3. Since Buddypress 1.1 was released, BuddyPress.org hasn’t changed a single bit. Little to no attention has been paid to the inner workings of this site, and all efforts have been poured into the project itself in a very successful attempt to deliver a much more stable and solid project. Even group avatars on this site are still broken from the conversion.

4. The purpose of the support forums is to have a central community devoted to the questions and answers that a wide array of users have while installing, theme-ing, and in general just using BuddyPress. If you have needs that don’t fall within the core code then you’re stepping outside of core support and looking for custom development.

5. Many people on the forums (including myself) have stepped up and taken on side projects (pro bono or as paid clients.) A slew of plugins are available specifically to enhance parts of BuddyPress, but just like with WordPress if nothing currently exists that does what you need, you either need do it yourself or find someone to do it for you in a way that fits your budget.

6. BuddyPress 1.0 launched in April of 2009. It’s less than a year old and 2 major updates have already come through with even more to come in 2010. It’s still a baby compared to WordPress and bbPress, and I think Andy and myself will be the first people to say that it’s still capable of a lot more. Patches are always welcome, and in the past year the number of code committers has doubled (from 1 to 2 ) and the number of significantly contributing code patchers, bug reports, and trac tickets has just about doubled also.

So, if you’re unhappy, I can understand why. In a way BuddyPress.org sets an unrealistic expectation of a turn-key installation. If you feel you’ve been mislead in one way or another, that makes sense to me. Your opinion is valid, and when the site is updated to 1.2, I think you’ll be pleased.

In the meantime, if you choose not to use it that’s okay. If you choose to study the code and start submitting ideas and patches, that’s cool too. Whatever anyone decides to do, I don’t think anyone will be mad. We’re all buddies here, remember?

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

Netbeans

Notepad++ for spot edits

IIS for easy local site deployment on Windows 7

TortoiseSVN

PoEdit

SmartFTP

phpMyAdmin of course

Firefox + Firebug for peeking at source; Google Chrome for speedy previews of changes

Pidgin for IRC

Skype for work

Tweetdeck for staying connected to the outside world

Pandora for a random music mix

Whiskey, because it makes everything better…

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

This is going to need an update to work with 1.2 and the bp-default theme. The files have changed as well as the ajax makes the sort-order a little wonky.

An update for 1.2 is coming soon.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

@arnonel, the parent template file is never accessed. The only possible performance hit you would see is with loading the additional CSS from your child theme. Since you’re styling it one way with one set of CSS rules, then overriding it with another, you’re basically doing the same thing twice.

It’s still the best/only way of doing this without totally writing your own CSS from scratch, or copying the bp-default CSS over totally, and never including it from the parent theme. If you go that route, you run the risk of not getting updates when CSS changes in the parent theme.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

Hmm…

Does your plugin use ajax? I haven’t specifically tried hooking a plugin into the ajax portion of the activity stream to know if the method of loading a plugin from the codex will work in an ajax situation.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

Just tagged version 0.5.3 of the BuddyPress Backwards Compatibility plugin to fix this.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

6 hours and yusoof hasn’t responded yet? Is he even reading his own topic to know we’re trying to help him?

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

Akismet can sometimes be a little over sensitive, so taking the bad with the good means some false positives from time to time.

If you’re having issues on BuddyPress.org with your posts or topics going rogue, send myself or another moderator a PM and I’ll make them appear again. If it’s an urgent topic let me know on Twitter: @johnjamesjacoby

Also, do this too.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

Unsticky-ing this from the front page. This should start to go away with 1.2.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

No, this isn’t built into the core, but we’ve talked about it for quite a while. This will probably happen in the future, particularly with the ability to @mention someone; now all that’s missing is the ability to look at other people’s @mentions and follow their activity streams.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

@r-a-y

Using plugins loaded still does not promise that the user has BuddyPress installed on their site and activated on that particular blog, so you will still want to do the check for BP_VERSION.

It’s a dizzying setup, trying to make plugins off of plugins that may or may not be there, or are there but just aren’t loaded yet, or are loaded before yours because another plugin force loaded it out of order.

Going forward from BP1.2, we can avoid all of those issues. Remember too that bp_init has priorities too. If you need to make sure your plugin is loaded before any other BuddyPress extensions are, you can prioritize it’s load the same way as any other WordPress action.