BuddyPress.org

I had the same problem with jcarousel and buddypress, and paid a few dollars over at wpquestions to get the fix, which involved editing a line of code in a buddypress js file which handles easing. The full answer is here if anyone else gets stuck: http://wpquestions.com/question/show/id/1615

hth

@boonebgorges BuddiPhone is actually a BP component plugin. It creates a slug /mobile. I would love to use REST and make it native, then I could use the hardware – image uploads – contact lists etc. I messed with this plugin a bit https://wordpress.org/extend/plugins/json-api. BuddyPress json post / get would be killer.

Yeah, @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?

Drool REST api

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

I use custom community theme on http://www.heroisme.nl but there are some missing pages when clicking on community items. Is there a solution for this?

This theme is really great!
I love it, and use it on my site.
Thanks allot!

but it’s still prone to being buggy. I’ll say

It’s reasonably stable for judicious development on while mentally noting areas that appear buggy, but one caveat , progress with it’s development is fast and furious :0 so update your repo checkout often to keep up with fixes as I experienced recently.

@DJPaul can you just confirm or settle that confusion on what platform 1.3 will require as far as I’m aware it’s simply the WP 3.* stream rather than 3.1

Edit// hmm just viewed that twitter link, slightly confused now. I have 1.3 albeit a trunk checkout prior to John Jame’s changes that runs on 3.0.4 what has changed or did it really never run ‘fully’ on 3.*. Also wasn’t aware Nacin was a BP developer how is it he knows better than you what BP will run on

You will need to add such things to BuddyPress, yes. If you come up with any good patches for core, I’d love to look at them.

And I thought BP 1.3 just required 3.*

I have a test install of BP 1.3 running on WP 3.0.4 and another running 1.3 on WP 1.3 RC 2

@DJPaul will need to confirm that comment in the thread you link to.

As for release date, you should note the blog post by John James where he announced he was proceeding with some major refactoring of the core, the open tickets is not really indicative of the amount of work left to complete with this particular cycle, I doubt that 1.3 will be ready this side of Feb and ought to go to a RC stage for a little more rigorous testing for this particular release.

I would have thought regardless of release dates one can and should be starting to test ones themes / plugins under 1.3/3.1

I agree, Gravity Forms is well worth the money, even with the newish pricing scheme. The about-to-be-released 1.5 version even includes the option to replace the BP registration form and adds PayPal support and such (a developer license is needed for those). As far as I know there’s no inbuilt support for custom post types yet, but even using custom fields, coding a recipe plugin should be very easy.

I use Gravity Forms to do this, although you could also look into TDO mini forms (https://wordpress.org/extend/plugins/tdo-mini-forms/) if you’re not keen on spending any money. I will say this… the GA plugin is *the* best plugin I’ve ever splurged on, bar none.

I love the theme layout, but how do you add color to it?

You could possible use the group docs plugin or create your own component or even use something like gravity forms.

http://www.buddyboss.com/bp-group-documents-buddypress-plugin-review

Here’s an example of a BP recipe site http://thepioneerwoman.com/tasty-kitchen/

BuddyPress Codex

Is there a way to show the group avatar in the activity feed when the plugin pulls a post from an external blog. It looks a bit unprofessional to have just a blank space there instead of an image.

Thanks,
Nick