BuddyPress.org

Did you find anywhere in your googling where a blank page means php errors and you should check your error logs?

Part of the problem might be running BuddyPress in a subdirectory. We use some tricky URI parsing to dynamically trap and trigger the pages that don’t actually exist. To do this, we count the slashes and put the slugs in the “correct” positions, which in your case are one level off.

You could .htaccess your way out of this by redirecting, but your best bet is to install it at the root of your site.

For those only having the trouble with /register and /activate, make sure you have member registration turned on. Since it’s off by default on single site WordPress, that has gotten me a few times.

You’ll also need to make sure you have Arabic installed for WordPress, and if using multi-site, Arabic must be set as the site language in site wide settings.

It sounds like you may have a hook sequence firing issue. In other words, your added action function might not be getting fired. This could be an issue with your code or even the BuddyPress code.

You can download my plugin WordPress Hook Sniffer to see if that might be the case. It takes awhile to figure out how to use my plugin but the two articles I wrote should guide you through the process.

Has anyone solved this yet? I am still getting this error.

I can configure, add BuddyPress, activate plug in and themes, etc.

Clicking on http://computername.corporatedomainname.com/wordpress-mu/ (where I am installed) lets me go to the BuddyPress home page (and very exciting it is too). Then clicking on the “Members” tab give me a http://computername.corporeatedomainname.com/wordpress-mu/members/ and

“Object not found!

The requested URL was not found on this server. The link on the referring page seems to be wrong or outdated. Please inform the author of that page about the error.

If you think this is a server error, please contact the webmaster.
Error 404?

I’d try using a SMTP plugin:
https://wordpress.org/extend/plugins/tags/smtp

@scwcreative Set permalinks to other than default and save

And what did support@apollohosting-inc.com say when you contacted them?

This could have been caused if you installed WP/MU via simplescripts, fantastico, etc. Delete previous installation including htaccess file generated and wp-config (if MU) and drop database tables.
Do manual upload of WP or MU via FTP or cpanel and install.
Go to dashboard > Settings > Permalinks and run it.
Do FTP/cpanel upload of BuddyPress plugin.
Activate BP plugin and go to BP settings page to enable components.

If you need a sidebar widget in author’s blog then you could use
https://wordpress.org/extend/plugins/bp-profile-widget-for-blogs/

Ok, I had the same problem, and I got that “Mail From” plugin and it works as far as the From line coming from the community name instead of from “WordPress.” However, emails are still going to the spam folder. Is there no way around this at all?

Thanks to Sarah Gooding, I found this plugin which mostly works with WPMU 2.9.2 and BP 1.2.3: http://www.thinkinginwordpress.com/2009/10/autoactivate-users-and-blogs-at-buddypress-signup/ Only problem is that it still sends the activation email despite the email already being active.

My hope is to incorporate the code from Andy so that it will work with both WPMU and WP and then make it so neither one sends the activation email.

If anyone has ideas why it’s sending the activation email in WPMU, I’d appreciate any help. Seems like it might be a priority issue, but I haven’t yet figured that out.

“Automattic needs to go back to the basic building blocks – users, posts, comments – and make sure they are solid, remove redundancies etc. And then develop different ways to connect those elements and display the data in different user interfaces; blog, social network, forum, microblogging, social bookmarking, etc“.
Just to be clear, on this account I agree wholeheartedly. Forum functionality is one thing, but a separate script all together to make a forum when you’ve already got WordPress and BuddyPress put together with their respective building blocks at your disposal, that seems like a flawed development practice to me.

With WordPress, 3.0 and its custom post types in particular, we’ve got all we need already. This is what I tried to get across on my ‘rethinking posts’ thread.
https://buddypress.org/community/groups/miscellaneous/forum/topic/re-thinking-posts/

@twodeuces – Nice job! It’s always nice though to attribute the original work. Also, it should be quite easy to add your admin menu to the existing BP admin menu without waiting for the 3.0 merge.

@3sixty (“The irony of “BuddyPress shouldn’t be about forums”, and “if you want a forum, don’t use BP” and “bbPress is a parasite in BP…” is that the FORUM is the center point of activity here on buddypress.org”)

There’s nothing ironic about that. Traditional forums are very useful, but if you want a traditional forum you can install PunBB or bbPress. The point is that bolting a forum onto a social network derails the social networking structure. Mixing forum and social networking is the cause of a lot of the confusion and interface problems that this thread is about.

Social networking sites (Facebook, LinkedIn, etc.) imho evolved from traditional forums; they are a next generation paradigm in how to structure a web community, with more emphasis on individual members, less on forum topics. That’s also why I keep complaining about anonymous usernames and the underdeveloped member management in BP.

It has been depressing to see in recent months that people who primarily want a traditional forum are taking over Buddypress, pushing it back into the older forms. Mixing these different approaches to structuring a community does not make it a more versatile product. It’s the kitchen sink. It’s becomes an unwieldy mess.

As explained earlier in this thread, you can get forum-like functionality following existing Buddypress/Wordpress structures. You can display blog posts and comments in a forum structure. You could probably do it in a template. There is absolutely no need to bolt on an external forum, adding new database tables and functionality that partly overlaps/clashes with existing functionality.

Automattic needs to go back to the basic building blocks – users, posts, comments – and make sure they are solid, remove redundancies etc. And then develop different ways to connect those elements and display the data in different user interfaces; blog, social network, forum, microblogging, social bookmarking, etc.

Wow, amazing analysis by Boone… I really “get it” now. Andrea_r also has a good point though that WPMU is distributed in other ways that are meaningful and powerful. I think the author’s comment was just speculation, and limited to a project called “DiSo” that was apparently designed to integrate with WordPress; not sure if DiSo worked at all with MU.

The part about that quote that resonated with me is just the idea of “WP wasn’t designed from the ground up to host BP.” When I’m writing something for BP, I always feel like I’m gaming WordPress to do something it was not really designed to do. So I’m writing code that somehow has to play nice with the host, WordPress, which is awesome in its own right – but what I’m really trying to do is build a social network. So it would be more logical to me to say, “OK, here’s my BuddyPress network. WP is really good at XYZ, so how can I adapt *WordPress* to meet my BP needs?”

“1) They tried to add on to WordPress, a project which was not designed from the ground up to be a distributed network.”

okay, here’s what I don’t get – isn’t MU a distributed network?

Is your problem that the javascript isn’t loading?

The best way to include the script is with https://codex.wordpress.org/Function_Reference/wp_enqueue_script.

You could also just edit the header.php file of your theme to include a script tag.

“1) They tried to add on to WordPress, a project which was not designed from the ground up to be a distributed network.”

This really feels like the “elephant in the room” every time I visit my wp-admin panel. My BuddyPress admin menu keeps growing and growing, disproportionate to the WP-specific admin menus.

I keep waiting for the discussions to start on how BP is “outgrowing” WP. I guess that happens when the limitations of WP start to outweigh the advantages, such as all the great WP functions we get “for free”. When you think about it, it is a little weird – for example, how blogs and forums are integrated with BP in such different ways and don’t really “talk” to each other in a meaningful way. The whole idea of “like” and “favorite” and “report” buttons that work on one content type but not another. Etc.