BuddyPress.org

@moominmama Invites is a work in progress. I have part of it working but not all yet.

https://buddypress.org/community/groups/cubepoints-buddypress-integration/
https://wordpress.org/extend/plugins/cubepoints-buddypress-integration/

Hi @pollyplummer. You have basically got the right idea, but there are a few problems.

First, your check for usermeta is not formatted correctly. See https://codex.wordpress.org/Function_Reference/get_usermeta for get_usermeta syntax. In any case, get_usermeta gets stuff from the wp_usermeta table, and I used it as an example in my code to give you a sense of the kind of check you’d want to do. But that’ll only work if you’re checking against a piece of data that is stored using update_usermeta. BP xprofile fields are not. If the “114” information is stored in a bp xprofile field, you will probably have to do some magic with xprofile_get_field() to get it to work. The following will check for a field called “Type” and check to see if the current user’s Type value is 114:

$field_id = xprofile_get_field_id_from_name( 'Type' );
$field = xprofile_get_field( $field_id );
$value = $field->data->value;

if ( bp_the_profile_group_name() == 'awesome' && $value == '114' ) {

There’s probably a slicker way to do this, but it works. Again, this is only relevant if you’re storing the salient data in the xprofile tables.

The second problem is that you don’t want to repeat the bp_has_profile etc stuff inside of the if statement. If you want to feed a profile_group_id argument to bp_has_profile, you should do it in the initial loop.

Then make sure that you include the markup inside of the conditional if statement. In edit.php, that means everything, including the

Hi, what’s the latest news for this pluggin? The Plugin’s changelog says it now supports BuddyPress 1.2 ( https://wordpress.org/extend/plugins/bp-member-filter/changelog/ ), but I can’t get it to work on BP 1.2.3. This is probably just me being ignorant, but with such limited documentation available it hard for n00bs like me to get it working. I’d be more than happy to sponsor the plugin as well if support for 1.2.3 does exist and the documentation is extended.

@Arques,
it looks like he is using, the Kaltura Media Component.

https://wordpress.org/extend/plugins/buddypress-kaltura-media-component/

@r-a-y you’re right, Saw for myself that BP components are rendered as Pages in test install with WPMU2.9.2/BP1.2.3 upgraded to WP3.0beta2/BP1.3-bleeding.

BP components rendered as Pages is not hot for me when I have 100+ Pages in main site of another test install (as I have in some live sites) and the Edit Pages panel and pagemash panel) have the BP components mixing in with “important information/documentation.” In this scenario, it would be more orderly to go multisite and to create a sub-blog and just to activate BP away from main site.

Of course for installs with BP set up primarily for social networking and with only 4 or 5 “static” pages – About, Contact, etc, no problem with components as Pages.

@anointed – great stuffm thanks for sharing Animo post_types.

Wordpress 3.0 Beta2, BuddyPress (current, think its 1.2.3), Buddypress Links v0.4.1

Links section, adding a new item. Trying to set the display image for the link by uploading an image. Image is 200×200 jpg.

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

I’m guessing this is related to the same code @Phlux0r posted above, but after looking at the bp-core-avatars file, and that specific function I was uncertain exactly where in there to insert that code into the function. Could we maybe get a line number or a larger code block?

Kimberly

(There is also a second, probably unrelated bug with Links, when I forget to fill in the Title & Description (and it was not auto filled), when I try to submit the link and get the error that says I must fill in all fields, the Title & Description area will not re-open.)

@Modemlooper

I ‘kind of’ agree with you when you say post_types are for individual pieces of content, but also disagree. Post types allows me to create a new object where I can assign multiple attributes to that object type ‘metadata, taxonomies’. You are also able to easily group individual object types of the post type together much easier than with pages. The real power comes into play when you create multiple post types and link them together. Then I have a ‘pods’ type of system with multi-relational datasets to a given object. There is just 100x more that I can do with a post type than with a page.

For instance, I am building a complete custom forum system using a post type. You could never do that with pages. Well I suppose you could but it would be much more work and not nearly as elegant. basically my goal is to completely dump the bbpress as it’s so far behind that it has no business in my sites. By using post types, I have all the inherent wp tools right at my fingertips for forum posts. Want to add images/video/tags/ to a post.. done… no work needed.

The advantage is then I could easily add that new post type to the activity stream, complete with all its attributes, ‘metadata’ for the individual object. Something else you can’t really do with pages.

Here is a really generic example of 3.0 multi relational post types in action. (It’s only a start, so please don’t complain about layout, have not even started that part yet, this is more concept than anything else)
http://deardaddy.org/sermons/daneil-ponce-sermon-1/

What you see here is much more than meets the eye
1. This is a custom post type sermons which is related to post types podcasts, preachers, locations.
2. The sermon title, description, and video are part of the sermon post type
3. When on the ‘add sermon’ admin page, you are also able to link it to a pre-existing post type to grab the preacher, podcast, and location. If they do not exist then you can add those attributes within the sermons post type without having to leave. Meaning you don’t have to go to post type podcast to add the audio file to a sermon. Same goes for preachers, locations.
4. sermons and podcast post types also have related taxonomies, ‘series, topics’. which you can directly link within the sermons page.

The easiest way to see how it’s linked is to notice the ‘locations’ link on the sidebar. It goes to:
http://deardaddy.org/locations/his-sanctuary-of-prayer/ which is the post type ‘locations’.

Keep in mind I did not have to manually type in the location when I added the sermon, although I could have, because it already existed. I simply chose it from a drop down of existing locations and they were linked together.

The power of this is simple.
1. I create a location one time
2. I can now add the individual location attribute to any new post type I create so long as I link the post types together, create a relationship in my themes functions file. This means that a user never has to input data more than 1x, it can be used over and over again in any post type.

To wrap up:
You said ‘a way in the front end of bp for users to add a movie’. I am already doing everything but the adding via the front end for the sermon example above. Adding the ability to the bp front end, will take me a bit of work, but it’s possible. I just have not yet had the time to read the bp code close enough. Hence my argument for post types in bp instead of pages. why add a movie page, when I can add a post type movie with all the attributes into the stream. Much much more power that way.

@r-a-y
will be interesting to see the direction they take. If they don’t worry about backwards compat well then the doors are wide open.

@anointed – There is no audio chat! It’s all text. What you read is what actually happened.

WP 3.0 isn’t even out of the gate yet; when WP 3 actually gets released, we’ll see where Andy and the core devs take it.

—

@modemlooper – if you check out what the BP Wiki component does, it already uses custom post types (it’s a development version). So custom post types for BP is possible via plugins. However, for the core (as stated above), it’s whatever the dev team decides.

@r-a-y
I couldn’t make it to the chat today, but I just read through the thread. What I couldn’t find was the reasons for using pages instead of post_types. Were those listed off on the audio portion or something?

I’ve spent the last month digging really deep into post_types, and while I don’t have a strong background in bp structure, post_types seems like the perfect fit for bp. Would you kindly give us some of the pro’s/con’s of pages vs types and why the decision was made? Maybe it would help many of us to understand the bp structure and direction in the future a little better.

did you try enabling username compatibility mode?
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/characters-in-usernames-cause-strange-issues/

Use paginate_links() https://codex.wordpress.org/Function_Reference/paginate_links. It’s not very easy to use (IMHO) but it’s better than doing it from scratch.

You’ll have to wait for Google to check your site again.

You can expedite this process by signing up for Google’s Webmaster Tools and requesting your site to be delisted.

Also make sure your WP site is blocked from search engines:
https://codex.wordpress.org/Settings_Privacy_SubPanel

BuddyPress is overkill.

You want to use a front-end posting plugin. There are a bunch of them out there.

Here’s one thread:
https://wordpress.org/support/topic/365980

Make sure your users have a WP role of Contributor or higher:
https://codex.wordpress.org/Settings_General_SubPanel

Such a discussion was briefly brought up by @sbrajesh today on the dev chat.

BP components will be full-on pages in BP 1.3.
However, there are currently no plans to implement custom post types for BP components.

See if a .htaccess file is written in your /wordpress/ folder?