BuddyPress.org

You can read more about this here:

https://trac.buddypress.org/ticket/787

Try the custom filters for BP plugin – https://wordpress.org/extend/plugins/custom-profile-filters-for-buddypress/

Allows you / your users to be more prescriptive about what BP ‘auto-links’. Don’t think it will completely stop BP auto-linking some things – though you could, if you wished, tell the plugin to exclude ALL fields from being auto-linked.

You / users can also use the square brackets ‘[ ]’ in profile fields to specify words or phrases they do want linking.

The plugin’s pretty handy for specifying fields like web site / twitter that shouldn’t be auto-linked.

It means more code in buddypress-core. It might not be a lot, but even small things add up after a while. All I’m saying is that it should be a theme option and not bp-core.

For anyone concerned, I encountered the same problem reported by outolumo and can’t happen to use the workaround. I submitted to TRAC…https://trac.buddypress.org/ticket/1356. Will see what happens!

you are most welcome

I am glad your site is working now.

I am not sure about facebuddy theme though.

well,follow these steps

1.Get a backup of bp-themes(I hope you already did it) and delete it from wp-content,there should be no folder named bp-themes

2.Now copy the bp-sn-parent and bp-default from the buddypress/bp-themes(the new buddypress plugin you have downloaded) to wp-content/themes

3.Go to wp-dashboard->Site Admin->Themes and enable bp-default

4.Go to appearance and activate bp-default ,hopefully ,you site should return back to normal.

You may need to do some extra styling on the child theme to get them to look right with the buddypress elements. But the buddymatic framwork has most of the work done for you.

Not sure about the php errors – depends on what they are. Ron’s been testing the Early Morning child theme as well.

have you removed bp-themes folder from the wp-content

The original poster has since deleted ther account, and as there are several solutions in this thread, I’m marking it as resolved.

Figured it out.

To anyone wondering, just change “Template: thematic” to “Template: buddymatic” in the style.css

I haven’t gotten any of the child themes from here http://themeshaper.com/thematic/ to work properly with buddypress. They all seem to have formatting errors, and sometimes php errors.

Should they all work fine? Am I doing something wrong?

Sorry for the triple post.

Does the Kubrick / K2 theme allow users to add a logo to it’s big blue header?

Also, how does letting an admin upload a logo (as a custom config option) mean more coding? The idea is that it would mean zero coding. You would go into the theme settings, click a button, upload a graphic, done.

And trust me… CSS is easy for me and you… but as a developer… I’m happy when a client can just figure out how to log in and write a post! Most people can’t handle anything more complicated than email and facebook.

hi Olive

have you checked this thread.Hopefully this should help you as your buddypress is not on the root domain but on sub blog.

https://buddypress.org/forums/topic/can-i-run-non-bp-theme-on-tld-and-bp-theme-on-subdomain-all-on-same-wpmu-install

as It seems from your error description it is bp-genealogies theme.

try deactivating this theme ,and activating the default buddypress theme.Is the error still showing ?

Well,Just to let you people know,I had written this plugin for buddypress 1.0.X version and It works upto buddypress 1.0.3.I last tested it(on request of one of user) for buddypress 1.0.3+wpmu 2.8.4a and It was working.

So hopefully,It will solve your issue if you are using buddypress 1.0.3

But again,because of security reasons It is strongly recommended to upgrade to most recent version of wpmu+buddypress.

(I’m going to try to be helpful rather than just telling you to go elsewhere. I want Buddypress to grow, and users helping users ought be part of that. I’d also like the forum here to be a useful resource. So many threads at mu.wordpress.org are just cries for help with zero replies. That sucks.)

wordpressfan, I’d probably approach this using Roles. I’ve never done it, but you could set the Dashboard user default role in Site Options to ‘Inactive’. That would allow you to monitor signups, and approve as necessary, I’d imagine. As long as users know that there is a process in place where they have to wait for approval. There are plugins out there that allow you to create custom roles, too, but I’ve never used them.

In terms of the registration emails sent to you as admin, this is also a WMPU thing, not on the Buddypress end. I’m sure I’ve seen plugins that allow you to edit these, but I can’t find them for the life of me. If you’re comfortable with hacking the WPMU core (and rehacking after updates), you can find the place these emails are generated in

function newblog_notify_siteadmin

in wmpu-functions.php in /wpmu-includes

off the root of your WMPU install.

Without knowing anything about the paid plugin in question, it’s pretty hard to make a guess. You might want to contact the plugin author, since I assume that if they made you pay for it, they offer support.

I note that it’s not one of the ones they explicitly say are Buddypress compatible, though, so you may have issues.

It can’t be a complicated bit of code, though, so I’d just open it up and see what’s in the code, and hack in the URL necessary. You’ll need to get the currently logged-in user from BP in order to build the URL of their profile, page, though, because their username is part of the URL.

That’s more than I know how to do off the top of my head, but I’m sure someone with more knowledge of BP coding can help you there.

@Jeff Sayre

Thanks a lot for your information, because of it, I have just upgraded to the new version, and (again) everything looks nice on my BuddyPress site.

I have the same problem but it’s not so much the issue of spammers coming to the site than non-working defense measures.

I have failed to find any reasoning behind the dropping of wp-signup.php and replacing it with /register (what’s the .php file for that btw?) in BuddyPress but that’s the reason for a lot of spam problems.

When you install a number of WP and WPMU anti-spam plugins, they add their own features to the signup page – which in WP and WPMU is wp-signup.php.

Now as it has been pointed out in about all spam-related posts, people even delete that file with no success to the spam issue. This confirms the problem that I believe could reduce the spamming significantly:

– WP and WPMU anti-spam plugins do *not* have any affect on the BuddyPress /register page.

Is it because some hooks are missing? I’m not sure as I’m not that deep into it but I think so.

My request to solve this problem and address the spam issue:

– either BuddyPress will return to use wp-signup.php, or

– makes sure that anything added by plugins to wp-signup.php is also added to whatever page is serving the /register URL.

No matter hashcash, captcha or security question (all nice and working (with wp-signup.php) plugins), they can’t add their stuff to the BuddyPress signup page.

Why I don’t use wp-signup.php manually (like redirect URL to there)? Because it’s a blank page (told to die somewhere in BuddyPress if I remember right).