Forum Replies Created
-
Use grep. That’s what I do. From the UNIX or Mac Terminal command line, cd to your buddypress installation directory. Then:
`grep -nR ‘bp_after_signup_profile_fields’ ./`That’ll tell you all the locations of all the instances of that text.
In the case of this particular do_action, I am pretty sure it is just there for the use of other plugins. I don’t believe it does anything in BuddyPress itself.
The plugin is not done yet.
In reply to: Forum Notification Via Email?BP core does not do any email notifications related to forum posts. So there is nothing for the Group Email Subscription plugin to interfere with.
Donations always accepted at http://teleogistic.net/donate/
The one thing that is truly network-wide about BuddyPress is that posts from every blog on the network will get tracked in the activity stream by default. If you turn off blog tracking (Dashboard > BuddyPress > Component Setup) then it’ll be functionally equivalent to having BP installed on a single blog. If you want to exclude single blogs, you could write a little plugin that unhooks the bp_blogs activity actions, and activate it on the blogs that you don’t want tracked.
Permissions are simple now: every member of a group can do everything to a doc in that group. It’ll be finer-grained when I get around to it.
You’re seeing the same docs in every group because you are using 3.0.2. I use the tax_query stuff in 3.1 to display docs on a per-group basis.
I should note that the plugin definitely *does* require WP 3.1. No way to make it compatible with 3.0.x, because I use some of the new tax_query stuff.
Ha ha, BuddyPress doesn’t like my Cyrillic. I said: thanks, I’ll let you know when it’s finished (po russkiy konyeshno)
Just pushed up a fix for that bp_is_current_component bit. I’ve got the plugin working on a local version of 1.2.7. Looking a bit ugly at the moment, but working.
@jokermill ??????? ??????? – ? ???? ????? ????? ?????????
In reply to: Buddypress, how to install bbpress (doesn’t work)
The project can be found here: https://github.com/boonebgorges/buddypress-docs
It is working properly for the most part. I have to do a fair amount of work to the doc edit screen for it to be fully ready to launch.
NB: I have been developing on the BP trunk. I’ve been adding 1.2.7 compatibility where it’s been obvious, but it’s possible that it won’t work on the stable version of BP.
In reply to: Buddypress, how to install bbpress (doesn’t work)Sure, you can disable the forums by going to Dashboard > BuddyPress > Component Setup and switching the Forums component to Disabled.
In reply to: Buddypress, how to install bbpress (doesn’t work)Please don’t bump your posts more than once every 24 hours.
To be clear, did you follow the steps from this page https://codex.buddypress.org/buddypress-site-administration/buddypress-forum/ , at the bottom where it reads Process for installing bbPress included with BuddyPress?
1) Dashboard > BuddyPress > Forum Setup
2) Setup a new installation, etc
3) Then go to a group > Admin > Enable group forumsYou should then see a Forum tab in the group. The bbPress software comes autoinstalled when you download BuddyPress. There is no need to download anything else.
In reply to: BP_init not working for themes Functions.phpIt’s possible that bp_init is fired too early in the process for it to be detected with functions.php, which is only loaded with your theme (relatively late). Try hooking to something like ‘wp’ instead. You should be able to detect whether BP is activated by doing something like
`if ( !function_exists( ‘bp_loaded’ ) )
return;`In any case, you should be enqueuing scripts on the init action, which is unrelated to bp_init: https://codex.wordpress.org/Function_Reference/wp_enqueue_script
Changing the tabs is an appearance issue; it doesn’t have any effect on the activity items shown.
Try the following function in your functions.php or bp-custom.php. The logic is this: If the query string is empty (as it is when you first visit the activity page) and there is nothing in the POST variable that says which scope to show (that is, the user has not clicked ‘All Activity’ and thus set an AJAX request into effect), then show only my group content.
`function bbg_my_groups_activity_default( $qs ) {
if ( empty( $qs ) && empty( $_POST ) ) {
$qs = ‘scope=groups’;
}return $qs;
}
add_filter( ‘bp_ajax_querystring’, ‘bbg_my_groups_activity_default’, 999 );`In reply to: [Resolved] Trying to modify the group loopIn your code snippet, the magical part is user_id=, so you could do this
`if ( strpos( bp_ajax_querystring( ‘groups’ ), ‘user_id=’ ) )`In reply to: [Resolved] Trying to modify the group loopI think you might be barking up the wrong tree. Since you want to repurpose an existing query (the ‘my groups’ query) you don’t really need to alter the querystring. Instead, you should be altering the behavior of the query itself, which happens at the level of the bp_has_groups() function, as found in bp-groups/bp-groups-templatetags.php. One of the arguments for that function is user_id; when one is passed, you know you are looking at a my-groups loop.
Ideally, you would be able to filter bp_has_groups() to detect when a my-groups-type query was being requested, and then hijack it and do a query just for hidden groups. Unfortunately, I don’t believe that there is going to be an easy way to do that in this version of BuddyPress. For one thing, while there is a filter on bp_has_groups, the original arguments (like user_id) are not passed along to the filter in BP 1.2.7 (it’d be a good enhancement request). Second, there is no way to filter groups by status (public, private, hidden) at the moment (that too would be a good enhancement request).
One quick and dirty way to do something like what you want to do is to filter bp_has_groups, grab the content of the group query out of the groups_template global, and remove the ones that are *not* hidden. It’s not an ideal solution for a number of reasons (for one, it screws up pagination) but it can work. Here’s an example off the top of my head (untested!)
`function bbg_hidden_groups_only( $has_groups ) {
global $groups_template;// when we are looking at a my-groups page…
if ( bp_is_user_groups() ) {
foreach ( $groups_template->groups as $key => $group ) {
if ( ‘hidden’ == $group->status ) {
unset( $groups_template->groups[$key] );
}
}// reset the keys so you don’t end up with blank spaces
$groups_template->groups = array_values( $groups_template->groups );
}return $has_groups;
}
add_filter( ‘bp_has_groups’, ‘bbg_hidden_groups_only’ );`In reply to: [Resolved] Trying to modify the group loopCheck out the function bp_dtheme_ajax_querystring() in bp-themes/bp-default/_inc/ajax.php. That’s where most of the bp_ajax_querystring() magic is happening. Essentially, it looks first in the $_POST (for a new value via AJAX) and from there in the $_COOKIE for the current page view.
In reply to: OpenSocial for BuddyPressThere’s an issue tracker at trac.buddypress.org (same username:pw as you use here), where you should feel free to open tickets for ways that BP needs to be changed in order for your Open Social add-on to work. For more general discussions – when you are talking about extending BP rather than modifying it – this forum is probably a better place. There are certainly more eyeballs here than on Trac.
In reply to: Will BP adminbar survive WP 3.1?It’s possible that there will be a version of the BP buddybar that is built into the WP 3.1 admin bar by the time the next version of BuddyPress comes out. However, I do not think that the BP Buddybar will be taken out of BP in the next version in any case, as it would disrupt many people who have modified and extended it. Worst case scenario, the Buddybar will be taken out and put into a plugin so that site admins will have the option of installing it for that Classic Look
In reply to: OpenSocial for BuddyPressYeah, @modemlooper what are you using for your iPhone app in the absence of REST? Or are you requiring a BP plugin to make it work?
In reply to: OpenSocial for BuddyPressHey Carl – Here are a couple considerations.
– WordPress (which BP runs on top of) already has support for XML-RPC. Here’s the spec: https://codex.wordpress.org/XML-RPC_wp Of course, the details of this spec are not much good for BuddyPress, since for the most part, BuddyPress data objects are different from WP data objects. But the gateways are already there for working with XML-RPC.
– That said, the kind of system-to-system talking that would be appropriate for BP would be much better suited to the simplicity of a REST gateway (as opposed to the generally one-to-one, client-to-server relationship that WP’s XML-RPC support was built for – eg the use case of native Android apps communicating with a WP installation).
– Neither WP nor BP has anything built in for REST support, so you’ll be starting with a clean slate (that is both good news and bad news!). There have been a few add-ons that might be good places to start. The one I’ve used in the past is called WP-RESTful https://wordpress.org/extend/plugins/wp-restful/. It’s a nice plugin, but it also has a huge amount of overhead, in particular with a full implementation of oAuth.
– In the very simplest terms, the very easiest way to set up a REST endpoint in WP is to intercept a certain kind of URL query and interpret the POST data. Here is about the most stripped down API possible:
`function bbg_api_listener() {
global $wp;if ( $r = $wp->request ) {
$ra = explode( ‘/’, $r );
if ( $ra[0] == ‘restserver’ ) {
// Do some stuff with the $_POST
die();
}
}
}
add_action( ‘wp’, ‘bbg_api_listener’, 1 ); // Ensure that the request is parsed before any WP front-end stuff, but after the core of WP is loaded`In this case, I am assuming that requests will go to example.com/restserver. From there it’s a matter of unpacking the POST action, etc.
– As for outgoing requests, WP has a pretty nice built-in HTTP library called WP_Http. Here is a nice tutorial: http://planetozh.com/blog/2009/08/how-to-make-http-requests-with-wordpress/ It’s a wrapper for cURL with some graceful fallbacks.
– For something to go into the core of BuddyPress it needs to be really flexible, especially in terms of authorization (this is part of the problem with WP-RESTful and its reliance on oAuth). Keep that separation in mind when you’re crafting something.
Can’t wait to see what you come up with. As you know, I’m really interested in this project and will be excited to play along.
In reply to: Security Feature Suggestions?Please don’t bump your own posts more than once every 24 hours.
In reply to: Security Feature Suggestions?Sorry to jump in on what is apparently just a semantic issue, but I want to point out that BuddyPress is actually quite *secure*, taking advantage of a wide array of security features in WordPress intended to prevent against various kinds of mischief (SQL injection, XSS, CSRF, etc) and in some cases inventing its own. It is in the area of customizable, fine-grained *privacy* that BP is somewhat lacking at the moment.
In reply to: Some questions about BuddyPress friendshipsAh, yeah, if you are trying to access things in an ajaxy way, and you’re not hooking into WP in the right way, you might hit some problems because BP and other plugins might not be fully loaded. Were you using a wp_ajax_ hook? Generally speaking, you can’t simply include BP files manually and have things work properly – all of WP needs to be loaded. https://codex.wordpress.org/AJAX_in_Plugins#Ajax_on_the_Viewer-Facing_Side
I’m not sure I entirely understand your suggestion about an additional template. If you have even a rough sense of what such a thing might look like, I invite you to work up a patch (even a super sketchy one) and post it as an enhancement ticket on trac.buddypress.org (with your buddypress.org user/pass).
