BuddyPress.org

@Hollosch I turned Andy’s code and my little addition to disable the email at activation into a plugin. I’ve posted it to my blog for now: http://www.crashutah.com/blog/juanchito/2010/05/12/buddypress-disable-email-activation-my-first-buddypress-plugin/ I’m still waiting for the SVN access to be able to add it to the WP plugin repository.

Also, right now the plugin only works for standard WP. I’m still working on disabling the activation email for WPMU, but have to figure out why it’s sending the email still.

Closing thread as per @paulhastings0 comment.

BuddyPress needs groups and forum in the URL so as to understand the URL properly. You can’t remove them, but you could rename them.

Try this FB plugin:
http://www.justin-klein.com/projects/wp-fb-autoconnect

Read the plugin’s instructions!

It’s a known bug:
https://trac.buddypress.org/ticket/1445

Keep watching that ticket for further details.

I am getting the same error msg, but it is returned when trying to upload any kind of avatar:

Catchable fatal error: Object of class WP_Error could not be converted to string in /path/to/wp-content/plugins/buddypress/bp-core/bp-core-avatars.php on line 281

Line 281 is:

$bp->avatar_admin->image->url = str_replace( WP_CONTENT_DIR, BP_AVATAR_URL, $bp->avatar_admin->image->dir );

I had previously had trouble with avatar uploads and found the advice on changing the small code segment “if ( !$path = get_option( …”

That worked sort of — couldn’t get avatars to align without forcing some things into the various loop php files — but now I can’t get any files uploaded.

The change is that I installed the newest beta of WP 3.0 so I don’t know if this new “catchable error” report is of any assistance at all.

I had found some similar references, not specifically to BP and avatars, but people having problems uploading files into posts and I recall some references made to ms-sites.php.

I have only one site, the base site, build is configured to use folders not subdomains, and I am seeing lots of problems with pathing to the elusive uploads directory.

I do know that I was not getting a BP-related error until I upgraded my install from MU 2.92 to Beta 3.0.

@scwcreative Set permalinks to other than default and save

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

Actually, you’ll want to ask that in the plugin’s forum here: https://buddypress.org/community/groups/bp-album/forum/

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.

@twodeuces I’m not sure that the change of menu will matter with WP 3.0. The various menus are still the same from what I’ve seen.

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/

I haven’t checked the source fully, but it looks like the Group Documents plugin only checks files by extension and not something like the mime-type. So there is a chance that someone could do something “dodgy”; though if you have a decent user base, you won’t have to worry about it.

@PeterAnselmo – ping!

Integrate with Cubepoints then you’re singin

Do you have any errors in the log files?

I assume that you are passing data into your function of the proper type. If so, then the next issue is to determine if the save method is receiving the data and if it’s provided in the way in which it expects. The example save method in the Skeleton Component is coded to accept all integer data and no string data. This is why I asked if you are passing the proper data type to the method for each field.

Your log files and some custom debugging strings should help figure this out pretty easily.

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

@twodeuces the instructions have a typo: … if (function_exist( …should be … if (function_exists( … else (as you would know but for anyone searching for this … ) following instructions results in Fatal error: Call to undefined function function_exist() …

Thanks for sharing! BG

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

@Dwenaus Great stuff, I’ll check it out! Let me know if you integrate custom rankings, that would be sweet!
Regards
Ross