BuddyPress.org

I do hope they didn’t really say could only be fixed by buddypress support. Generally email issues are not BP problems, and currently BP has no issues I’m aware of in sending registration emails, which also is really a WP function.

Easy check that should have been run first would have been and still ought to be tried is to disable BP and simply try registering an account under WP.

Often email issues fall under the heading of ‘Domain Record’ issues i.e email servers rejecting an email as it can’t be verified as authorised on the sending domain or there’s no PTR record or SPF record, or simply that the server sendmail is at issue, these though are not really problems that lie with WP or BP which normally happily send out emails.

Search this forum though as these issues have been discussed many times and you’ll find more info in the archives.

@icepin while I write all my code as text domain translatable and if a plugin provide for a languages file lookup I would hardly ever really call the above ‘easy’ when a user simply needs to change one little character and where we’re not talking about a distributed theme or plugin.

@idavidson

The file that contains that translatable string is register.php if your theme is running bp in theme compatibility mode then the file being used lives in /bp-templates/bp-legacy/buddypress/members/

However you are NOT advised to edit theme files residing in the core plugin, if you wish to directly edit a template file you must make a child theme of the theme you are using and copy the template files over and edit in the child theme.

instruction for that may be found in the BP codex, and child theme creating guides in the WP codex.
https://codex.buddypress.org/theme-development/theme-compatibility-1-7/a-quick-look-at-1-7-theme-compatibility/

N.B. Any criticism of the above grammar or general syntax will be ignored! 🙂

the easiest way would be to create a folder called “languages” in your wp-content folder and put a copy of buddypress.pot from wp-content\plugins\buddypress\bp-languages.

– Rename the new buddypress.pot from “languages” to “buddypress-en_US.pot”
– Download Poedit – http://www.poedit.net/download.php – and install it
– Open “buddypress-en_US.pot” with Poedit
– Press Ctrl + F and search for “Registering for this site”. The string should appear.
– In Translation field put any text you want. It will simply replace the original text.

This is pretty much the best way to use your own words in your BP installation rather then modifying the core files. It might sound complicated but it’s actually pretty easy once you get the hang of it.

Cheers

It all very much depends on where exactly you want to display the bio info.

$user_id is the key variable you need, but obtaining this value is done differently depending on where you are on your website.

If you want to display bio info in a member’s blog post footer then add this to your theme’s single.php file:

<?php
$user_id = get_the_author_meta('ID');
echo xprofile_get_field_data('field=BIO', $user_id); 
?>

Note: You will need to change BIO to whatever you’ve called your bio field when setting it up.

Hi, I also do have the issue.
Tired two method, one is what you have suggested, instead the code into theme.css

#buddypress .standard-form div.submit input {
color: #000 !important;
}
It does not work.

I have a also come across a post stating about the height under” what-new-option”. Currently it is state 0px, so I change it to 40px first using firebug to try, and it actually appear, so I ask my friend to change it in my theme css(I do not know coding actually), and save the file. It doesn’t reflect again. Now I know it is actually visible, but it wont allows any changes in the less theme css.

Any help in this? Really appreciate.

@tse11
Patience please! Deactivate the plugin you was using for redirecting and try this in bp-custom.php https://codex.buddypress.org/plugin-development/bp-custom-php/ :

function bphelp_redirect() {
  if( is_user_logged_in() && is_super_admin && is_home) {
    // redirect to dashboard code
    bp_core_redirect( get_option( 'home' ) . '/wp-admin/' );
  }else {
      if( is_user_loggedin() && !is_super_admin  && is_home) {
    // redirect to activity code
    bp_core_redirect( get_option( 'home' ) . '/activity/' );
      }
   }
}
add_action( 'template_redirect', 'bphelp_redirect', 1 );

@tse11
Search the forum. This has been covered before! You could create a conditional to do this. Basically an if and else statement. You would need to include is_super_admin in the conditional check and the user would be redirected appropriately. For instance:

function bphelp_redirect() {
  if( is_user_logged_in() && is_super_admin ) {
    // redirect to dashboard code
  }else {
      if( is_user_loggedin() && !is_super_admin ) {
    // redirect to activity code
      }
   }
}
add_action( 'template_redirect', 'bphelp_redirect', 1 );

This would go in bp-custom.php:
https://codex.buddypress.org/plugin-development/bp-custom-php/

@cappiels you’d need a custom plugin to pull that off. Or, tweak https://wordpress.org/plugins/wp-fb-autoconnect/ or a purchase http://buddydev.com/buddypress/introducing-buddypress-facebook-connect-advance-facebook-loginregistration-plugin-for-your-buddypress-based-social-network/

Did you remove it from this file https://buddypress.trac.wordpress.org/browser/tags/1.8.1/bp-themes/bp-default/groups/single/activity.php

I hope you’re using a child theme of the BP Default theme instead of making those changes on that theme in your server. Otherwise, your changes will be overwritten when BP is updated.

@kvschwartz name of file should be bp-custom.php and not bp-customs.php
https://codex.buddypress.org/plugin-development/bp-custom-php/

@kvschwartz
bp-custom.php should reside in http://www.your-site/wp-content/plugins or if your on localhost it would be http://localhost/your-site/wp-content/plugins. It is not in a folder like other plugins would be. It is just a php file named bp-custom.php that occupies the same directory as a plugin. Please review:
https://codex.buddypress.org/getting-started/bp-custom-php/

Hmm didn’t seem to work for me, maybe i’m still calling jquery somewhere and not realizing it?
thanks for posting Henry!

@cpagan2000 thanks SO much for coming back and posting that code! I have literally searched for hours to try and fix my problem that my site, which has been running over a year spam free, all of a sudden was getting SLAMMED with spam registrations because BuddyPress hijacked my registration page and I couldn’t figure out how to make it stop.

For anyone else who finds this thread, you have to create the bp-custom.php file and put it in your wp-content/plugins folder (contrary to all the other information out there on the web – – SO CONFUSING!!) I tried to put in in my functions.php and it just wouldn’t work. You can find more information on customizing BuddyPress by following the link above that @bp-help posted above.

This information should really be easily accessible. No one should ever have to search this hard to fix this type of issue. That is why I made a point to come back and thank pagan and add the missing info that I had to track down to fully understand the situation.

@kvschwartz
Have you tried:

BuddyPress Notifications Widget

Or:
https://wordpress.org/plugins/buddymenu-buddylinks/
?

No what you are describing having started is a theme compat approach renaming page.php to buddypress.php ( that can be located for neatness in /buddypress/ or /community/; mercim’s post directly related to using the now older bp-default theme files copied over now you have started on theme compat stick with it, your issue is going to be that the theme does something to mess up page.php BP needs that file to adhere to WP template principles you must have a proper loop with the_title() and the_content() tags in place

You should be able to just add googles
wp_enque(the version I posted)

And they should work together.

This is more than likely due to the function which is (for instance) clipping your images needs an older version of jquery.

When you placed the bootstrap (v3?) and included the jquery in the statement then it over-rides that which is included in the image crop function.

try including versions jquery, and you might want to also include googles jquery and then test.
ie.
include path/jquery.1.1.min etc
Please let me know if this was the issue.

Specifically add this one first, and then lets see if your problem quits:

(‘jquery’, ‘http://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js’);

@henrywright-1 where did you use that? I think i’m having some of the same issues. Thanks for any help!!!