BuddyPress.org

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” >

@jeff:

I’d already marked two of those threads as resolved, and posted what was causing the problem.

They weren’t problems related to this.

I have 2 unresolved threads open: the media library duplicate declaration problem, and the failure to add a friend issue.

I’ve responded to your feedback on these in thread: https://buddypress.org/forums/topic.php?id=3000

I appreciate the helpful responses from anyone on this forum (moderators and regular users alike). Thanks in advance.

I am very interested in privacy component. How is it going so far? Do you have some estimation when will it be available to test or use?

What I have found as a must regarding privacy (until now) is:

– allowing user to set what details from profile s/he wants to be public, available just to friends or private

– settings on activity streams which will allow user to select what type of activities s/he wants to be displayed in sitewide activity, be available to friends or be totally private. This settings could be similar to Notification settings (for email notifications).

I intended to write this on my own, but found out that it can’t be done easily without changing activity core files (and that is never a good option) and then I discovered that you are working on privacy component. So, if you see a way how I can help in development process, please let me know.

@ Atul Singhal

duplicate you /register.php in your buddypress-home theme,

(duplicate it to keep it as a backup)

towards the bottom of register.php you’ll see something like “do_bp_core_signup”

you can comment that out and replace it with the Iframe version of the rpx plugin

‘

<iframe src=”https://buzzwe.rpxnow.com/openid/embed?token_url=http%3A%2F%YOUR_SITE.com%2F%3Frpx_response%3D1%26goback%3Dhttp%253A%252F%252FYOUR_SITE.com/WELCOME_LANDING_CUSTOM_PAGE&#8221;

scrolling=”no” frameBorder=”no” style=”width:400px;height:240px;”>

</iframe>

‘

just change YOUR_SITE and WELCOME_LANDING_CUSTOM_PAGE to your own token url

one issue I have with this on my site, is that the RPX plugin doesn’t gather much information… sometimes it will only get the email/username… sometimes the email is a “proxy mail email ” => @yahoo12343-proxymail.com (I haven’t confirmed this with all the 3rd party login providers)

this will effect how the notifications work… so you’ll proly want your landing page to have instructions to update their profile information

that should work

Hi all,

The code is located in wp-includes/wpmu-functions.php (it is a big file)

A few caveats:

1) There is text for the user signup email and for the blog signup email (blog signup email is also in the admin panel)

2) There is text for a bunch of other emails, alerts and notices. All over the place

3) The text is located in some squirrely locations, so move your cursor slowly (I missed some of the phrases a few times)

4) Keep a log of what you change, because wpmu-functions.php will change with WPMU upgrades.

5) You probably already know to avoid apostrophes and other symbols–depending on which ones you use, errors show up. I just avoided contractions.

Hope this helps.

I\’d like to know as well. Especially that \”Dear User\” annoys the hell out of me. \”User\” sounds like \”drug user\” or \”abuser\” or \”you\’re not a friend, you\’re just a user!\”.

The email is sent out after the new member has already given his name. There should be a way to just include the full name or first name in the welcome email. It\’s standard practice.

BTW, Socialpreneur, do you mean this thread? It’s not very helpful.

yeah, it was in v1.1 for sure. i used it for my first component. i found a reference in /wp-content/plugins/buddypress/bp-example/bp-example-cssjs.php in v1.1. I tried adding this back myself and it didn’t work.

/**

* bp_example_add_activity_bullets_css()

*

* This function will allow your component to dynamically add CSS to themes so that you can

* set the activity feed icon to use for your component.

*/

function bp_example_add_activity_bullets_css() {

?>

li a#my-example, li a#user-example {

background: url(<?php echo site_url( MUPLUGINDIR . \'/bp-example/images/heart_bullet.png\' ) ?>) 88% 50% no-repeat;

}



li.example {

background: url(<?php echo site_url( MUPLUGINDIR . \'/bp-example/images/heart_bullet.png\' ) ?>) 0 8% no-repeat;

}



table#bp-example-notification-settings th.icon {

background: url(<?php echo site_url( MUPLUGINDIR . \'/bp-example/images/heart_bullet.png\' ) ?>) 50% 50% no-repeat;

}

<?php

}

add_action( \'bp_custom_member_styles\', \'bp_example_add_activity_bullets_css\' );

add_action( \'bp_custom_home_styles\', \'bp_example_add_activity_bullets_css\' );



?>

I assume you’re specifically talking about customizing a BuddyPress template. If so, then you need to look in the BuddyPress profiles tables in MySQL.

For instance, the field definition for the “Full Name” field is stored in the wp_bp_xprofile_fields table and any corresponding datum is stored in the wp_bp_xprofile_data table.

With respect to this:

At the moment Buddypress/WP MU makes it very hard, perhaps impossible, to flexibly use member’s real names or other data (companyname, city) in the site or have something like ‘Hello John’ in email notifications.

That is not true. Any piece of stored data can be accessed and spit out in any number of ways. It just must first be in the database. Look in the bp-xprofile.php file and the bp-xprofile subdirectory for a number of functions that can be called to extract a user’s data.

By the way, I did see your other post about this topic and it was answered appropriately. With the default WPMU and BuddyPress setup, you will not be able to use a user’s full name until they’ve entered that data. They will not be able to enter their full name until after they register.

So, unless you hack the wp-signup.php or register.php files, and require that a full name be provided when registering, you will not be able to send them a welcome email with their full name since that piece of data does not yet exist.

All of what you are asking is possible but requires either a pre-existing plugin, a custom hack, or your ability in customizing and coding a BuddyPress template.

Seems to me “report this item” is the exact opposite of “Add to Favourites”… The buttons would show up at the same spots (group home, blog post, wire post, photos, user’s profile etc), the handling code would be the same except in Report case a notification gets sent to the administrator and in Favourite’s case it gets added to the user’s favourites.

That being said, Report This SHOULD be in the core…

@awarner20 your problem with the email friendship requests is a bug. Can’t be solved with a one liner. Sorry. I did submit a workaround patch in trac though:

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

It eliminates the problem by eliminating the problem. Lemme explain. When a user requests friendship an email is sent out to the destination user. The destination user is supposed to click the link and it automatically approves or rejects the request. Doesn’t work due to the fact that a security mechanism is being used to validate the process. The ‘nonce’ security scheme uses the originating user’s identity and some other stuff to come up with this ‘nonce’ key. The key is only valid when used by the originating user.

When the destination user clicks on the link the key is used but they are not the originating user. So the security check fails. Andy is aware of the problem. I just removed the automatic accept/reject links and used a link to the destination user’s friendship notifications page where it will have to be manually accepted or rejected.

$test is empty. no matter what we do.

/wp-content/mu-plugins/x.php

<?php

require_once( ‘bp-core.php’ );

global $bp, $wpdb, $current_blog;

require_once( ‘x/classes/DB_Operations.php’ );

require_once( ‘x/classes/FS_Operations.php’ );

require_once( ‘x/classes/POST_Operations.php’ );

require_once( ‘x/classes/Render_to_Browser.php’ );

require_once( ‘x/classes/x_Environment.php’ );

require_once( ‘x/classes/File.php’ );

require_once( ‘x/classes/Notification.php’ );

$init_environment = new x_Environment();

$doPostActions = new POST_Operations();

$test = $bp->loggedin_user->id;

?>

maxaud, the function that does the work in bp is groups_send_invites() and it lives in bp-groups.php, line 1642.

function groups_send_invites( $group_obj ) {

global $bp;

This function serves both the group creation ‘send invites’ and the member theme ‘send invites’ in the group screen.

I’d put a return; statement right under that global $bp; statement. Users can flip all the switches they want but nothing will actually happen. The users will still see the capability but nothing will work.

Lemme test this to make sure…

No notification emails are actually sent. The screen says it did but it didn’t. The notification message “Group invites sent” isn’t part of that function you will be bypassing.

What a great idea. Never thought of that. That message about ‘you have no friends’ (something like that) is kinda bleak. We could have the system send them a ‘friendship request’ from admin. That way they learn a little about the adminbar and the member theme right away. That glaring (1) next to notifications would be hard to resist. Click Me.