BuddyPress.org

If you’re using standard WP, you can’t.

—

If you’re using WPMU, login to the admin area, navigate to “Site Admin > Options” and under “Allow new registrations”, make sure “Enabled. Blogs and user accounts can be created.” is selected.

If you’ve done this, when you’re logged in, navigate to your blog directory (example.com/blogs) and click on the “Create a Blog” button.

I have this same problem – I know WPMU is sending me emails for other things, but BuddyPress related items do not get sent.

On new user registration, the final part of the registration process says “You have successfully created your account! To begin using this site you will need to activate your account via the email we have just sent to your address.”

No email sent to either new user or admin, and new user isn’t in list of users in admin panel.

Perhaps I’m unclear, but why would it be preferable to keep the navigation bars separate by default, as opposed to just adding buddypress tabs to one main navbar? This isn’t the way that the default theme works, and the UI problems of having two home buttons are significant…

I noticed another CSS tweak too: there is a float:left applied to #sidebar .padder a, which is floating the links for “create an account” in the sidebar.

You are correct about the subdomain.

I run the root domain as the install of wpmu. Wpmu is installed in the root directory of the root domain.

I then create customer accounts off of the root domain, like customer1.root.com

This allows me to run a system kind of like wp.com does. I only have to manage one install of wp.

The customers don’t know they are actually on a subdomain.root.com because I use domain mapping.

(well my customers know, I don’t hide it, but the website visitors have no idea which is all they care about)

So I went into my shawngaffney.root.com blog as though I was a customer and tried to setup a group blog.

That is how I ended up with shawnsfriends.shawngaffney.root.com when I created the group blog from a subdomain site.

When I went into the root blog and then into a group and created a group blog, it worked. it became testblog.root.com as it should.

I’m only guessing, but I think the ‘create blog’ function is grabbing the url of the blog from the db?

It’s probably grabbing the subdoman.root.com url instead of the root.com url…..

Maybe it’s as easy as one change url change in the code?

I may have an idea of how to get this to work with domain mapping.

Obviously the groups blogs plugin needs to reference the root.com url for proper path creation –mentioned above.

But…. if you also save the url of the subdomain site that the user was on when the blog was created.. then I can solve domain mapping issue.

by having the ‘true’ domain address of the group that created a blog, then it’s just a matter of comparing that value to the domain mappings table?

just a few ideas

Hi all,

I was actually having this same issue with a site I’m developing, and removing the space from the user_nicename field worked sporadically through the BP “My Account” menu. I’ve created another dummy account or two and it appears they go through a set of checks that the initial user account doesn’t, but removing that space will work.

An interesting point, if you still can’t get the menu to link properly, try logging in as a non-admin user. I did that after testing for a few hours logged into the admin account, and all’s well!

Cheers,

Graham

Something’s wrong because the admin bar is not showing up at the top of the screen either.

What theme are you using? Is there anything in your web server error log?

create a child theme…. easist way is to issue @YOURDOMAIN.COM email accounts to the premium user and then have those folks have special priviledges..

Found a huge problem with this (or though it seems)

Whenever you create an account, the link to activate your account in the activation email won’t let you it through because of the redirects. Anyone else having this problem?

Thanks for the help and the great plugin. A small but mighty one!

@hnla how did you deactivate blog-signup? If I use that option in the backend, registration does not accur at all. If I choose “only Useraccounts” they cannot create a blog in a second step (no new blogs at all)

I’m using wpmu 2.9.1 and buddypress 1.2.1. I’m having this issue after the upgrade to 1.2.1. I can create users in the back end, and they can create posts and pages, but if they sign up through the /register/ page, then they do not have an “Add New” option for posts or pages, even though the user is an Administrator on that blog, and has activated their account.

I just upgraded to BP 1.2.1 (from BP 1.1.3) last night and noticed that right away. In fact I created a brand new user, logged in as them, and then deleted my account… only to find out that I wasn’t logged out by the deletion. So I manually logged out… and then logged back in as the deleted user. All of my activities on the site had been erased but the user was definitely still there.

I had to go into the admin dashboard and delete the user from the WordPress MU Users list.

So I guess this is a bug then?

If you don’t want to get into the database, the simplest way would be to create another administrator account, logging in as the new admin, and deleting the user named admin.

PS: @hnla Buddypress now works with regular WP, too.

I’m somewhat at a loss as to why people debate this issue or try and state it’s a WP issue as logically that doesn’t make sense?

As jfigura posts this is an inherent problem, I have it on a production install and it must be hugely confusing for users, and yes the only approach so far has been to modify the text and remove the WP password from the confirmation emails.

Further testing points to the initial blog registration as being possibly the issue:

Clean install of WP MU 2.9.1 & BuddyPress 1.2 no significant further plugins activated.

Test Condition 1:

WP MU with BuddyPress disabled – admin options -> Allow New Registrations ->’Only user account can be created’

Register new user

Receive confirmation email of new registration along with Activation key

Activate registration

Receive second email with account username and pass

All as expected!

Test Condition 2:

WP MU with Buddypress activated – admin options for registration still set as ‘User Account only’

Register new user

Receive confirmation and activation key

Activate registration – screen message stating ‘you can now login with user name and password you set’

No further emails sent!

Test Condition 3:

WP MU BuddyPress still activated – admin options -> Allow New Registrations -> ‘Enabled. Blogs and user accounts can be created.’

Register new user as well as a blog!

Receive confirmation and activation for account and new blog

Activate registration – screen message ‘you can now login with password you set etc etc’

Receive further email from WP! (copied below)

Dear User,

Your new *********.co.uk Blogs blog has been successfully set up at:

http://eggs.********.co.uk/

You can log in to the administrator account with the following information:

Username: eggbert

Password: 5f112917

Login Here: http://eggs.**********.co.uk/wp-login.php

We hope you enjoy your new blog.

Thanks!

–The Team @ ********.co.uk Blogs – Sent via Site Admin options email

So having new accounts and new blogs enabled at initial registration triggers the sending of the ‘Welcome Email’ noted above.

clearly this is confusing as it contains the WP generated password.

Why is it that BP registration doesn’t disable / override the WP registration completely? To my mind this IS a BP issue, but I may very well be wrong on that score as I don’t profess to have a deep understanding of the core coding involved here.

On a sidenote:

Testing this and the slightly odd behavior of ‘Allow New Registrations’ where option for ‘only logged in users can take a blog’ actually seems to prevent all registrations. It occurred to me that on a social community ,and from our experience, blogs are not necessarily what users register for and that I would prefer the option to have a blog be only available for registered users from their account options. what actually happens is that registration is disabled completely! Not the effect I desired. I realise this IS a WP MU issue but is simply daft behavior and that set of options needs to be re-worded to be a lot clearer as to what it really does.

It would be great to be able to restrict blog signup to users already with account set up and remove, completely, the option to take a blog on initial signup, I have done this by simply scripting out the option / section for registering a new blog in BP register page but feel it’s not the best approach?