Here’s a temporary solution that worked for me:
`function bp_fix_blog_role($blog_id, $user_id) {
add_user_to_blog($blog_id, $user_id, ‘administrator’ );
}
add_action( ‘wpmu_new_blog’, ‘bp_fix_blog_role’, 10, 2 );`
Just drop this in `mu-plugins` if you want. You can change “administrator” to whatever role you prefer. This function runs immediately after the blog is created, so it will probably solve your problem.
Just drop this bad boy in your `mu-plugins` folder and you’re good to go. If you want a different default role for your users, just set “administrator” to whatever you want (editor, author, etc.). The beauty of this function is that it runs immediately after the blog is created, so it will fix any issues you have during blog creation.
Turns out my issue was with bbPress. If I deactivate bbPress there are no problems with creating a blog through `/blogs/create/`. I know that more recent versions of bbPress (I’m running 2.2.3) have created their own user roles, perhaps @JohnJamesJacoby can help me understand this issue.
I’ll try a few things and then report back here if I find a solution.
I noticed after posting this yesterday that the form on the registration page (which works) is hard coded into the form, whereas the one on the `/blogs/create/` page is generated by the `bp_show_blog_signup_form();` function. Is it possible that the different functions that are run upon submission (on signup vs. blog creation) are be different enough to make this error occur?
I got it working. Just thought I’d post here to update.
In the registration form (whether you’ve copied/pasted it or created a custom file to call), you need to do two things:
First, change your opening “ tag to this: `<form action="” name=”signup_form” id=”signup_form” class=”standard-form” method=”post” enctype=”multipart/form-data”>`
Second, add this php before the form: `global $bp;
if(empty($bp->signup->step))
$bp->signup->step=’request-details’;` (Wrapped in php tags, of course.)
@frank13 thanks for the suggestion, the FireFox inspection tool is similar to one in Firebug but does help, thank you. As a result of using the inspect tool I added/edited the following classes as such:
li.friends.friendship_created.activity-item.mini a img {
display:inline-block !important;
}
li.friends.friendship_created.activity-item.mini div.activity-content div.activity-header p a img {
display:inline-block !important;
}
Unfortunately, this does not seem to have solved my problem.
That is a possibility. Originally, what I did was install the BP Template Pack plugin to get the files and html structure worked out. Then I copied `bp.css` from the plugin, placed it at the end of my `style.css`, and checked “Disable Template CSS” in the plugin settings (this is so that my custom styles did not disappear upon plugin update, etc.).
I will copy the “BuddyPress” section of the `default.css` and replace mine and re-customize it to see if that solves my problem.
…Good thing I kept a separate log of all my custom changes…
