BuddyPress.org

I found a tutorial by Spencer Forum that had step-by-step instructions that I think cleared up my issues.  I was able to change the slugs and I think things are working correctly in the forum area now.  Here is his tutorial which will hopefully benefit others:  http://www.youtube.com/watch?v=M8mh3f6Vzbo

Now I’m having problems with registration.  I opened it up so that a few of our members could register and I could test what happened.  Two of them couldn’t access their profiles and kept getting the wordpress log in page.  Spence’s video also addressed some of that and I hope that the changes I made will fix that.  But, more importantly, I have been looking for a plug-in that will allow people to apply for entry to the site.  This site is going to be a free forum for our membership organization.  The plug-ins that I have seen are for paid memberships and have a lot more weight than I want (configuration with Pay Pal, etc.).

I did install the membership plug-in which hopefully fixed the problems I had with the two members, but that doesn’t offer any kind of registration options.  I would like it to operate like private Facebook groups: apply and get let in.

No, it definitely needs the wordpress added on the end… Without a logcat there’s not much I can say. Can you try accessing the plugin page http://www.site.de/wordpress/wp-content/plugins/bpxmlrpc/bp-xmlrpc.php with a browser?

Oh, I think I forgot to mention that the plugin needs to be in the directory named bpxmlrpc as per the above URL… Oops.

Resolved.

Indeed, the child-theme functions php is called before the parent-theme functions php
https://codex.wordpress.org/Child_Themes#Using_functions.php

The function `bp_dtheme_setup()` where the button is added in bp-default is made pluggable as I’ve just learned that it should be 😉

Therefore, the solution is to override the function in child-theme functions php.

That is, copy the function `bp_dtheme_setup()` from bp-default/functions php to child-theme/functions php and comment out the lines
`
if ( bp_is_active( ‘activity’ ) )
add_action( ‘bp_member_header_actions’, ‘bp_send_public_message_button’, 20 );
`

Hope it helps someone!

Cheers
Mort3n

Yes I am delinking in a child theme and then linking to the Google repository, because the version rolled with WordPress, particularly jQuery UI, is broken up into separate pieces and is missing a few at that, whereas my own coding requires the full library and is much easier to have it all on hand instead of little pieces, plus I need the latest version.

I would say that in one way or another, updating WordPress and it’s plugins is a must.

Yes I am using the newest version of WordPress…

I am using a theme called Valor from Themeforest.net (http://themeforest.net/item/valor-responsive-wordpress-theme/full_screen_preview/3741916).

I created a Menu item called “Dream Bank”. I want site visitors to be able to come to http://www.glassworksdream.com and click on the “Dream Bank” menu item. Then, I want them to be asked to register for the Buddypress section of the site.

When I installed and activated Buddypress, instead of that happening, the Valor template was deactivated, and Buddypress became my site template.

Gwen

OK, here’s what I can offer in the way of isolating the problem.

I wanted to see if it was my server or any changes I made to the theme. It was not!

I went ahead and did a completely fresh restall of everything. When i got wordpress multisite with buddypress working again, I did not have a problem with editing the topics.

Then I brought in my custom theme files: Again nothing was off, everything worked as it should in editing topics.

It was only when I brought in my database of existing users and content did I get the 404!

So it is something wrong in the database.

What in buddypress would cause topics to 404 based on something off in the database?

Yes to the settings.

Permissions: Ok there may be something here. I can access the ftp of the live site host and I just noticed something.

I can give the uploads directory all permissions (write read execute: 777) however wordpress will create a dir for a new user avatar (uplaods/avatars/59 for ex) but it cant upload files inside it. Apparently any directory I create with the ftp user has a different owner than the directories created by wordpress itself and even though permissions are set to 777 wordpress is giving me a write permission error when trying to upload any new avatar.

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

@mercime

Sorry for delayed response. I thought the thread was dead. Nevertheless, thanks for your directions.

It seems I chose the wrong words to describe my problem. The problem was “after the compatibility process is over, the site doesn’t look 2012-ish, with bp-default styles in BP parts.” After the compatibility process is done successfully (which I did), the theme “works fine”, but doesn’t look fine. So in other words, how to make the BP part look like 2012.

Both the BP-compatibility-pack approach and your approach worked fine, except, the theme CSS is (understandably) the same (bp-default). I ended up modifying the bp.css to make it look like it belongs to 2012 theme. I also “hard-coded” (so to speak) the BP specific changes in my child theme itself (added the bp-template-pack.php part with some modifications to functions.php), and a few minore changes to BP templates, so that my child theme is BP-compatible out of the box (no need of plugin or external CSS). Will upload the child theme somewhere and post a link here as I get to it.

Thank you @mercime for your help.

For those of you interested I’ve found a temporary solution that works perfectly:

`// When a User Creates a New Blog, Force the Administrator Role (bbPress Bug Temp Fix)

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 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.

Source: https://wordpress.org/support/topic/how-do-i-change-the-default-administrator-role-to-author-for-new-users