BuddyPress.org

Log in to your account on this site, and put this in your browser address:

http://sob-s.com/groups/create/step/group-details/

Then tell me what it says or does after that.

have they checked their junk mail / spam folders?
If your users aren’t happy about this, just wait until they start using it – lol it’s a crude work in miserable progress imho – the signup issueS are just the beginning. I would consider buddypress more of a hobby thing for those who want to spend long hours in multiple forums trying to hash out why everything does not work well together. You will find spam robots have no problem signing up and activated dozens of accounts daily. Once your users actually get activated they will have a great time trying to sort out real blog posts from spam, they may wish they never signed up in the first place – especially if they create their own group.

See. I feel like such an idiot. I’m stuck on the first two steps!
My instructions are:
Open up the httpd.conf file or the include file containing the VHOST entry for your web account.
Add this line:
ServerAlias *.example.com

In the DNS records on your server, add a wildcard subdomain that points to the main installation. It should look like:
A *.example.com

Firstly, I can’t find the httpd.conf file they want me to edit. I do have the ability to add subdomains so I wonder if putting * in the cpanel field will suffice.

When I access the DNS records on the server I have two fields to fill out:
Name and Address.

Am I correct in assuming Name = A *.razewv-tac.org and Address = http://www.razewv-tac.org?

Do I not recall this issue being raised a while ago? Are we talking about the *Default* WP admin acount created at initial signup and of the practice of then changing or masking that accounts displayed name by editing the DB entries?

The @ mention on the member pages is always based on the user’s log-in name. I have just created a tested a new install with an admin account username of “pgibbs”, and it displayed @pgibbs on the member page.

When the admin account is created for buddypress, the @mention is “ @admin“.

I’m not sure what this means. BP doesn’t create any admin accounts. It uses the same accounts as your WP installation. As long as you have WP 3.0+, you should have had the opportunity to select your admin login name when you signed up.

Can you be more specific about where you are seeing @admin show up incorrectly? In the member header? Or in activity items? Or elsewhere?

@jwack

hi, I had similar issues… even after removing the blog signup at registration, spammers would sign up, activate their accounts, and then create a new splog. to help cut down, I tried these steps:

– changed my registration slug in bp-custom.php:
define ( ‘BP_REGISTER_SLUG’, ‘join’ );

– also added a redirect of wp-signup.php inside bp-custom.php:
function register_redirect() {
if (strpos($_SERVER, ‘wp-signup.php’) !== false ) {
$url = ‘http://www.mysite.com/join’;
wp_redirect($url);
exit;
}
}
add_action(‘init’, ‘register’);

those two helped but didn’t completely remove the issue, this plugin really nailed it for us though:

– installed this plugin: https://wordpress.org/extend/plugins/invitation-code-checker/ (since we have a local comm site, we just used a zip code as the invite code)
Not sure how your site is set up but perhaps you can find a way to use it too, may even allow you to re-enable blog sign up at registration. It says Tested up to: WordPress MU 2.8.4 but I have WP 3.0.3 with network enabled and BP 1.2.6 and still seems to be working just fine.

Most of these suggestions were pulled from helpful posts on BP, hopefully they help you out a bit

I’ve not seen any. Is this reproducible, and does it only apply to certain user accounts? If so, anything special about those accounts — how they were created, etc

I doubt it’s a bug but design, deleting an account is a WP process, xprofile data is BP data I would assume that WP is not aware of a plugins tables and therefore couldn’t and wouldn’t delete that data. Generally plugins that create tables do not clean them up if deactivated in case data is still required likewise WP would be in error if it started to delete plugin tables. Of course I might be wrong on all that

@pcwriter go for it, it’s there to be used if it suits the purpose. – API keys were always a pain

@leguis08 Glad it works.

@gunju2221 It is very possibly a custom theme issue, a custom theme will have to have ensured that the correct action hooks exist in pages as the main maps are fed through to the page via these, you could test with the widget instead which was provided really so that site admins could place the map in more refined custom widitised areas of the members profile pages if they existed.

When writing something like this you can only account for that which is known thus the included stylesheet is there simply to try and style the map if it’s dropped into bp-default, therefore those styles may not have relevance to a custom theme, especially where that theme may be heavily modified, however the basic styles are worked on elements and element id’s/classes that should exist in any theme.

The other aspect of course is that you must have created that extended profile field and named it ‘location’ and existing users will then need to actually edit their profile to add an address or partial address for the map to display, if a user hasn’t filled this item in then the map does not display at all.

Unfortunately I don’t think there is a super easy short term solution.

You’d have to create a new WP capability, and then on each page load, you’d have to essentially spoof the proper BP permissions. For groups and forums that means $bp->is_item_admin. In the case of activity deletion, there isn’t really a good piece of data to spoof (aside from the activity’s user_id field, which is obviously used for other stuff like displaying the activity avatar and so probably shouldn’t be messed with). So you might need to build your own delete links, and then make your own function that replicates bp_activity_action_delete_activity() except that it (a) hooks earlier to `wp` (maybe with a priority of 2 rather than 3) and (b) replaces the `/* Check access */` business with your alternative.

The core team is hoping to make this sort of thing easier in 1.3. Once BP has taken better account of proper user roles, I think it’d be an appropriate feature request that this sort of role be part of BP core, as it’s something that will be needed by pretty much any community site beyond a certain size.

I fixed most of mine by adding a few fields in the Profile Field Setup. I added City, State ( as a dropdown menu and a zipcode. I got rid of 70% just from this. also, I have seen in my log files they are searching for
“yes i d like to create a new blog”
“registering for this site is easy just fill in the fields below and we ll get a new account set up for you in no time yes i d like to create a new blog”
“intext yes i d like to create a new blog blog with wordpress inurl register”
“i d like to create a new blog”

maybe someone can tell us where this text lives so we can remove these tags from the search engines. just by this they are able to see all wordpress sites. I tried it with google and it does work.

In “Community”, I only see Activity, Members and Groups. In “My Account”, I see Activity, Profile, Messages, Friends, Groups, Albums, Settings, Logout (with appropriate subnavs). The Create a Group button is only seen in the Group directory (where it should be), but you can grab the code from groups/index.php and add it to other templates too if you prefer.

I just created an account on your site and was able to create a group just the way it’s supposed to be done (the “Create a group” button is in the Groups directory).
Forums aren’t enabled yet on your site, are they? You can do that in your WP backend under “Buddypress” > “Forums Setup”.

ok created this but made it so you verify via the WP backend at the bottom of each user page there is a check and it will show a little verified in profile header. I’ll upload it to the plugin repo after I create a check graphic.

https://wordpress.org/extend/plugins/user-role-editor/

Thats one but i’m not sure it will work with BP. My thought was you could create a “verified” role and then do an if statement for some code to show a verified check badge.

I may make a plugin that adds a verified check.

You can add the login form to one of the columns after

<div id="third-section" class="widget">


login code:

<?php if ( is_user_logged_in() ) : ?>

        <?php do_action( 'bp_before_sidebar_me' ) ?>

        <div id="sidebar-me">
            <a href="<?php echo bp_loggedin_user_domain() ?>">
                <?php bp_loggedin_user_avatar( 'type=thumb&width=40&height=40' ) ?>
            </a>

            <h4><?php echo bp_core_get_userlink( bp_loggedin_user_id() ); ?></h4>
            <a class="button logout" href="<?php echo wp_logout_url( bp_get_root_domain() ) ?>"><?php _e( 'Log Out', 'buddypress' ) ?></a>

            <?php do_action( 'bp_sidebar_me' ) ?>
        </div>

        <?php do_action( 'bp_after_sidebar_me' ) ?>

        <?php if ( function_exists( 'bp_message_get_notices' ) ) : ?>
            <?php bp_message_get_notices(); /* Site wide notices to all users */ ?>
        <?php endif; ?>

    <?php else : ?>

        <?php do_action( 'bp_before_sidebar_login_form' ) ?>

        <p id="login-text">
            <?php _e( 'To start connecting please log in first.', 'buddypress' ) ?>
            <?php if ( bp_get_signup_allowed() ) : ?>
                <?php printf( __( ' You can also <a href="%s" title="Create an account">create an account</a>.', 'buddypress' ), site_url( BP_REGISTER_SLUG . '/' ) ) ?>
            <?php endif; ?>
        </p>

        <form name="login-form" id="sidebar-login-form" class="standard-form" action="<?php echo site_url( 'wp-login.php', 'login_post' ) ?>" method="post">
            <label><?php _e( 'Username', 'buddypress' ) ?><br />
            <input type="text" name="log" id="sidebar-user-login" class="input" value="<?php echo esc_attr(stripslashes($user_login)); ?>" /></label>

            <label><?php _e( 'Password', 'buddypress' ) ?><br />
            <input type="password" name="pwd" id="sidebar-user-pass" class="input" value="" /></label>

            <p class="forgetmenot"><label><input name="rememberme" type="checkbox" id="sidebar-rememberme" value="forever" /> <?php _e( 'Remember Me', 'buddypress' ) ?></label></p>

            <?php do_action( 'bp_sidebar_login_form' ) ?>
            <input type="submit" name="wp-submit" id="sidebar-wp-submit" value="<?php _e('Log In'); ?>" tabindex="100" />
            <input type="hidden" name="testcookie" value="1" />
        </form>

        <?php do_action( 'bp_after_sidebar_login_form' ) ?>

    <?php endif; ?>

    <?php /* Show forum tags on the forums directory */
    if ( BP_FORUMS_SLUG == bp_current_component() && bp_is_directory() ) : ?>
        <div id="forum-directory-tags" class="widget tags">

            <h3 class="widgettitle"><?php _e( 'Forum Topic Tags', 'buddypress' ) ?></h3>
            <?php if ( function_exists('bp_forums_tag_heat_map') ) : ?>
                <div id="tag-text"><?php bp_forums_tag_heat_map(); ?></div>
            <?php endif; ?>
        </div>
    <?php endif; ?>