BuddyPress.org

It’s a bit old now, but have a look at https://trac.buddypress.org/ticket/1150 if any developer wants to attempt this.

Then ask your host

Looks like you’ll need to contact your web host to increase your memory limit.

Have you checked your error log to see what is causing the white screen of death?

Change your theme on blog 83 to something else, deactivate any BP-related plugins on blog 83.

Deactivate BP entirely. Delete the BP_ROOT_BLOG line in wp-config.php, activate BP sitewide, activate a BP theme on blog ID 1.

What happens?

@ Andrea_r

Yeah I realise that now after having a play with it

I inadvertently asked a similar yet different question in another thread, perhaps it could be considered a half way for this also. It involves using the domain map plugin and then adding the following to the wp-config.php:

Allow BuddyPress to function on multiple blogs of a WPMU installation, not just on one root blog:

define ( ‘BP_ENABLE_MULTIBLOG’, true );

It wouldn’t give each site its own buddypress, but it would let you share the one install.

I’ve not actually tested all this but it seems logical.

I know there also use to be a plugin that allowed you to be an oid provider, the WP directory shows its last update as 2007 though so not sure how viable an option that would be.

https://wordpress.org/extend/plugins/mu-open-id/

+1

Do you have BP activated on one blog or site-wide?

If BP is activated on one blog, deactivate BP on blog 83 as well as the BP-enabled theme from blog 83.

Redefine the BP root blog to 1. Activate BP on blog #1 and enable the default BP theme.

@sueme

Don’t bump similar threads.

You already replied to this thread:

https://buddypress.org/forums/topic/permalinks-setup-with-wp-intalled-in-subdirectory-and-indexphp-in-root

Please leave follow-ups in that thread.

Increase your PHP memory limit then.

Read this:

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Increase your limit to 128MB or higher.

I think that “like” has legs…we just need to figure out a better use for it. Perhaps a “most liked” widget?

Personally, I would love to see “like” expanded to include blog posts within MU, making it function like an internal tweet, promoting good posts in the activity stream.

Same with “Favorites”

@Djsteve

This seems like a buddypress flaw, not a wordpress or mu issue.

Perhaps if buddypress can’t read the wpmu blocked domains, maybe BP needs it’s own domain banner.

This has been a wordpress mu issue for a while off and on.. I discussed an idea about at mu forums:

https://mu.wordpress.org/forums/topic/13982

[blockquote]

I too have noticed that even putting domains in the block list seems to not stop future registrations. Here is a thought of mine.

MAYBE a spammer actually signs up 100 new accounts, and then only activates one a day. So even though we have added his domain to the ban list for signups, he still has 99 more that have been signed up, but not yet activated?

If this is the case I would like to see MU add core code that checks to see upon activation if the domain they originally used to signup has since been banned, and then prevent them from activating if it has.

Just a thought, not sure if this is the case – but it may be worth looking into.

[/blockquote]

It was suggested that I add this suggestion to the trac, ( https://core.trac.wordpress.org/ )

but I really don’t know how to use that thing…

not sure that it is a buddypress specific issues, but I DO believe that the spammers are looking for buddypress phrases when compiling their lists of sites to hit…

@kunal17

I’m seeing the same thing you are….

Is there any way to get buddypress registration to reference the banned domain list?

First, I just found a small bug and fixed it in the trunk – you just need to update the file: bp-forum-extras-activity.php

Second, make sure you add the theme edit (detailed on forum extras wp-admin page)

The comments appear directly underneath the post which has the activity. It pulls in all replies for the given post (so threaded). It will work for any backdated activity comments – whatever it can find for the given group_id and post_id (item_id)

http://files.etiviti.com/misc/buddypress/bp-group-forum-topic-post-activity-1.gif

http://files.etiviti.com/misc/buddypress/bp-group-forum-topic-post-activity-2.gif

http://files.etiviti.com/misc/buddypress/bp-group-forum-topic-post-activity-3.gif

http://files.etiviti.com/misc/buddypress/bp-group-forum-topic-post-activity-4.gif

I’m having 300 spam registrations a day and having to mark them all as spam manually 15 in one go in the user list. The plugin wordpress Hashcash (updated today to 4.5.1) should now work for BuddyPress registration but it stops EVERYBODY from registering.

David Lewis, one week later, is your solution still working for you?

@Peterverkooijen

Would it be very complicated to write a plugin that checks if the entered username exists in the other three databases? And then verify the user’s password by checking in that same database? And then enter that user’s data, including username + pass, into the ‘New Community’ database?

This could be done but the issue would be security as you are grabbing data across domains. I am not a big fan of pushing and pulling your members’ most important data across domains–that data being usernames and passwords. It exposes your site in a potentially dangerous way. Implementing security measures would be essential.

The best option is to allow your users two choices in accessing your suite of sites:

1. A separate account for each site–which means you do not need to do anything different

2. A single sign on (SSO) solution, be it OpenID, FOAF+SSL, or even the Facebook Connnect Plugin

The Web is slowly moving toward SSO as a standard option for users. In my opinion, this is the way to go.

I’m currently running an active site, and having followed the instructions in https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory I’ve got all my files in a mysite/wordpress file with everything in the wordpress folder but the index.php and .htaccess files in the home directory. that’s given the whole of my site a mysite address rather than a mysite/wordpress address.

This sites been up a while and works well, but I’m having trouble getting BuddyPress to work on it. Whatever I try, I seem to end up with half the site still on mysite (whilst everything in mysite/wordpress is coming up unobtainable); or half the site on mysite/wordpress (whilst everything in mysite is unobtainable).

There’s quite a bit of activity on the site, so I don’t want to start from scratch, but I would like to get BuddyPress on it. Has anyone worked out how to do this yet?

I tried the solution at https://buddypress.org/forums/topic/permalinks-setup-with-wp-intalled-in-subdirectory-and-indexphp-in-root?replies=23#post-45920 (which is marked “Resolved”) but it didn’t work for me.