BuddyPress.org

The password in the welcome email, if you restore it…, is generated by this file in wpmu-functions.php:

function wpmu_welcome_user_notification($user_id, $password, $meta = '') {

global $current_site;



if( !apply_filters('wpmu_welcome_user_notification', $user_id, $password, $meta) )

return false;



$welcome_email = get_site_option( 'welcome_user_email' );



$user = new WP_User($user_id);



$welcome_email = apply_filters( "update_welcome_user_email", $welcome_email, $user_id, $password, $meta);

$welcome_email = str_replace( "SITE_NAME", $current_site->site_name, $welcome_email );

$welcome_email = str_replace( "USERNAME", $user->user_login, $welcome_email );

$welcome_email = str_replace( "PASSWORD", $password, $welcome_email );

$welcome_email = str_replace( "LOGINLINK", wp_login_url(), $welcome_email );

...

So I guess you should replace $password with something else from BP? Or maybe add $bp as global (whatever the hell that is…)?

EDIT: Adding $bp does nothing.

BTW, the wrong password in the welcome email is the same number of chars as the password that was entered, so I assume it’s an encryption issue. Unfortunately the ‘forget password’ function resets the password, it does not send the stored one. That’s probably more secure, but I don’t see where else I could find code that retrieves the stored password.

Excellent point. Not all is lost but I will take this opportunity to provide some feedback to @jjj and @apeatling re 1.2 in it’s current state

1. I get the use of the Twitter @ metaphor and adding “mentions” to the filters. Cool. BUT, it introduces a potential UI snag for users. Throughout 1.2 you make nice use of Display Name which users will become accustomed to and identify with. Now, you are identifying users by their user name as well (mixing metaphors, so to speak) as in ->

John Doe

and

@jdoe

Given people’s tendencies to use whacky usernames, thee is a big risk of confusion when both start popping up around the site. Not sure what the solution is but I think it’s not a trivial point, imho.

2. Now that the wire has disappeared and along comes the concept of “Send Public Message” (I get it) let’s look at what vehicle we’re making use of and what it may mean to users. As it currently stands in 1.2, to “Send Public Message” you click that button on someone’s profile and you are taken to your own Status Update field with an @username filled in.

a. the cursor is highlighted just before the @username not after (don’t forget to include a space) – this will only cause people to write the pubic message and push the @username to the end of the message. clunky

b. You’ll probably need to include a @mentions on each person’s profile page otherwise, you’ll never be able to easily see the public message to @username you just wrote. The key point being, you want this to show up on THEIR profile.

c. Probably worth considering including a notification to @username of said public message via email (make optional)

d. Q: Will these @’s be co-mingled in your own status updates and, thus create confusion. Maybe that doesn’t matter and i am overthinking it.On the activity stream, it says John Doe posted an update, when he really sent @username a public message. In Twitter when @ leads a message as 1st character, it has different context than everywhere else in the Tweet. Perhaps -> John Doe sent @username a public message ? or something.

I know I am getting fine grained here but theses (excellent) feature adds need to be over the top intuitive when introduced or they will breed unintended usages.

Thanks. That clears things up. The only other problem I’ve encountered is after I deactivate the BuddyPress plugin and re-activate it, I’ll get the follow db errors:

WordPress database error: [Duplicate key name ‘useritem’]

ALTER TABLE wp_bp_notifications ADD KEY useritem (user_id, is_new)

WordPress database error: [Table ‘wp_bp_activity’ already exists]

RENAME TABLE wp_bp_activity_user_activity_cached TO wp_bp_activity

WordPress database error: [Duplicate entry ‘1’ for key 1]

INSERT INTO wp_bp_xprofile_groups VALUES ( 1, ‘Base’, ”, 0 );

WordPress database error: [Duplicate entry ‘1’ for key 1]

INSERT INTO wp_bp_xprofile_fields ( id, group_id, parent_id, type, name, is_required, can_delete ) VALUES ( 1, 1, 0, ‘textbox’, ‘Name’, 1, 0 );

I’d ultimately love to see things go in that direction, and have been sifting through code the past few days thinking of how to get more red in the trac than green.

However, if this was the case, and activity had a component scope and a serialized array of return values, then you could replace private messaging with a threaded activity stream that only the users involved in that thread can view. You could send activity to multiple groups at a time, or only 1, or all of your groups, or the entire site, or any other registered components serialized set of values that mean whatever they mean.

You can almost replace the notifications class all together too, because if you take a count of the number of activities a user has directed at them and store it in usermeta, when the user returns if that number is higher, there’s your total notifications. Filter those new activities and now you can see how many of each. Actually, the code already exists within both WP and BP to do this.

In that regard, the activity stream does start to replace core communication components like forums, private messages, status updates, notifications, and the wire. At that same time, BuddyPress becomes less about separate components with their own API’s and classes and subsets of functions, but more about creating new methods for users to interact with each other in specific scopes of communication.

You could take things like twitter lists and make them work both ways, where you could send a message/comment/update/picture to only specific users instead of only viewing tweets from users. You could create an endless array of ways and names for collaborative tools to develop the platform from within the platform. It’s basically the blog post_types concept attached to people’s activity instead of re-categorizing blog posts.

The way to further develop groups would need a whole new topic, but I’ve got some ideas for that too.

@mrmaz, what you propose is the fundamentals of how I’ve approached my development before finding WP; start with small basic classes and work my up in functionality. There very easily could be a basic “bp_component” class where every new component just extends off of that, and sets the needed vars and assigns the needed functions accordingly.

Hi DJ Paul.

as far as I can see, nobody is complaining that the sky is falling, that would be a quite silly thing to do. Well I guess technically it is, but at least the earth is stopping it from doing so

Just pointing out an inaccuracy in thinking, I am sure that this is allowed without immediately posting PHP to fix it?

Back on topic; the question should also be: how could this spammer get access to all the usernames automatically? Of course everybody is listed, but somehow the were harvested and added to the pm list.

– Anyway, I think a very good start is that you can only message your friends. Thought that this would be already ths case, that is why I wondered how we could get spammed?

– Additionally: a maximum of PM’s per user per x amount of time (seems that 1/minute should be enough, + 50 per day. of course this should be optional and configurable with error notification (site options or plugin?)

– Maybe a maximum mailbox size, which included sent messages. So that at least spammers have to clean out their sent box before being able to send new messages.

– Also a maximum of adressees per PM, else the other 2 are useless

– maybe a minimum age of user (meaning time since registration), before he can send out PM at all?

Of course, any of these can be worked around, but at least it might slow spam down, at least from strangers..

Cheers, Harry

Welcome Pack did originally auto-accept Friend invites but someone made the suggestion that letting users respond to the notification also taught them how to use the site. I changed it a few versions back.

Devil’s advocate: if you friend everyone with everyone automatically, what’s the point? You haven’t got any not-friends to be not-friends with

Hello.

I do have spam user registrations even with registration option set to:

[*] Only logged in users can create new blogs.

I understand this option to say that new user registrations are DISABLED but registered users may create blogs. Unfortunatly the “Register”-Button appears in the welcome widget with that setting — even though clicking it will redirect back to the homepage.

To disable the above option also disables the blog creation — which I do NOT want.

For an unkown reason I do see spam registrations (a couple per week) but it seems those users are not able to login and create blogs (or comment). I also do NOT get the usual notification mails for new user registrations.

It seems like a bug to me.

Here is one way to do it I believe. Put this filter and function inside a plugin or your custom.php.

add_filter('bp_blogs_activity_new_post', 'my_process', 2, 3 );



function my_process($activity_content, $post, $post_permalink){



$activity_content = sprintf( __( '%s wrote a new blog post: %s', 'buddypress' ), bp_core_get_userlink( (int)$post->post_author ), '<a href="' . $post_permalink . '">' . $post->post_title . '</a>' );

$activity_content .= "<blockquote>" . bp_create_excerpt( $post->post_content, 25 ) . "</blockquote>";



return $activity_content;

}

I think this is the most efficient way of doing this. Basically, this code snippet overrides the content of the activity notification for a new blog entry. It is unfortunate that you have to write all the other crap again, but as you can see the thing you want to change (bp_create_excerpt) doesn’t have its own filter.

The good news is, unlike some approaches to this problem, this solution doesn’t require that you alter the core.

Try it and see if it works. Sorry ’bout the layout overflow

Hi guys, I’m having the same problems. When I do not add the $bb->bb_xmlrpc_allow_user_switching = true; line to the bb-config file it works, but just for the admin. After adding it, bbpress keeps coming up with the famous ‘There was an error posting that topic.’ notification. Since it’s dificult to debug a message like that I just can’t find out what can be wrong…I just updated the BBPress installation to 1.0.2, but I still have the same problem.

I hope somebody can help me out, thanks .

I think it’s a great feature and should be available to everyone… but perhaps should have more messaging around it and/or made an option that an admin can disable. Personally… in my case… this feature would be invaluable and it would need to be available to everyone. It all depends on the nature of the group. For a giant group… maybe you don’t want it. But let’s say you form a group that is a small collection of committee members using the wire to talk about ideas or what have you… in that case… the mass notify is great. Also… users who get annoyed with these kinds of notifications always have the option to turn them off!

@Boone – Cool. Brent and I have decided to go with your version for our interim rollout tonight. Yours just implements users options much better. However, we are going to redo the user sent email on notification as we don’t think it steers novice users well to action 9from experience) Not a big deal and I hope you aren’t offended. It involves a few extra variables and copy tweaks. I’ll post you when it’s done.

Mike

Wow, Westpointer, we had the same idea at the same time. https://buddypress.org/forums/topic/group-forum-subscription

My version allows a bit more user control (opting out of specific discussions or entire groups) by using bbPress’s native Favorites function. I wonder if there’s some way you and I can combine forces

I literally have to go to work after this post but:

To fix your site, rename your plugins directory to anything else i.e. ‘aardvark’. Load admin again, it should load up OK. Rename ‘aardvark’ back to plugins. You’ll have to re-activate any existing plugins. Once those have been done, try activating BP site-wide again.

BP v1.0.3 tables are:

wp_bp_activity_sitewide,wp_bp_activity_user_activity,wp_bp_activity_user_activity_cached,wp_bp_friends, wp_bp_groups,wp_bp_groups_groupmeta,wp_bp_groups_members,wp_bp_groups_wire,wp_bp_messages_messages,wp_bp_messages_noticeswp_bp_messages_recipients,wp_bp_messages_threads,wp_bp_notifications,wp_bp_user_blogs,wp_bp_user_blogs_blogmeta, wp_bp_user_blogs_comments,wp_bp_user_blogs_posts,wp_bp_xprofile_data,wp_bp_xprofile_fields,wp_bp_xprofile_groups,wp_bp_xprofile_wire,

Safe to delete as you haven’t used BP yet. Also these records in wp_sitemeta:

Any “meta_key” beginning with “bp-” i.e. bp-core-db-version, bp-friends-db-version.

If you don’t remove those meta_key records, then BP will think it’s already installed and won’t install itself again.

Before you activate BP again, open up your web server error log in a window and see if you get any specific messages when you try to run.

Also, versions of WPMU and BP you are you trying to install here will help us help you.

r-a-y

There are a number of new hooks and an array object that need to be available for the privacy component to function. Although the alpha versions may work with v1.1, the full-blown version is really targeted for v1.2 and will require that as a minimum.

Concerning your wire post, for some reason, I believe that I never received that email. Strange, since I do have all my email notifications set to “Yes”.

But, to answer that specific question, your direct calls to xprofile fields should still function properly. Since you are pulling your data directly from the table and not from a templatetag function, you should be fine. Now, if you want your direct calls to be subjected to privacy control, then that is a different matter. You would then need to pull your data after the fields array has been filtered.

There is a separate table that gets installed that handles all privacy object settings. The privacy component filters the fields array that populates the profile page, removing any field-level elements that a given user chooses to hide from a given viewer category.

Just experienced the OP’s problem.

I looked into it and found a tentative fix… though a BP dev will need to look at the code.

In “bp-core/bp-core-notifications.php”, look for the bp_core_notifications_for_user() function.

Then look for these lines:

$item_id = ( 1 == $action_item_count ) ? $component_action_items[0]->item_id : false;

$secondary_item_id = ( 1 == $action_item_count ) ? $component_action_items[0]->secondary_item_id : false;

Change this to:

$item_id = $component_action_items[0]->item_id;

$secondary_item_id = $component_action_items[0]->secondary_item_id;

I don’t know why there was a check done for only 1 item and then returning false for more than 1… if a BP dev can explain why, that’d be great.

Let me know if anyone encounters any problems.

Trac ticket made.

The Skeleton Component is just that–a generic, bare-bones plugin template that you can use to create your own, custom BuddyPress plugin.

But the only things that this plugin do is to put in profil EXAMPLE..

Did you read the in-line documentation? At the top of bp-example.php it reads:

--- SKELETON COMPONENT V1.2.2 ---



Contributors: apeatling, jeffsayre



This is a bare-bones component that should provide a good starting block to

building your own custom BuddyPress component.



It includes some of the functions that will make it easy to get your component

registering activity stream items, posting notifications, setting up widgets, adding

AJAX functionality and also structuring your component in a standardized way.



It is by no means the letter of the law. You can go about writing your component in

any style you like, that's one of the best (and worst!) features of a PHP based platform.



I would recommend reading some of the comments littered throughout, as they will

provide insight into how things tick within BuddyPress.



You should replace all references to the word 'example' with something more suitable

for your component.



IMPORTANT: DO NOT configure your component so that it has to run in the

/plugins/buddypress/ directory. If you do this, whenever the user auto-upgrades

BuddyPress - your custom component will be deleted automatically. Design

your component to run in the /wp-content/plugins/ directory

Hello. I’ve started to work on it since a few weeks.

It starts to be interesting.

*are things not started yet or **planed for a even more later

TYPES & CATS

-customizable types and categories, nestables

**customizable fields for posting/showing classifieds in it

MODERATION :

-decide wether or not to allow public viewers

-decide wether or classifieds needs validation before being published

-*grant a user moderator for all classifieds or by type / category

SITE VIEW

-search, explore, filter (by categories, days, **custom fields)

MEMBER VIEW

-show my published classifieds

-show my- awaiting moderation [author/moderators only]

-show my unactive

-watched : when you click a button on a classified, it will be in your profile and you’ll be notified if someone posted a on the wire or if the author modify it +*watched types & cats

-single classified : see details, author, see & post on the wire, see watchers

MEMBER OPTIONS

-*email notifications for new classifieds, classifieds by type,category

-*email for new posts on wire (watched classifieds)

-**email for new classifieds of friends

-*filters for home page

POSTING

– user needs to agree terms & conditions (only once) before posting

-fields : title, description, type, category

-****customizable fields

-****photos

-enable wire

-*enable email notifications when editing (for watchers)

…maybe i’ll start with this

I also have to say that it is a huuuge work and I’ll probably open a project page with a PAYPAL button to encourage me (need it).

I’m not a professional coder but i’m trying to do the best possible.

Today i’ve almost finished the admin part.

Proud to say that I’ve find something to dynamically (jQuery) add types/cats and edit,order (nested!!),delete,save them. It works !!!

<img src=”http://img53.imageshack.us/img53/420/classifiedssetup.jpg&#8221; alt=”classifieds setup” >